-
Notifications
You must be signed in to change notification settings - Fork 96
[JENKINS-62014] Add support for build step environment filters #124
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
Conversation
|
Wasn't me: |
|
That's really strange this issue is showing up again. The issue I ran into was because of the loading order of |
|
Weird, these commits are in my history -- this PR is based off of latest master. |
|
Re-ran and it fixed a bunch of tests, but the quoted one remains. |
|
I wonder if the |
|
This looks good, though I'm not an expert in this area. I'm not able to get the tests to complete locally. It seems to just hang on BourneShellScriptTest. |
| <jenkins.version>2.236-rc29908.d71e7c850809</jenkins.version> | ||
| <java.level>8</java.level> | ||
| <binary.src>src/main/go/org/jenkinsci/plugins/durabletask</binary.src> | ||
| <useBeta>true</useBeta> |
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.
I'm not sure about the best approach here. It doesn't seem wise to use this flag. It's a big switch and can hide other potential issues.
I guess this can't be merged until after all supported versions have the new API anyway. We've got enough pieces involved here and demonstrations of behavior that the Beta restriction doesn't help. The purpose is to make these API changes available and then use them as soon as possible. Marking them as Beta, waiting for propagation, and then removing the restriction, and waiting for further propagation makes little sense.
|
I tested basic operations with a few different configurations. Everything worked as expected. The console log messages are a little weird, but it looks like they don't originate here. This PR could use an improved description of what it adds and how it needs to be tested. |
|
Latest failures look like flaky infra issues, rebuilding:
|
|
Looks like #125 should fix the CI build. |
|
Rebuilding to pick up #125. |
|
On-holding due to feedback in downstream PR. |
See JENKINS-62014.
This adds support for global build step environment filters to durable task based pipeline steps.
Downstream from jenkinsci/jenkins#4683.
Upstream from jenkinsci/workflow-durable-task-step-plugin#135.