Darrel: In our case, a local best practice is for the various developers to configure their build projects to use the same upstream job (let's call it "common_build_prologue"), and not try to bypass it or substitute their own variant of it. I'm looking for a capability that could warn a user (in the console output, say) if s/he neglected to use the "standard" pre-build logic.
On Thursday, August 21, 2014 11:26:45 AM UTC-6, DarrelVun wrote: > > I'd expect you'd want an *overt* step so that users know they should > follow your local best practices. > > My group loves the pre-scm build step ( > https://wiki.jenkins-ci.org/display/JENKINS/pre-scm-buildstep) for checks > before the build starts. > > Regards, > Darrel V. > > On Wednesday, August 20, 2014 1:44:41 PM UTC-4, G Dameron wrote: >> >> Is it possible to configure a pre-build (or post-build) script that runs >> by default before (after) any job, even newly-created ones? The idea is to >> do some checks that ensure all users' projects are adhering to local best >> practices. >> > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
