I've set up some thing like that, Basically the first job in the chain asks all the questions about tasks to builds, are artifacts required, etc via parameters.
Does some basic checking (tasks correct, do they exist) and creates a summary of this information. If this checking passes, it creates a property file that is passed to all downstream jobs, via the parametrized trigger plugin All further jobs then reference this file (can be accessed from scripts or added to the build env using envinject plugin) If you want to prevent jobs 2-N being started manually, use the role strategy plugin to block who can start these. https://wiki.jenkins-ci.org/display/JENKINS/Role+Strategy+Plugin I don't personally use this as we are a small team of 8 people who use the service and don't mess around things they don't need to. Chris On Friday, June 15, 2012 4:39:20 PM UTC+1, shanz wrote: > > At the moment I am resigned to defeat so I've got a slightly underwhelming > plan B. > I can put a hyperlink in the description of job1 as follows > Once complete manually continue by clicking here :- > <a href="http://localhost:8086/jenkins/job1/build";> > http://localhost:8086/jenkins/job1/build</a> > > On Friday, June 15, 2012 4:08:51 PM UTC+1, shanz wrote: >> >> I split the whole project into jobs for convenience only, there is >> nothing special about having separate jobs. >> Job 1 is triggered by a user but then all the subsequent jobs just follow >> the previous job automatically. >> I guess the original user would be the one to prompt in their browser. >> >> >> On Friday, June 15, 2012 3:47:27 PM UTC+1, (unknown) wrote: >>> >>> Can you explain what you want to happen? If you are talking about a >>> job that is triggered by a previous job, rather than by a user, who do you >>> want to ask for input? There is no user to ask. >>> >>> >>> >>> I guess the question is, how are the consecutive jobs being run at the >>> moment? >>> >>> >>> >>> *From:* jenkinsci-users@googlegroups.com [mailto: >>> jenkinsci-users@googlegroups.com] *On Behalf Of *shanz >>> *Sent:* 15 June 2012 15:30 >>> *To:* jenkinsci-users@googlegroups.com >>> *Subject:* User Prompts >>> >>> >>> >>> I know I can use the Parameterized Builds plugin to prompt for user >>> input however this only works for the initial job. >>> I want to ask for user input (eg: Boolean tick box - have you done >>> xyz?), in a job which is in the middle of a list of consecutive jobs. >>> Is this possible? >>> >>
