Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-21712

Jenkins Update breaks Subversion credential configuration

    XMLWordPrintable

Details

    • Bug
    • Status: Resolved (View Workflow)
    • Critical
    • Resolution: Duplicate
    • subversion-plugin
    • None
    • Jenkins 1.548, Subversion plugin 2.0 on Ubuntu 12.04.4 amd64 with Tomcat 6 and OpenJDK 7.0

    Description

      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.

      Attachments

        Issue Links

          Activity

            stmork Steffen Mork created issue -

            Upgrade to credentials 1.9.4 and you have in-place addition of credentials on the configure job screen

            stephenconnolly Stephen Connolly added a comment - Upgrade to credentials 1.9.4 and you have in-place addition of credentials on the configure job screen

            Code changed in jenkins
            User: Stephen Connolly
            Path:
            pom.xml
            src/main/java/hudson/scm/SubversionSCM.java
            src/main/resources/hudson/scm/SubversionSCM/AdditionalCredentials/config.jelly
            src/main/resources/hudson/scm/SubversionSCM/ModuleLocation/config.jelly
            src/main/resources/hudson/scm/SubversionSCM/config.jelly
            http://jenkins-ci.org/commit/subversion-plugin/208f10ba16f8317f64060262fa82477db18be299
            Log:
            [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

            Compare: https://github.com/jenkinsci/subversion-plugin/compare/2107e714114e...208f10ba16f8

            scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Stephen Connolly Path: pom.xml src/main/java/hudson/scm/SubversionSCM.java src/main/resources/hudson/scm/SubversionSCM/AdditionalCredentials/config.jelly src/main/resources/hudson/scm/SubversionSCM/ModuleLocation/config.jelly src/main/resources/hudson/scm/SubversionSCM/config.jelly http://jenkins-ci.org/commit/subversion-plugin/208f10ba16f8317f64060262fa82477db18be299 Log: [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 Compare: https://github.com/jenkinsci/subversion-plugin/compare/2107e714114e...208f10ba16f8
            scm_issue_link SCM/JIRA link daemon made changes -
            Field Original Value New Value
            Resolution Fixed [ 1 ]
            Status Open [ 1 ] Resolved [ 5 ]

            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.

            renea Rene Affourtit added a comment - 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.
            renea Rene Affourtit made changes -
            Resolution Fixed [ 1 ]
            Status Resolved [ 5 ] Reopened [ 4 ]

            Same problem here, reverting to version 1.54 of subversion plugin was my only option for now.

            brunojcm Bruno Medeiros added a comment - 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 ...

            ingmartinlopez ingmartinlopez added a comment - Even reverting to version 1.54 of subversion plugin, problem persists ...
            dan_smartstream dan russell added a comment -

            Just found this gem as well. Upgrading from 1.5.3 to 2.5 subversion plugin.

            Even in place generation means changing every job

            dan_smartstream dan russell added a comment - Just found this gem as well. Upgrading from 1.5.3 to 2.5 subversion plugin. Even in place generation means changing every job
            renea Rene Affourtit made changes -
            Link This issue duplicates JENKINS-29211 [ JENKINS-29211 ]
            recena Manuel Recena Soto made changes -
            Assignee Manuel Jesús Recena Soto [ recena ]
            recena Manuel Recena Soto added a comment - It seems related to https://issues.jenkins-ci.org/browse/JENKINS-29211
            recena Manuel Recena Soto made changes -
            Resolution Duplicate [ 3 ]
            Status Reopened [ 4 ] Resolved [ 5 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 153712 ] JNJira + In-Review [ 194659 ]

            People

              recena Manuel Recena Soto
              stmork Steffen Mork
              Votes:
              9 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: