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’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Propagate TaskRunSpecs to created TaskRuns #2683

Conversation

jlpettersson
Copy link
Member

@jlpettersson jlpettersson commented May 23, 2020

Changes

TaskRunSpec set in PipelineRun is never propagated to new TaskRuns in createTaskRun(), they are only propagated to Condition-pods in makeConditionCheckContainer()

This commit

  • Adds propagation to new TaskRuns
  • Also adds a unit test

Also, now when this is implemented, the example with a custom NodeSelector will not work on our infrastructure, so I moved it to no-ci/

  message: 'pod status "PodScheduled":"False"; message: "0/3 nodes are available:
   3 node(s) didn''t match node selector."'
   reason: Pending

Fixes #2682

/kind bug

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 missing propagation of TaskRunSpecs to created TaskRuns

@tekton-robot tekton-robot added the kind/bug Categorizes issue or PR as related to a bug. label May 23, 2020
@tekton-robot tekton-robot requested review from imjasonh and a user May 23, 2020 20:15
@tekton-robot tekton-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label May 23, 2020
@tekton-robot
Copy link
Collaborator

This PR cannot be merged: expecting exactly one kind/ label

Available kind/ labels are:

kind/bug: Categorizes issue or PR as related to a bug.
kind/flake: Categorizes issue or PR as related to a flakey test
kind/cleanup: Categorizes issue or PR as related to cleaning up code, process, or technical debt.
kind/design: Categorizes issue or PR as related to design.
kind/documentation: Categorizes issue or PR as related to documentation.
kind/feature: Categorizes issue or PR as related to a new feature.
kind/misc: Categorizes issue or PR as a miscellaneuous one.

@tekton-robot
Copy link
Collaborator

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

File Old Coverage New Coverage Delta
internal/builder/v1beta1/pipeline.go 83.0% 82.0% -1.0
internal/builder/v1beta1/task.go 76.2% 75.5% -0.7
pkg/reconciler/pipelinerun/pipelinerun.go 75.3% 75.3% 0.1

@jlpettersson
Copy link
Member Author

/test pull-tekton-pipeline-integration-tests

TaskRunSpec set in PipelineRun is never propagated to new TaskRuns in `createTaskRun()`, they are only propagated to Condition-pods in `makeConditionCheckContainer()`

This commit
- Adds propagation to new TaskRuns
- Also adds a unit test

Fixes tektoncd#2682

/kind bug
@jlpettersson jlpettersson force-pushed the propagate_pipelinetaskrunspec_to_taskruns branch from 8f7e718 to 358a0c2 Compare May 23, 2020 21:32
@tekton-robot
Copy link
Collaborator

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

File Old Coverage New Coverage Delta
internal/builder/v1beta1/pipeline.go 83.0% 82.0% -1.0
internal/builder/v1beta1/task.go 76.2% 75.5% -0.7
pkg/reconciler/pipelinerun/pipelinerun.go 75.3% 75.3% 0.1

Copy link
Member

@vdemeester vdemeester left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/cc @sbwsg @dibyom

@tekton-robot tekton-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 2, 2020
@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 Jun 2, 2020
@vdemeester
Copy link
Member

/test pull-tekton-pipeline-integration-tests

@tekton-robot tekton-robot merged commit be9ac3b into tektoncd:master Jun 2, 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. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TaskRun creation fails, created from PipelineRun with TaskRunSpec
3 participants