I have to do this with one of our processes as well, this is basically what I do: - The main job has 3 promotion criteria, RegressionsPassed, ComparePassed, CompareApproved. - The CompareApproved is a "manual" promotion - This job triggers all the regressions - Have a job called 'compare', which is triggered with a join from the main job. - Itdoes the compare of the latest output to the "golden" output, if it's different then it generates a report of the differences, and the job goes unstable - The developer is required to review the report, and if it looks good, they run the CompareApproved promotion, which run's another job called 'approve' which copies the latest files to the golden copy (and these files are in svn so we have a history)
That's the basics, if you need more info let me know. - Jim On Wed, Jun 20, 2012 at 9:07 PM, Bopolissimus X Platypus <[email protected]> wrote: > On Wed, Jun 20, 2012 at 12:40 PM, Richard Lavoie > <[email protected]> wrote: >> What you could do is probably look at the "promoted builds" plugin, where a >> human can actually promote a build after a manual review. I've never tried >> it tho but it looks like doing a promotion on some criterions. Take a look, >> that might be your solution. > > Thank you Richard. Haven't tried it yet, but that does look good. > > Gerald
