Set HOME="/tekton/home" for GCS PipelineResources #4081
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes
Dashboard noticed their nightly release pipeline no longer worked
after a Pipelines upgrade in dogfooding. They tracked it to use of a GCS
pipeline resource; adding a HOME="/tekton/home" env var to the Task's
PodTemplate resolved the issue.
Prior to this commit the GCS PipelineResource didn't get its HOME
explicitly set to /tekton/home.
After this commit the GCS PipelineResource always includes this env var in
the pre- and post- containers it adds to Task pods.
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
functionality, content, code)
Release Notes
/kind bug