Hi Am 08.10.2013 21:30, schrieb Kohsuke Kawaguchi: >> need to add a new entry to the list of options for a parameterized >> build. That's >> not the problem and all necessary configuration options are already >> implemented >> and usable. >> >> Now I'm struggling with the problem, that there must be some steps >> performed >> between the click on "Build with parameters" to start the job and the >> next step >> which shows the parameter screen. To be more detailed, my plugin needs to >> prepare a list of options, from which the user who triggers the build, >> must >> choose one. This list can only be prepared after starting the job, so >> no chance >> to setup it during job configuration. > > I'm bit confused here.
Thx for your respone, seem's I should explain a little bit more. See below. > The former part of this seems to imply that you just want some > multi-page wizard to fill in parameters. I wonder you can effectively > achieve the same result by having some controls update its options based > on the selection of other controls. There's a number of places in > Jenkins that does this, and UI samples plugin has a good example of this. > > The latter part seems to indicate that you want to pause the build after > it gets going, to receive human input. Then you can bring the build to > the completion. > > Jenkins isn't really good at suspending a build in progress, in the > sense that it'd waste precious executor, but that can be done from a > BuildStep. I do this in > https://wiki.jenkins-ci.org/display/JENKINS/Remote+Terminal+Access+Plugin to > prevent the build from getting completed. I do not need to pause a build as it isn't started yet!? Let me explain more detailed: I need to configure a build job as a parameterized build. The new option (implemented by my plugin) will get an URL on the job configuration page. If the buildjob is startet by clicking the corresponding button "Build with Parameters", you see the intermediate page "This build requires parameters:". Until this point, the job is not started and no executor is wasted, isn't it? And exactly on this point, I'd like to view a list of entries, which my plugin extracts from the configured URL. These list needs to be generated dynamically, so it can't be configured on job configuration using another parameter option like "Choice". >> Until now I'm unable to find out, how to do this. Maybe it's too easy >> but please >> let me know how to trigger code on my plugin implementation right between >> triggering the job but before the parameter screen is opened. Thx a >> lot in advance. Kind regards, Yves -- 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.
