-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Release on latest tekton #1421
Release on latest tekton #1421
Conversation
When running YAML E2E tests, use kubectl create instead of apply, so that example can use generateName, which is a best practice for run objects (TaskRun/PipelineRun). Using "create" also exposed name conflicts for several resources all named the same. Luckily the content of those secret was the same, so we had no race condition in the past, but it's best to avoid side effects between tests as much as possible and keep resource names uniques across examples. With this change we start running taskrun tests again, and it turns out the gitlab test is broken because of a broken gitlab URL. Introduce a subfolder for examples that are valid but that we don't want to run in CI because they need some access to a resource which is not available. The Gitlab test has been removed before this was merged, but keeping the no-ci folder anyways as it may be useful for examples that we have no easy way to run in CI. Fixes tektoncd#1397
/hold |
I'm still testing this in the dogfooding cluster. |
Change the release pipeline so that it runs on the latest version of Tekton. We can now run manual releases from the `dogfooding` cluster so there's no reason to keep compatibility to old version of Tekton.
95edc40
to
100e414
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
[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 |
I tested this using the staging bucket and the staging namespace on gcr.io, and it worked fine. Here are the logs for the pipelinerun
|
/hold cancel |
Changes
Change the release pipeline so that it runs on the latest version
of Tekton. We can now run manual releases from the
dogfooding
cluster so there's no reason to keep compatibility to old version
of Tekton.
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.
Double check this list of stuff that's easy to miss:
cmd
dir, please updatethe release Task to build and release this image.
Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes