Add nop-image to release configs #3025
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This should ensure that the nop-image is built and released alongside other utility images. Followup from tektoncd#3014
tekton-robot
added
the
release-note-none
tekton-robot
added
the
size/S
ghost
approved these changes
Jul 28, 2020
tekton-robot
added
the
approved
|
/kind cleanup |
tekton-robot
added
the
kind/cleanup
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dlorenc, sbwsg 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 |
bobcatfish
added a commit
to bobcatfish/pipeline
that referenced
this pull request
Sep 9, 2020
In tektoncd#3025 the nop-image was added to our release pipeline, this commit updates our README to include an example that sets it. Also removed the reference to resources.yaml from the instructions b/c imo opening that file and modifying it is more confusing than helpful; feels like it makes more sense to create a new PipelineResource instance without bothering with that file.
bobcatfish
added a commit
to bobcatfish/pipeline
that referenced
this pull request
Sep 9, 2020
In tektoncd#3025 the nop-image was added to our release pipeline, this commit updates our README to include an example that sets it. Also removed the reference to resources.yaml from the instructions b/c imo opening that file and modifying it is more confusing than helpful; feels like it makes more sense to create a new PipelineResource instance without bothering with that file.
3 tasks
tekton-robot
pushed a commit
that referenced
this pull request
Sep 14, 2020
In #3025 the nop-image was added to our release pipeline, this commit updates our README to include an example that sets it. Also removed the reference to resources.yaml from the instructions b/c imo opening that file and modifying it is more confusing than helpful; feels like it makes more sense to create a new PipelineResource instance without bothering with that file.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This should ensure that the nop-image is built and released alongside
other utility images.
Followup from #3014
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:
cmddir, 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
/assign @sbwsg