There is a simple step available in the worfklow plugin called input. https://github.com/jenkinsci/workflow-plugin/blob/master/TUTORIAL.md#pausing-flyweight-vs-heavyweight-executors But it would require your job to be a worfklow job and does not support a very sophisticated input form, AFAIK.
On Friday, July 31, 2015 at 10:09:23 AM UTC-7, Peter Hayes wrote: > > Hi, > > I am doing a proof of concept of codifying our delivery pipeline within > Jenkins. We have a number of our stages automated but we do have a couple > stages that require manual inspection of the software. I was thinking that > it would be cool if there was a build step type that you could configure > for a job (call the job manual-testing) and when run, the job would > essentially pause waiting for user input that the manual testing completed. > The confirmation screen would accept file uploads to the workspace, the > build result, and a log entry. When submitted, the job would then continue > with post build actions as a normal fully automated job execution would. It > could then generate reports and fit nicely into the overall delivery > pipeline. > > I did some plugin searching and came up empty - could mean I am out in > left field on this, but the more I think about it the more interested I am > in having this capability. Does anyone know if something like this exists? > > Thanks, > Pete > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-users/8610e7d8-663f-41f4-9910-09d7d2dd7ec6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
