Because you probably don't want to couple your source code too strongly to your SCM.
Of course the breakthrough from my PoV is that you always want a README in SCM that says what the build command(s) is/are (hopefully it's a single command, but sometimes you need a couple of them) Hijacking the README to infer the build command thus is much better IMHO than reading an 80 page spec and deciphering a pile of different "magic" defaults based on what values you put in a config file. The .jenkins directory is thus more about giving Jenkins some metadata about the build output, it doesn't interfere if you want to change CI system, and it is not critical for a build+test verification build. If you want to try another CI system the .jenkins directory should not get in your way. Finally the marker file is all about identifying the branches to build without having to visit the UI... And since we have that file we can use it (if non empty) as a replacement for the README if you want to tweak the CI build >From my PoV this is all obvious *now* but that's the thing about good ideas, they are always obvious when you look back after discovering them. There are a lot more subtleties to literate but I don't think people are quite ready for the brain melt if I start explaining them now ;-) On Thursday, 3 October 2013, Les Mikesell wrote: > On Thu, Oct 3, 2013 at 11:27 AM, Stephen Connolly > <stephen.alan.conno...@gmail.com <javascript:;>> wrote: > > Of course with literate builds you get a much easier way: > > > > Here's the markdown you'd have > > > > # Environments > > > > * `debian` > > * `i386` > > * `x64` > > * `redhat` > > * `i386` > > * `x64` > > * `windows` > > > > # Build > > > > * `debian` > > > > whatever command you use to make the deb > > > > * `redhat` > > > > rpmbuild blah blah blah > > > > * `windows` > > > > whatever command you use to make the exe > > > > Sooo... Why didn't Jenkins do it that way from the start (at least > allowing the job definition to be stored/versioned as part of the > project)? > > -- > Les Mikesell > lesmikes...@gmail.com <javascript:;> > > -- > 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 jenkinsci-users+unsubscr...@googlegroups.com <javascript:;>. > For more options, visit https://groups.google.com/groups/opt_out. > -- Sent from my phone -- 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 jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
