Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Add option to run tests on non-Intel architectures #238

Merged
merged 1 commit into from
Mar 3, 2021

Conversation

barthy1
Copy link
Member

@barthy1 barthy1 commented Feb 26, 2021

Changes

At this moment tests for operator can be executed with default e2e-tests.sh script only for amd64 architecture, because operator image during setup process is built for amd64 by default. Addition of the PLATFORM env variable to Makefile allows to build operator image for needed architecture via --platform parameter in ko tool.
In case if PLATFORM variable is not specified, there will be current behaviour.

Also --kubeconfig parameter support is added to the test script, this parameter is used when tests are executed not on default k8s cluster.
If KUBECONFIG env variable is not specified, --kubeconfig parameter is not used.

Submitter Checklist

These are the criteria that every PR should meet, please check them off as you
review them:

See the contribution guide for more details.

Release Notes

NONE

At this moment tests for operator can be executed with default
e2e-tests.sh script only for amd64 architecture, because operator
image duringng setup process is built for amd64 by default.
Addition of the PLATFORM variable to Makefile allows to build
operator image for needed architecture via --platform parameter in ko tool.
In case if PLATFORM variable is not specified, there will be current behaviour.

Also --kubeconfig parameter support is added to the test script, this
parameter is used when tests are executed not on default k8s cluster.
If KUBECONFIG env variable is not specified, --kubeconfig parameter is
not used.

Signed-off-by: Yulia Gaponenko <yulia.gaponenko1@de.ibm.com>
@tekton-robot tekton-robot added the release-note-none Denotes a PR that doesnt merit a release note. label Feb 26, 2021
@tekton-robot tekton-robot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Feb 26, 2021
Copy link
Member

@vdemeester vdemeester left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@tekton-robot
Copy link
Contributor

@vdemeester: cat image

In response to this:

/meow
/cc @savitaashture @nikhil-thomas

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@tekton-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: vdemeester

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@tekton-robot tekton-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Mar 2, 2021
@nikhil-thomas
Copy link
Member

/lgtm

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 3, 2021
@tekton-robot tekton-robot merged commit 913e9d2 into tektoncd:main Mar 3, 2021
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesnt merit a release note. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants