best way to update jenkins on ubuntu 13.10?

[andrea crotti]

On ubuntu server now there is this version:

Jenkins ver. 1.509.2

which however is not letting me install Cobertura and other few things for example.

I would like to update it but also still use a standard package style, is that possible?

There was a PPA for that but very old and outdated, any other possibility?

Thanks

[Nick Stolwijk]

As far as I know you can use the debian repository of Jenkins.

I have this in /etc/apt/sources.list.d/jenkins.list:

deb http://pkg.jenkins-ci.org/debian binary/

Hth,

Nick Stolwijk

~~~ Try to leave this world a little better than you found it and, when your turn comes to die, you can die happy in feeling that at any rate you have not wasted your time but have done your best ~~~

Lord Baden-Powell

--
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-use...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[andrea crotti]

It complains about the key now when I try to do the update though..

W: GPG error: http://pkg.jenkins-ci.org binary/ Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9B7D32F2D50582E6

[Sebastian Otaegui]

The Jenkins website specifies how to import the key in the gpg keystore

--

[and...@wazoku.com]

Ah yes sorry I missed that..

Now I followed the doc from that page but it still didn't work and left me in a half-configured state; I had to force a dpkg -i of the old package to fix it..

Basically it was failing

Setting up jenkins (1.540) ...

start: Job failed to start

invoke-rc.d: initscript jenkins, action "start" failed.

dpkg: error processing jenkins (--configure):

 subprocess installed post-installation script returned error exit status 1

Errors were encountered while processing:

 jenkins

So maybe is the package not correct for Ubuntu 13.10 or what else can it be?

[Marius Gedminas]

On Thursday, November 21, 2013 10:30:03 PM UTC+2, and...@wazoku.com wrote:

Ah yes sorry I missed that..

Now I followed the doc from that page but it still didn't work and left me in a half-configured state; I had to force a dpkg -i of the old package to fix it..

Basically it was failing

Setting up jenkins (1.540) ...

start: Job failed to start

invoke-rc.d: initscript jenkins, action "start" failed.

dpkg: error processing jenkins (--configure):

 subprocess installed post-installation script returned error exit status 1

Errors were encountered while processing:

 jenkins

So maybe is the package not correct for Ubuntu 13.10 or what else can it be?

There's a bug in upstream packaging that breaks upgrades:

https://issues.jenkins-ci.org/browse/JENKINS-18798

There's a related bug that makes Jenkins not start up on boot:

https://issues.jenkins-ci.org/browse/JENKINS-19329

Workarounds for both issues:

    sudo apt-get remove jenkins jenkins-common

    sudo apt-get install jenkins

    sudo rm /etc/init/jenkins.conf

    sudo update-rc.d jenkins defaults

    sudo service jenkins start

[Daniel Beck]

On 22.11.2013, at 09:27, Marius Gedminas <mar...@gedmin.as> wrote:

> There's a bug in upstream packaging that breaks upgrades:
> https://issues.jenkins-ci.org/browse/JENKINS-18798
>
> There's a related bug that makes Jenkins not start up on boot:
> https://issues.jenkins-ci.org/browse/JENKINS-19329

Are these really _bugs_ in the Jenkins Debian package? It looks like the Ubuntu maintainers created another Jenkins package that behaves differently, and the 'official' Jenkins releases ('upstream') simply don't know or care about its existence. If you create something new 'downstream', shouldn't you need to handle any compatibility issues between your package and the 'official' one?