Status: Resolved (View Workflow)
Jenkins 1.548, Subversion plugin 2.0 on Ubuntu 12.04.4 amd64 with Tomcat 6 and OpenJDK 7.0
Since subversion plugin 2.0 the subversion credential storage has changed. The credentials must be configured globally while the subversion access user inside a job is configured with a combobox selecting from the globally configured CI-User. After upgrading to 1.458 all credential information in all subversion based jobs are lost. This means reconfiguring more than 150 jobs.
The global configuration of credentials is confusing and time consuming. Please rollback the type of configuration of the subversion credentials to the previuos one.
JENKINS-29211 E200015: ISVNAuthentication provider did not provide credentials
Code changed in jenkins
User: Stephen Connolly
[FIXED JENKINS-21712] The merge lost the switch to <c:select/>
- Refactored the UI to a more modern jelly structure as this made the form validation and updating easier
Upgrade from Jenkins 1.530, svn 1.50 to Jenkins 1.553, svn 2.2, credentials 1.10
running on windows 7 (32 bit).
Credentials for svn server are automatically created, but are not used in jobs.
I'd expect that login information for the svn plugin to be automatically replaced by the correspoding credentials.
Same problem here, reverting to version 1.54 of subversion plugin was my only option for now.
Even reverting to version 1.54 of subversion plugin, problem persists ...
Just found this gem as well. Upgrading from 1.5.3 to 2.5 subversion plugin.
Even in place generation means changing every job
It seems related to https://issues.jenkins-ci.org/browse/JENKINS-29211
Upgrade to credentials 1.9.4 and you have in-place addition of credentials on the configure job screen