Wouldn't you have the same requirement for deployments that are performed manually? If so, it would make more sense to put this into your deployment tool, not in Jenkins.
-- Dean On 4/19/12 1:26 AM , "Michele Sacchetti" <michele.sacche...@gmail.com> wrote: > Hi all > > I'd like to introduce a sort of external validation on jenkins build. > > Basically all I want to do is have people compile a "release form" on > a ticketing tool (redmine,RT,etc. i do not care) > Such ticketing tool can expose ticket status through web service/REST > so it can be checked by http. > > On jenkins i'd like to introduce a parametrized build in which ticket > number has to be provided. > Artifacts can be deployed (deploy/install goal) only if the ticket has > been approved, all other goals are unaffected. > > so basically I must introduce a step (the sooner the better, optimal > solution would be pre-checkout but it's not mandatory) which will > invoke an url, check the result and force the build to fail if needed. > > All this logic must be contained in jenkins not into the project to be > build (I have hundreds of them). > > is there a plugin I can already use for this ? > > thanks in advance
