![]() |
|
|
|
|
Issue Type:
|
Bug
|
|
Affects Versions:
|
current |
|
Assignee:
|
huybrechts
|
|
Components:
|
parameterized-trigger |
|
Created:
|
06/Feb/13 9:25 AM
|
|
Description:
|
This is similar to issue #11082, issue #9263, issue #5184.
The only difference is how the "Projects to build" value is set.
In my case I build an environment variable "$TO_TRIGGER" dynamically and simply put it in the text box, "parameterized trigger" does the job of expanding it to the job names well. The only problem is that although the projects are triggered and in the console log it is listed as if they were triggered successfully, see log:
Waiting for the completion of trigger1
trigger1 trigger1----#2 completed. Result was SUCCESS
Build step 'Trigger/call builds on other projects' changed build result to SUCCESS
Finished: SUCCESS
They still don't appear as downstream builds, nor do they upstream build appear as upstream build in the downstream build.
|
|
Project:
|
Jenkins
|
|
Priority:
|
Major
|
|
Reporter:
|
Benjamin Kemper
|
|
|
|
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
[email protected].
For more options, visit
https://groups.google.com/groups/opt_out.