On Thursday, 3 October 2013 20:37:27 UTC+1, Stephen Connolly wrote: > > > > On Thursday, 3 October 2013, teilo wrote: > >> Hi Stephen, >> >> Is the literate plugin going to be the only route into the multi-branch >> job? >> >> > I am sure somebody may use the branch api to implement other types... I > have a freestyle multi branch but there is just too many build differences > for it to be useful and a ton of UI glitches because plugins assume they > are owned by <? extends Job> > > > >> Reason being for enterprisy software we need to enforce things in a >> build/release so I can't let my users run abitrary maven invocations that >> change the build (and make it unreproduceable). >> >> e.g. they should not be able to change the settings by using mvn -s >> $workspace/some_setting_with_external_repo.xml -DskipTests=true >> > > But they can just change the pom to skip tests anyway... You have a false > sense of security... >
That was a bit of a bad example - but actually if they want to skip tests in the POM then that is 100% ok - as we know that the tests were not run on a specific build. > > And if they want to use a different settings... Invoker and an alternative > pom file. > > But you are assuming my maven enforcer rules etc. are the only line of defence here. The MRM can also play an important part :-) Besides that can you configure things that are not reporters? e.g. wipe out workspace, always checkout a fresh copy, enable a release plugin... > Plus you can just watch what shit they are committing... You need to do > that with the poms anyway > No I can't (and actually I don't). If I could do that then we wouldn't need the Template plugin as I could watch all Jenkins job creation :-) You are correct in that there is a little bit of an arms race going on - but most of this is not actively trying to create non-repeatable builds - it's just people not always thinking things through and the system can probably automatically pick up 95+% of that. There are several thousand projects+branches - it would take a full time person to watch all of that - you could say that this could be somewhat automated - but even that has human overhead to setup these jobs when new projects are added, maintain mapping of project/branch to user+manager mapping etc... > > >> >> but at the same time its nice that you just branch and get a job (from >> say a job that's created from some kind of template, and that should allow >> the user to specify the properties exposed by that template only...) >> >> (you haven't yet beaten my addiction to the maven job type...) >> > > I'm not done... There are more tricks up my sleeve > -- 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.
