I just updated this plugin, after making a backup (since the beta/alpha
before wiped out my config.xml, I was a bit gun shy)... but figured I'd
give it a go now.
It pulled out all the credentials from the jobs correctly and put them in
the global config. The problem I faced is I had to go into each job and
tell it which credential to use. With a lot of jobs this consumed some
time. I did whip up a groovy script to help identify problem jobs:
Jenkins.instance.items.each {item ->
if(item.scm instanceof hudson.scm.SubversionSCM) {
item.scm.locations.each { location ->
if(location.credentialsId == null) {
println item.name
}
}
}
}
If there was a way for it to associate that job with that credential, that
would be ideal.
-- Larry
On Wed, Oct 23, 2013 at 9:04 AM, Stephen Connolly <
[email protected]> wrote:
> This now has the credentials migration as good as I think I can make it.
>
> You are advised to backup
>
> $JENKINS_HOME/config.xml (should not be necessary, but just in case)
> $JENKINS_HOME/credentials.xml
> $JENKINS_HOME/hudson.scm.SubversionSCM.xml
> $JENKINS_HOME/jobs/**/config.xml
> $JENKINS_HOME/jobs/**/subversion.credentials
>
> As if there are any bugs in the credentials migration these are the files
> that will be touched.
>
> We need feedback on this as I intend cutting 2.0 (which will show up in
> the main update centers) after giving this a bit of a soak.
>
> -Stephen
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Developers" 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/groups/opt_out.
>
--
You received this message because you are subscribed to the Google Groups
"Jenkins Developers" 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/groups/opt_out.
