Yes, the fork happened around 1.395 or so. I don't know what version Hudson
changed the format.
Sent from my Windows Phone
--
From: Daniel Fortunov
Sent: 1/3/2013 5:18 PM
To: jenkinsci-users@googlegroups.com
Subject: Re: migration hudson 2.2.0 to jenkins
What i
What is the latest version before the fork? I thought 2.2.0 was already
beyond the fork?
On 2 January 2013 20:46, Lars Nordin wrote:
> Search the mailing list archives for posts from folks that have done
> this same thing.
>
> ** **
>
> The pattern has been – depending on how old of a versi
Search the mailing list archives for posts from folks that have done this same
thing.
The pattern has been – depending on how old of a version of hudson – to upgrade
to the last version of hudson before the fork (you may need an interim upgrade
if your version of Hudson is really old) and then
om my Windows Phone
--
From: Daniel Fortunov
Sent: 12/28/2012 10:11 AM
To: jenkinsci-users@googlegroups.com
Cc: maro.schu...@gmail.com
Subject: Re: migration hudson 2.2.0 to jenkins
Hello,
Is there any more information on this? I've also just (resumed) trying to
up
Hello,
Is there any more information on this? I've also just (resumed) trying to
upgrade from Hudson 2.0.0 and noted that the configuration file format is *
completely* different.
My existing config files have pretty much *everything*, including the build
commands, defined within:
In the new
Hi,
Does anyone have experience migrating from hudson 2.2.0 to jenkins (current
version, 1.461) ? The format of the hudson config files has changed and
migration isn't as easy as it used to be:
- some settings aren't picked up (for instance a project specific jdk and
the schedule for 'build pe
