Issue Type: New Feature New Feature
Affects Versions: current
Assignee: huybrechts
Components: parameterized-trigger
Created: 25/Apr/13 5:08 PM
Description:

When "Trigger a parameterized build" is used in a promotion step, there is no link to the parameterized build that was actually started.

In the promotion, it looks like this following:

Building on master in workspace /var/lib/jenkins/jobs/Main Build/workspace
Promoting Main Build #222
build hudson.plugins.parameterizedtrigger.BuildTrigger@25765df0 SUCCESS
Marking build to keep forever.
build hudson.plugins.promoted_builds.KeepBuildForeverAction@7e114ac6 SUCCESS
Finished: SUCCESS

The parameterized trigger succeeded, and the build started. But, in the build that is triggered, you get this:

Started by upstream project "Main Build/promotion/Triggered Build" build number 32
originally caused by: Legacy code started this job. No cause information is available

There are no actual links between the build that was promoted, and the build that was triggered by the promotion.

I think it would be very useful if there were links between the 2, in the same way that upstream / downstream builds are linked such that you can figure out which build caused another build.

Environment: Linux
Project: Jenkins
Labels: plugin parameterized
Priority: Major Major
Reporter: Greg Smith
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/groups/opt_out.
 
 

Reply via email to