[JIRA] [promoted-builds] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Steve Jansen commented on JENKINS-22679 Regression, Promoted builds plugin not expanding job parameters on immediate promote after build. Confirmed reverting to 2.16 fixes the problem for me. 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.
[JIRA] [promoted-builds] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Robert Liotta commented on JENKINS-22679 Regression, Promoted builds plugin not expanding job parameters on immediate promote after build. Hello. I just updated to the 2.18 SNAPSHOT that was posted a few days back to fix the re-execute button. I have now run into this issue. Will this get fixed for 2.18? 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.
[JIRA] [promoted-builds] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Wilco Greven
commented on JENKINS-22679
Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
This seems to be caused by the fix for JENKINS-22005. I can reproduce the issue using the following steps:
1) Create a job job1 with a string parameter named param1.
2) Create a job job2 with a string parameter named param1.
3) Create a job job3 with a string parameter named param1.
4) Add a promotion process promotion1 to job3 with criteria 'Only when manually approved'. Add an action 'Trigger parameterized build on other projects' to the promotion that triggers job1 with predefined parameters 'param1=${param1}'.
5) Add a promotion process promotion2 to job3 with criteria 'When the following downstream projects build successfully' on downstream project job1. Add an action 'Trigger parameterized build on other projects' to the promotion that triggers job2 with predefined parameters 'param1=${param1}'.
6) Run job3 with param1=someString.
7) Manually approve promotion1. You will see that job1 is correctly run with param1=someString.
8) Promotion process promotion2 will automatically run job2. But job2 will be run with param1=${param1} which is not correct.
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.
[JIRA] [promoted-builds] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Wilco Greven
edited a comment on JENKINS-22679
Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
This seems to be caused by the fix for JENKINS-22005. I can reproduce the issue using the following steps:
1) Create a job job1 with a string parameter named param1.
2) Create a job job2 with a string parameter named param1.
3) Create a job job3 with a string parameter named param1.
4) Add a promotion process promotion1 to job3 with criteria 'Only when manually approved'. Add an action 'Trigger parameterized build on other projects' to the promotion which triggers job1 with predefined parameters 'param1=${param1}'.
5) Add a promotion process promotion2 to job3 with criteria 'When the following downstream projects build successfully' on downstream project job1. Add an action 'Trigger parameterized build on other projects' to the promotion which triggers job2 with predefined parameters 'param1=${param1}'.
6) Run job3 with param1=someString.
7) Manually approve promotion1. You will see that job1 is correctly run with param1=someString.
8) Promotion process promotion2 will now automatically start job2. But job2 will be run with param1=${param1} which is not correct.
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.
[JIRA] [promoted-builds] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Wilco Greven
edited a comment on JENKINS-22679
Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
This seems to be caused by the fix for JENKINS-22005. I can reproduce the issue using the following steps:
1) Create a job job1 with a string parameter named param1.
2) Create a job job2 with a string parameter named param1.
3) Create a job job3 with a string parameter named param1.
4) Add a promotion process promotion1 to job3 with criteria 'Only when manually approved'. Add an action 'Trigger parameterized build on other projects' to the promotion which triggers job1 with predefined parameters 'param1=${param1}'.
5) Add a promotion process promotion2 to job3 with criteria 'When the following downstream projects build successfully' on downstream project job1. Add an action 'Trigger parameterized build on other projects' to the promotion which triggers job2 with predefined parameters 'param1=${param1}'.
6) Run job3 with param1=someString.
7) Manually approve promotion1. You will see that job1 is correctly run with param1=someString.
8) Promotion process promotion2 will automatically run job2. But job2 will be run with param1=${param1} which is not correct.
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.
[JIRA] [promoted-builds] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Wilco Greven
edited a comment on JENKINS-22679
Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
This seems to be caused by the fix for JENKINS-22005. Reverting to 2.16 fixes the problem. I can reproduce the issue using the following steps:
1) Create a job job1 with a string parameter named param1.
2) Create a job job2 with a string parameter named param1.
3) Create a job job3 with a string parameter named param1.
4) Add a promotion process promotion1 to job3 with criteria 'Only when manually approved'. Add an action 'Trigger parameterized build on other projects' to the promotion which triggers job1 with predefined parameters 'param1=${param1}'.
5) Add a promotion process promotion2 to job3 with criteria 'When the following downstream projects build successfully' on downstream project job1. Add an action 'Trigger parameterized build on other projects' to the promotion which triggers job2 with predefined parameters 'param1=${param1}'.
6) Run job3 with param1=someString.
7) Manually approve promotion1. You will see that job1 is correctly run with param1=someString.
8) Promotion process promotion2 will now automatically start job2. But job2 will be run with param1=${param1} which is not correct.
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.
[JIRA] [promoted-builds] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Bruce Edge commented on JENKINS-22679 Regression, Promoted builds plugin not expanding job parameters on immediate promote after build. Problem still exists in jenkins update site. What's needed to get the above merge pull into the global plugin update site? 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.
[JIRA] [promoted-builds] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Jamey Graham commented on JENKINS-22679 Regression, Promoted builds plugin not expanding job parameters on immediate promote after build. or, instead of building... http://updates.jenkins-ci.org/download/plugins/promoted-builds/2.15/promoted-builds.hpi https://wiki.jenkins-ci.org/display/JENKINS/Plugins#Plugins-Byhand 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.
[JIRA] [promoted-builds] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Bruce Edge commented on JENKINS-22679 Regression, Promoted builds plugin not expanding job parameters on immediate promote after build. Confirmed that reverting to 2.15 fixes the problem. For anyone else hitting this, download the source from here: https://github.com/jenkinsci/promoted-builds-plugin/archive/promoted-builds-2.15.tar.gz unpack, mvn clean package, then copy promoted-builds-plugin-promoted-builds-2.15/target/promoted-builds.hpi to JENKINS_ROOT/plugins.promoted-builds.jpi note the extension change. 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.
[JIRA] [promoted-builds] (JENKINS-22679) Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Bruce Edge
created JENKINS-22679
Regression, Promoted builds plugin not expanding job parameters on immediate promote after build.
Issue Type:
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
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.
