|
||||||||
|
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.
Hey Patrik,
I have a particular build scenario would make what I'm trying to do work (Note that my example is fictitious just to get my idea accross).
I have a matrix job with a 'User Defined Axis' named 'arguments.' Arguments has two values ('arg1' 'arg2'). The matrix job triggers a parameterized job (let's call this 'param_job') for each value of 'arguments' and passes the AXIS value as a parameter. 'param_job' has it's 'stage' set to 'deploy' and it's 'task' set to '$arguments'.
Right now when I look at the dashboard with the matrix job as the starting job it looks like this:
(matrix_job) -> param_job(stage: deploy, task: $arguments)
The issue here is that this doesn't show that matrix_job kicked of two builds of param_job.
Once this fix is in, should I expect the dashboard to show this:
(matrix_job) -> param_job(stage: deploy, task: arg1)
-> param_job(stage: deploy, task: arg2)