-
Notifications
You must be signed in to change notification settings - Fork 110
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
Add combine script, to combine two manifest lists and push the result #871
Conversation
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.
Neat! Just some minor things, but otherwise LGTM!
Bonus points if you can figure out a way to test this while mocking out the remote calls. Maybe pull out the merging into a tested func?
This will be used to build a combined base image from our current distroless/static base image, and a Windows base image, to produce a base image that supports both. This will, in turn, provide a base image for Tekton images so they can be built with multi-OS support, in addition to their existing multi-arch(-but-only-Linux) support today.
/lgtm |
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.
/test .*
/test plumbing-yamllint |
1 similar comment
/test plumbing-yamllint |
Don't mind me, just trying something out: /run try-out-tekton |
hahaha well that sure didnt work - sorry for the noise @imjasonh ... now im not sure how to remove that check 😅 |
I forced it to be successful 🙏 sorry again for the noise |
Two years ago I was playing around with Prow's tekton support as a way to dogfood pipelines and I created this config to run a hello world type pipeline on the plumbing repo (tektoncd#66). Today while looking for uses of PipelineResources to update to use the experimental Pipeline to TaskRun custom task instead, I found this. It no longer runs successfully (just added noise to tektoncd#871) and I don't think there's any reason to keep it around.
Two years ago I was playing around with Prow's tekton support as a way to dogfood pipelines and I created this config to run a hello world type pipeline on the plumbing repo (tektoncd#66). Today while looking for uses of PipelineResources to update to use the experimental Pipeline to TaskRun custom task instead, I found this. It no longer runs successfully (just added noise to tektoncd#871) and I don't think there's any reason to keep it around.
/test plumbing-yamllint |
One more try to bump the yamllint task: /test plumbing-yamllint |
/approve |
/approve cancel |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: vdemeester, wlynch 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 |
/test plumbing-yamllint |
dropping lgtm to unblock tide /lgtm cancel |
Two years ago I was playing around with Prow's tekton support as a way to dogfood pipelines and I created this config to run a hello world type pipeline on the plumbing repo (#66). Today while looking for uses of PipelineResources to update to use the experimental Pipeline to TaskRun custom task instead, I found this. It no longer runs successfully (just added noise to #871) and I don't think there's any reason to keep it around.
re-lgtming now that tide is unblocked and plumbing-yamllint has passed /lgtm |
/test plumbing-yamllint |
Changes
This will be used to build a combined base image from our current
distroless/static base image, and a Windows base image, to produce a
base image that supports both.
This will, in turn, provide a base image for Tekton images so they can
be built with multi-OS support, in addition to their existing
multi-arch(-but-only-Linux) support today.
Ref tektoncd/pipeline#182
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.
/kind feature