Hi Stephen, Is the literate plugin going to be the only route into the multi-branch 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 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...) /James On Friday, 20 September 2013 10:16:47 UTC+1, Stephen Connolly wrote: > > Ok! > > This is the first bit of noise about this. I'll be writing up a series of > blog posts around this, but as I just got everything OSS I thought that > some of the more adventurous amongst you may want to start playing with it > now. > > To play with this you need to do the following: > > 1. Checkout and build (mvn install) the branch-api-plugin > 2. Checkout and build (mvn package) the literate-plugin > 3a. Checkout and build (mvn package) the git plugin (either the master or > the refactoring branch... pick your poison) > 3b. Checkout and build (mvn package) the subversion plugin (the > refactoring branch) > 3c. Checkout and build (mvn package) the mercurial plugin > > In your Jenkins 1.509+ install the three (or more) plugins that you have > just built > > You should now be able to create literate multi-branch projects. > > To try it out. > > In your SCM system create a project. In the root of the project put the > following two files: > > $ touch .cloudbees.md > cat - > README.md <<EOF > Hello World project > ============== > > How to Build > ------------------ > > echo 'Hello world' > > EOF > > Checkin these two files. Create a literate multi-branch project with your > project as a source. Trigger the indexing. You should see a sub-project for > the main branch of the project. > > *NOW* go and fork your main branch into another branch. > > Trigger indexing again... oh look that branch has a project too. > > Have fun. > > The 10 best bug reports will be getting at least a T-shirt from CloudBees, > but I am hoping to improve the swag that I can offer. > > -Stephen > > P.S. There will be an update centre that allows people to pull this > without building themselves... and there will be a blog post later today > detailing more of the fun you can do! > > P.P.S. The aim is to have enough people test this that it can be > considered GA ready for JUC in late Oct 2013 > > P.P.P.S. Many thanks to my employers (CloudBees) for funding the > development of this fully open source (MIT license) feature for Jenkins... > the only "cost" is that the default marker file is called .cloudbees.md! > -- 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.
