You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When PipelineRun params are updated, the PipelineRuns .spec is updated, and the PipelineRun is re-run, creating new TaskRuns and pods, and finally the .status is updated.
OR
The PipelineRun .spec (or at least params) are immutable, because once created the parameters cannot be reconciled
Actual Behavior
The PipelineRuns .spec is updated, but never reconciled and re-run. The PipelineRun .status remains with details of the PipelineRun run using the old parameters.
Thanks @jimmyjones2 - a PipelineRuns cannot be "re-run" - PipelineRuns are by design associated one-by-one with executions of pipelines.
We could prevent updates to the spec in *Run resources though - I believe it should be doable via the validating webhook. @tektoncd/core-maintainers WDYT?
We could prevent updates to the spec in *Run resources though - I believe it should be doable via the validating webhook. @tektoncd/core-maintainers WDYT?
Expected Behavior
When PipelineRun params are updated, the PipelineRuns
.spec
is updated, and the PipelineRun is re-run, creating new TaskRuns and pods, and finally the.status
is updated.OR
The PipelineRun
.spec
(or at least params) are immutable, because once created the parameters cannot be reconciledActual Behavior
The PipelineRuns
.spec
is updated, but never reconciled and re-run. The PipelineRun.status
remains with details of the PipelineRun run using the old parameters.Steps to Reproduce the Problem
IMAGE
Additional Info
Kubernetes version:
Output of
kubectl version
:The text was updated successfully, but these errors were encountered: