-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Validation for Task Result expression in Pipeline Results not working #4922
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
/assign |
/cc @jerop |
5 tasks
vsinghai
pushed a commit
to vsinghai/pipeline
that referenced
this issue
Jun 6, 2022
Prior to this commit, the validation for static strings for Task Result expressions in Pipeline Results was not extensive. This commit adds the case where a pipeline would be invalid if there is no expression following the valid form `$(tasks.<task-name>.results.<result-name>)`. Please reference this [doc](https://github.com/tektoncd/pipeline/blob/main/docs/pipelines.md#emitting-results-from-a-pipeline) for more information. Fixes bug [tektoncd#4922](tektoncd#4922)
vsinghai
pushed a commit
to vsinghai/pipeline
that referenced
this issue
Jun 8, 2022
Prior to this commit, the validation for static strings for Task Result expressions in Pipeline Results was not extensive. This commit adds the case where a pipeline would be invalid if there is no expression following the valid form `$(tasks.<task-name>.results.<result-name>)`. Please reference this [doc](https://github.com/tektoncd/pipeline/blob/main/docs/pipelines.md#emitting-results-from-a-pipeline) for more information. Fixes bug [tektoncd#4922](tektoncd#4922)
tekton-robot
pushed a commit
that referenced
this issue
Jun 8, 2022
Prior to this commit, the validation for static strings for Task Result expressions in Pipeline Results was not extensive. This commit adds the case where a pipeline would be invalid if there is no expression following the valid form `$(tasks.<task-name>.results.<result-name>)`. Please reference this [doc](https://github.com/tektoncd/pipeline/blob/main/docs/pipelines.md#emitting-results-from-a-pipeline) for more information. Fixes bug [#4922](#4922)
vsinghai
pushed a commit
to vsinghai/pipeline
that referenced
this issue
Jun 9, 2022
Prior to this commit, the validation for invalid `Task Result` expressions in `Pipeline` `Result`'s was not extensive. This commit adds the case where a `Pipeline` would be invalid if there is no expression following the valid form `$(tasks,<task-name>.results.<result-name>)`. Please reference this [doc](https://github.com/tektoncd/pipeline/blob/main/docs/pipelines.md#emitting-results-from-a-pipeline) for more information. Fixes bug [tektoncd#4922](tektoncd#4922) /kind bug /cc @jerop
5 tasks
vsinghai
pushed a commit
to vsinghai/pipeline
that referenced
this issue
Jun 9, 2022
Prior to this commit, the validation for invalid `Task Result` expressions in `Pipeline` `Result`'s was not extensive. This commit adds the case where a `Pipeline` would be invalid if there is no expression following the valid form `$(tasks,<task-name>.results.<result-name>)`. Please reference this [doc](https://github.com/tektoncd/pipeline/blob/main/docs/pipelines.md#emitting-results-from-a-pipeline) for more information. Fixes bug [tektoncd#4922](tektoncd#4922) /kind bug /cc @jerop
vsinghai
pushed a commit
to vsinghai/pipeline
that referenced
this issue
Jun 9, 2022
Prior to this commit, the validation for invalid `Task Result` expressions in `Pipeline` `Result`'s was not extensive. This commit adds the case where a `Pipeline` would be invalid if there is no expression following the valid form `$(tasks,<task-name>.results.<result-name>)`. Please reference this [doc](https://github.com/tektoncd/pipeline/blob/main/docs/pipelines.md#emitting-results-from-a-pipeline) for more information. Fixes bug [tektoncd#4922](tektoncd#4922) /kind bug /cc @jerop
tekton-robot
pushed a commit
that referenced
this issue
Jun 9, 2022
Prior to this commit, the validation for invalid `Task Result` expressions in `Pipeline` `Result`'s was not extensive. This commit adds the case where a `Pipeline` would be invalid if there is no expression following the valid form `$(tasks,<task-name>.results.<result-name>)`. Please reference this [doc](https://github.com/tektoncd/pipeline/blob/main/docs/pipelines.md#emitting-results-from-a-pipeline) for more information. Fixes bug [#4922](#4922) /kind bug /cc @jerop
@jerop I believe this issue can be closed now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
A
Pipeline's
Results
can be composed of one or manyTask
Results
emitted during thePipeline's
execution variables of the form$(tasks.<task-name>.results.<result-name>)
. If a variable passed toPipeline's
Results
does not take the expected form, thePipeline
validation should fail.For more information, please reference this doc
Example
Modified the
Pipeline
in the provided example as such:Actual Behavior
And this was the created
PipelineRun
, with theFinally Task
'sResult
passed on to thePipeline
:initialized-2
, which is a static string, is produced as is.initialized-3
, which is an invalid variable expression, is not produced and the pipeline does not fail.Steps to Reproduce the Problem
Pipeline
in the provided example with the code pasted abovekubectl apply -f pipelinerun-with-final-tasks.yaml
tkn pr describe -L
Additional Info
Here is a Related Bug
The text was updated successfully, but these errors were encountered: