I thought it was considered bad practice to alter binary files which are managed by the operating system package manager.
One of the things that I find so pleasant about the Jenkins debian packaging is that it integrates so nicely with the rest of the operating system packaging. I upgrade to a new Jenkins LTS with the same commands as I use to upgrade to a newer compiler or a newer Java or a newer text editor. If I replace the war file, I think that will surprise the package manager and it may refuse to perform upgrades the way I like. The Debian/Ubuntu install instructions for Jenkins are a very few steps and then it is very nicely integrated. When Debian added the jenkins package to the operating system's own distribution packages, I worried that it might make my smooth Jenkins install and upgrade experience a little less smooth. Mark Waite On Mon, Mar 10, 2014 at 2:22 PM, Daniel Beck <[email protected]> wrote: > > On 10.03.2014, at 21:21, Mark Waite <[email protected]> wrote: > > > If the operating system provides a package, and I want a newer > version, and the packaging between the newer version and the Debian version > are different > > Can't you just replace the war file? > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- Thanks! Mark Waite -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
