Sorry, misunderstood your question. Forget my answer ;)
Deleting the contents of the updates directory fixed it. Now I see the
option to get 1.480.2 instead of 1.496.
On Mon, Jan 7, 2013 at 1:29 PM, teilo wrote:
> you may waat to remove the contents of jenkins_dir/data/updates
>
> /James
>
>
> On Monday, 7 January 2013 13:53:18 UTC, Jon Schewe wrote
Can you explain more? What link provided by Jenkins?
On Mon, Jan 7, 2013 at 8:09 AM, SBreitbach wrote:
> Don't use the link on the webpage. Use the link provided by Jenkins itself
> instead.
--
http://mtu.net/~jpschewe
you may waat to remove the contents of jenkins_dir/data/updates
/James
On Monday, 7 January 2013 13:53:18 UTC, Jon Schewe wrote:
>
> I just switched one of my Jenkins servers to the LTS release. I downloaded
> the war file and replaced my current war file. I then updated the update
> site for t
Don't use the link on the webpage. Use the link provided by Jenkins itself
instead.
I just switched one of my Jenkins servers to the LTS release. I downloaded
the war file and replaced my current war file. I then updated the update
site for the plugins and restarted. Everything is running fine, except when
I goto Manage Jenkins I'm still prompted to upgrade to the latest bleeding
