-
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
[StepAction] taskSpec.results in Pipeline not works with workspaces #7754
Labels
kind/bug
Categorizes issue or PR as related to a bug.
Comments
Thanks for filing this bug @uqix The issue is the use of an emptyDir which inturn is added to the Step template and when merging Step with StepTemplate, we lose the Step's Results and Params. It's a quick fix that I will send in very shortly. |
Thanks, BTW, |
chitrangpatel
added a commit
to chitrangpatel/pipeline
that referenced
this issue
Mar 15, 2024
Prior to this, when we merged StepTemplate with the Spec, we would lose the Results and Params because the merged Step would overwrite the original Step. This PR adds the Results and Params when creating the new Step so that we don't lose this information. It fixes Issue tektoncd#7754 Signed-off-by: Chitrang Patel <chitrang@google.com>
8 tasks
Fix in #7757 |
tekton-robot
pushed a commit
that referenced
this issue
Mar 26, 2024
Prior to this, when we merged StepTemplate with the Spec, we would lose the Results and Params because the merged Step would overwrite the original Step. This PR adds the Results and Params when creating the new Step so that we don't lose this information. It fixes Issue #7754 Signed-off-by: Chitrang Patel <chitrang@google.com>
Fixed. |
3 tasks
tekton-robot
pushed a commit
to tekton-robot/pipeline
that referenced
this issue
Mar 27, 2024
Prior to this, when we merged StepTemplate with the Spec, we would lose the Results and Params because the merged Step would overwrite the original Step. This PR adds the Results and Params when creating the new Step so that we don't lose this information. It fixes Issue tektoncd#7754 Signed-off-by: Chitrang Patel <chitrang@google.com>
tekton-robot
pushed a commit
that referenced
this issue
Mar 27, 2024
Prior to this, when we merged StepTemplate with the Spec, we would lose the Results and Params because the merged Step would overwrite the original Step. This PR adds the Results and Params when creating the new Step so that we don't lose this information. It fixes Issue #7754 Signed-off-by: Chitrang Patel <chitrang@google.com>
l-qing
pushed a commit
to katanomi/pipeline
that referenced
this issue
Apr 29, 2024
Prior to this, when we merged StepTemplate with the Spec, we would lose the Results and Params because the merged Step would overwrite the original Step. This PR adds the Results and Params when creating the new Step so that we don't lose this information. It fixes Issue tektoncd#7754 Signed-off-by: Chitrang Patel <chitrang@google.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
taskSpec.results
inPipeline
works withworkspaces
andStepAction
.Actual Behavior
taskSpec.results
inPipeline
not works withworkspaces
.No results generated.
Steps to Reproduce the Problem
Additional Info
Kubernetes version:
Output of
kubectl version
:Tekton Pipeline version:
Output of
tkn version
orkubectl get pods -n tekton-pipelines -l app=tekton-pipelines-controller -o=jsonpath='{.items[0].metadata.labels.version}'
The text was updated successfully, but these errors were encountered: