Add nightly tests for cli, triggers & operator on ppc64le architecture

[svghadi]

Changes

This PR adds nightly e2e tests on ppc64le architecture for cli, triggers & operator. Nightly pipeline tests on ppc64le hardware is already enabled via #762.

/kind feature
/cc @afrittoli

Submitter Checklist

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

• Includes docs (if user facing)
• Commit messages follow commit message best practices

See the contribution guide
for more details.

[tekton-robot]

Hi @Siddhesh-Ghadi. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

[vdemeester]

/ok-to-test

[vdemeester]

/cc @afrittoli

[tekton-robot]

[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:

• OWNERS [vdemeester]

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

[afrittoli]

I would prefer we did not duplicate common deploy and cleanup script between bastion-z and bastion-p (and more architectures in future.
These deploy tasks are already duplicating logic which is release pipeline of the respective repo, it will become hard to maintain if we copy it many times.

I guess it's ok to do it for now, but I really would prefer if eventually we used the nightly build to run the tests, which would allow us to know whether the nightly build works or not.

In fact we could get rid of the extra cronjob, and define a trigger that catches the completion of a nightly release to start the tests.

/cc @barthy1

/lgtm

[tekton-robot]

@afrittoli: GitHub didn't allow me to request PR reviews from the following users: barthy1.

Note that only tektoncd members and repo collaborators can review this PR, and authors cannot review their own PRs.

In response to this:

I would prefer we did not duplicate common deploy and cleanup script between bastion-z and bastion-p (and more architectures in future.
These deploy tasks are already duplicating logic which is release pipeline of the respective repo, it will become hard to maintain if we copy it many times.

I guess it's ok to do it for now, but I really would prefer if eventually we used the nightly build to run the tests, which would allow us to know whether the nightly build works or not.

In fact we could get rid of the extra cronjob, and define a trigger that catches the completion of a nightly release to start the tests.

/cc @barthy1

/lgtm

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.