-
Bug
-
Resolution: Unresolved
-
Critical
-
None
-
Linux
Up until upgrading to 2.17 I could reference my build parameters (from "This build is parameterized" section). Now these parameters are silently replace with empty strings when the promotion is run automatically after the build.
If I run the promotion again, it works.
From the promotion job:
${RELEASES}/${PROMOTED_NUMBER}/${CONFIG}/develop-${CONFIG}-${PROMOTED_NUMBER}.ipa
I logged the env for a promotion run immediately after and one run later manually.
For the immediate case, all my parameters above, CONFIG, RELEASES are null whereas they are correct for the later manual invocation.
Note that promoted builds specific parameters are OK, it's just all the rest that are not.
What makes this worse is that the jenkins updater doesn't offer a downgrade option for this plugin.
- is duplicated by
-
JENKINS-22094 Promoted builds not picking up injected env settings as of 2.17 (2.15 is ok)
- Closed
- is related to
-
JENKINS-27883 PROMOTED_* variables not exposed to all promoted build actions
- Open
-
JENKINS-14169 Injected env variables not available for use in processing promotion.
- Resolved