On Friday, 25 January 2013 21:56:41 UTC, LesMikesell wrote: > > On Fri, Jan 25, 2013 at 3:43 PM, teilo <teilo+...@teilo.net <javascript:>> > wrote: > > > > To be pretty honest - I would suggest you skip the packaged versions and > use > > your own init scripts and the war with the inbuilt winstone container. > > > > As for which distro - if you take the above advice it depends on you. > > Pretty much anything recent will have a good enough kernel and the reset > is > > just java. > > > > I use CentOS, but I prefer to admin debian - but work is RH/CentOS. If > you > > are thinking of support then make sure that whatever you choose is > covered > > by your support vendor. Whichever you choose you can always choose not > to > > install the defaults but install just what you want (but having things > > installed should not be an issue - just don;t start the services and > install > > root on cheaper HDD and then have your JENKINS_HOME on the SSD > > > > For RH or CentOS, I think the yum install is even easier if you want > to use the embedded winstone. > http://pkg.jenkins-ci.org/redhat/ > You can configure your options in the /etc/sysconfig/jenkins file so > subsequent updates won't overwrite them. JENKINS_HOME will be > /var/lib/jenkins (following packaging guidelines) so mount whatever > you want there before then install. > > > Its easier for the first install, but after that it is not as good.
Packages are guaranteed to be broken more than the war alone (as there is an extra layer it is one more thiing that can change/break - as shown by the recent deb change) The war arguments are not likely to change but will be added to (if needed) but the config exposed by these scripts is not the same. For example what happens if you say want to run SSL - you then add custom ARGs to the line. Later the init scripts add a user friendly option for SSL (defaults to -1). so now the init script can fail as the HTTPS_PORT var is not -1 (as it doesn't exist in your config) - or worse it is 8443 by default so it uses the default as well as your different port. That is a contrived example - but that has happend recently on the deb when a parameter was removed. upgrades/downgrades are a simple change of a symlink with the jenkins war. by all means grab the init scripts from the src repo - but in the long run the ease is lost. my 2p from experience.
