![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
Unassigned |
|
Components:
|
promoted-builds |
|
Created:
|
18/Apr/14 8:47 PM
|
|
Description:
|
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.
|
|
Environment:
|
Linux
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Bruce Edge
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
