Hi Chris, Why not simply avoid skip anything to do with the dependency graph in the case of a job with a variable in it? I understand that some features would not work, such as links to upstream/downstream jobs, but I think we'd gladly sacrifice that kind of thing for the benefit of being able to trigger jobs with variable names. Are there more critical features that would break?
On Thursday, March 7, 2013 6:57:41 AM UTC-6, cjo wrote: > > As the parameterized trigger plugin uses the dependency graph, this > feature is no longer working as the the dependencies are calculated when > the job is altered (modified, saved, other jobs deleted, etc) rather than > at build time. > The reason for this is that the build triggering occurs after all > publishers/notifiers finish with this solution, rather that doing it during > the publisher perform which can trigger the other builds before other > publishers are run which can cause issues. > > > I have been trying to think of a suitable way to bring this feature back > but haven't found a suitable solution with the dependency graph yet. > My current chain of thought is to have the dependency graph have > dynamic dependencies generated during a build that are a one time use. But > due to time constraints I have not yet mocked up any solutions. > > Chris > > > On Thursday, March 7, 2013 11:57:58 AM UTC, Fran Martín wrote: >> >> Michael, I have the same case. Do you know any update? >> >> Thanks, >> >> Fran >> >> On Wednesday, October 10, 2012 12:00:11 AM UTC+2, Michael C wrote: >>> >>> Hello, I have a question on how to use this feature of the Parameterized >>> Trigger Plugin: https://issues.jenkins-ci.org/browse/JENKINS-9391 >>> >>> I have tried to set the *Projects to build *field to an environment >>> variable, $JOB_TO_BUILD. It's set before the build kicks off: >>> >>> >>> <https://lh6.googleusercontent.com/-Zo3sJ6wiitc/UHSdRyCyLHI/AAAAAAAAAAM/5vsu3jkxm78/s1600/Screen+Shot+2012-10-09+at+4.54.30+PM.png> >>> and then I pass it off here: >>> >>> >>> <https://lh5.googleusercontent.com/-1mvJrc0cIMs/UHSd5F20xlI/AAAAAAAAAAU/-ef7lcz00wY/s1600/Screen+Shot+2012-10-09+at+4.57.00+PM.png> >>> (test.txt is generated during a build step.) >>> >>> So, if I ignore the form validation warning and save my job here, then >>> NO jobs are triggered at the end of a build. >>> >>> Why is this? What am I missing? >>> >> -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" 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.
