I'm volunteer tout take the maintainer role, until someone else is interested. Le 8 oct. 2014 11:45, "Stephen Connolly" <[email protected]> a écrit :
> Fine Jesse, you win... I have released the source code for my mythical > Freestyle Multibranch Project type: > > https://github.com/jenkinsci/freestyle-multibranch-plugin > https://wiki.jenkins-ci.org/display/JENKINS/Freestyle+Multibranch+Plugin > > Background > ========= > > Back in 2011 I got fed up with the stupid way the git plugin built > multiple branches. I wanted to be able to see the history for each branch > independently. I wanted to not have to go and create/copy a new job for > each branch. I said: "screw this shit... there must be a better way" > > So I did some hacking in my spare time and came up with a freestyle > multibranch project type... but my OCD kicked in and I didn't like that > configuring this project type littered the log files with NPEs... and I > couldn't figure out a hack to fix it... > > And of course I also realised that you usually need a different build > configuration for different branches which kind of negates the > cookie-cutter model in this project type. > > So then I decided that the most important thing (a.k.a. the crux) is that > there should be a single file in source control that says how to build the > project... which is where literate came from. > > But while refactoring everything to make Literate, I did keep the > freestyle multibranch project type current with the refactoring. > > Announcement > ============ > > Are you looking for a Jenkins plugin to maintain? > > Are you interested in the multi-branch style of projects? > > Are you not interested in a file in source control that describes how the > project should be built but rather prefer to configure everything from the > Jenkins UI? (note that literate does not force that file to be written in > markdown... it even ships with a *very* limited .travis.yml parser... if > you want to have the build configuration defined by a file in SCM, then > providing alternative parsers to the literate-api is the way to get > involved in that) > > Well here is your lucky day! > > I am throwing away this code. You can now take up the baton and forge > forward... > > Infamy, riches and the worship of whatever gender you are attracted to > awaits... all you need to do is step up and become a maintainer. > > -Stephen > > -- > 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/d/optout. > -- 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/d/optout.
