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

Jenkins Update breaks Subversion credential configuration

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Resolved (View Workflow)
    • Priority: Critical
    • Resolution: Duplicate
    • Component/s: subversion-plugin
    • Labels:
      None
    • Environment:
      Jenkins 1.548, Subversion plugin 2.0 on Ubuntu 12.04.4 amd64 with Tomcat 6 and OpenJDK 7.0
    • Similar Issues:

      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

            Hide
            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

            Show
            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
            Hide
            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

            Show
            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
            Hide
            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.

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

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

            Show
            brunojcm Bruno Medeiros added a comment - Same problem here, reverting to version 1.54 of subversion plugin was my only option for now.
            Hide
            ingmartinlopez ingmartinlopez added a comment -

            Even reverting to version 1.54 of subversion plugin, problem persists ...

            Show
            ingmartinlopez ingmartinlopez added a comment - Even reverting to version 1.54 of subversion plugin, problem persists ...
            Hide
            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

            Show
            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
            Hide
            recena Manuel Recena Soto added a comment -
            Show
            recena Manuel Recena Soto added a comment - It seems related to https://issues.jenkins-ci.org/browse/JENKINS-29211

              People

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

                Dates

                • Created:
                  Updated:
                  Resolved: