Skip to content
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鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

SetDefaults for embedded specs (Pipeline, Task) 馃 #2162

Merged

Conversation

vdemeester
Copy link
Member

@vdemeester vdemeester commented Mar 5, 2020

Changes

Embedded TaskSpec and PipelineSpec were not being set defaults when
the resource embedding it was. This fixes that.

Signed-off-by: Vincent Demeester vdemeest@redhat.com

/cc @sbwsg @bobcatfish
Fix #2157

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:

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

Fix defaults not being applied for embedded Pipeline(s) and Task(s)

Embedded TaskSpec and PipelineSpec were not being *set defaults* when
the resource embedding it was. This fixes that.

Signed-off-by: Vincent Demeester <vdemeest@redhat.com>
@tekton-robot tekton-robot requested review from bobcatfish and a user March 5, 2020 08:04
@googlebot googlebot added the cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit label Mar 5, 2020
@tekton-robot tekton-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Mar 5, 2020
@vdemeester vdemeester added the kind/bug Categorizes issue or PR as related to a bug. label Mar 5, 2020
@tekton-robot
Copy link
Collaborator

The following is the coverage report on pkg/.
Say /test pull-tekton-pipeline-go-coverage to re-run this coverage report

File Old Coverage New Coverage Delta
pkg/apis/pipeline/v1alpha1/pipelinerun_defaults.go 100.0% 93.8% -6.2
pkg/apis/pipeline/v1beta1/pipeline_defaults.go 0.0% 33.3% 33.3

@vdemeester
Copy link
Member Author

Will need to get cherry-pick in a 0.11 branch. I feel we need a label for this 馃懠

@vdemeester
Copy link
Member Author

/test pull-tekton-pipeline-integration-tests

@tekton-robot
Copy link
Collaborator

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 /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 5, 2020
@pritidesai
Copy link
Member

/lgtm

Thanks @vdemeester 馃憤

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Mar 5, 2020
@tekton-robot tekton-robot merged commit b7208c4 into tektoncd:master Mar 5, 2020
@vdemeester vdemeester deleted the 2157-set-defaults-embedded branch March 5, 2020 16:57
@vdemeester vdemeester added the needs-cherry-pick Indicates a PR needs to be cherry-pick to a release branch label Mar 6, 2020
@ghost ghost removed the needs-cherry-pick Indicates a PR needs to be cherry-pick to a release branch label Mar 9, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Trying to make the CLA bot happy with ppl from different companies work on one commit kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Validation on Embedded PipelineSpec different from stand-alone Pipeline spec
4 participants