-
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
Support context variable replacements in custom tasks #6620
Conversation
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
There seems to be a flake with the git-resolver pipeline-integration-test which I've filed an issue for here: #6626 /retest |
43c2625
to
07da08d
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please add a test where a custom task uses context variables to ensure they are replaced 🙏🏾
07da08d
to
cc8cca4
Compare
@jerop Added a context param for Custom Tasks in testing. |
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/retest |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @EmmaMunley!
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jerop 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 |
@EmmaMunley please update the docs to indicate that custom tasks do take context variables - https://github.com/tektoncd/pipeline/blob/main/docs/pipelines.md#using-custom-tasks |
cc8cca4
to
b22f171
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
b22f171
to
32b2180
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like this is a user facing bug fix; i.e. we now support context variable replacement in custom tasks in inline pipeline specs. Can you please focus the commit message and PR title more on the user impact? I found it hard to understand from the title/description what the changes were and why they were being made. This also needs a release note.
This commit enables adds support for context variable replacements, allowing users to define context variables in inline pipeline specs for custom tasks. Prior to this, context variable replacements were only supported for non-custom tasks.
32b2180
to
f9d66ae
Compare
The following is the coverage report on the affected files.
|
The following is the coverage report on the affected files.
|
/lgtm |
@EmmaMunley: The
The following commands are available to trigger optional jobs:
Use In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/retest |
Changes
This PR adds support for context variable replacements, allowing users to define context variables in inline pipeline specs for custom tasks. Prior to this PR, context variable replacements were only supported for non-custom tasks.
/kind bug
Submitter Checklist
As the author of this PR, please check off the items in this checklist:
/kind <type>
. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tepRelease Notes