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

Subversion-Tagging Plugin can't create tag because of missing credentials

    Details

    • Similar Issues:

      Description

      When trying to tag a successfull build, I get this errormessage:
      "Das Erstellen des Tags ist fehlgeschlagen. svn: E200015: OPTIONS /svn/tools/Redmine/Changelog/trunk failed
      Build step 'Erstellt Subversion Tags für erfolgreiche Builds.' marked build as failure"
      Which means "The creating of the tag failed. svn: E200015: OPTIONS /svn/tools/Redmine/Changelog/trunk failed
      Build step 'Creates Subversion tag for successfull Builds.' marked build as failure"

      This happens since the subversion plugin update to Version 2.0.
      There is no way to fill the credentials for the subversion tagging plugin.

        Attachments

          Activity

          Hide
          e598372 Branz Frandwein added a comment -

          I'm facing the same problem, this is very frustrating.

          Any workarounds?

          Show
          e598372 Branz Frandwein added a comment - I'm facing the same problem, this is very frustrating. Any workarounds?
          Hide
          hikeeba John Long added a comment -

          I am also having this issue and I have not found a workaround.

          Show
          hikeeba John Long added a comment - I am also having this issue and I have not found a workaround.
          Hide
          e598372 Branz Frandwein added a comment -

          I tried downgrading the Subversion plugin back to 1.54, but that didn't solve it either.

          Show
          e598372 Branz Frandwein added a comment - I tried downgrading the Subversion plugin back to 1.54, but that didn't solve it either.
          Hide
          heinzepreller heinzepreller added a comment -

          Same to me:

          After Upgrade to Jenkins 1.551 and Subversion Plugin 2.1 we aren't able to VCS Tag after "Release Staging" Build.
          Also pom commit fails with Subversion Plug-in: "Failure in post build SCM action: svn: E200015: OPTIONS"

          I don't know where to specify credentials for Artifactory Plugin or something else.

          Show
          heinzepreller heinzepreller added a comment - Same to me: After Upgrade to Jenkins 1.551 and Subversion Plugin 2.1 we aren't able to VCS Tag after "Release Staging" Build. Also pom commit fails with Subversion Plug-in: "Failure in post build SCM action: svn: E200015: OPTIONS" I don't know where to specify credentials for Artifactory Plugin or something else.
          Hide
          heinzepreller heinzepreller added a comment - - edited

          Upgrade of Subversion Plugin to v 2.2 didn't change anything.

          Also "Release Staging" build to build a Release for Artifactory is not possible anymore, because VCS cannot be tagged and pom.xml cannto be commit because of missing credentials.

          Show
          heinzepreller heinzepreller added a comment - - edited Upgrade of Subversion Plugin to v 2.2 didn't change anything. Also "Release Staging" build to build a Release for Artifactory is not possible anymore, because VCS cannot be tagged and pom.xml cannto be commit because of missing credentials.
          Hide
          joe Joe Shomphe added a comment -

          This is also causing us quite a bit of trouble.....fixing it requires rolling back to a prior backup of Jenkins

          Show
          joe Joe Shomphe added a comment - This is also causing us quite a bit of trouble.....fixing it requires rolling back to a prior backup of Jenkins
          Hide
          e598372 Branz Frandwein added a comment -

          @Joe Shomphe
          To which version (Jenkins, plugins) did you roll back to fix it?

          Show
          e598372 Branz Frandwein added a comment - @Joe Shomphe To which version (Jenkins, plugins) did you roll back to fix it?
          Hide
          heinzepreller heinzepreller added a comment -

          We are still not able to build releases with "artifactory release staging" since a week now, because of missing credntials artifactory tag & commit.

          Any ideas, any workarounds ?

          Show
          heinzepreller heinzepreller added a comment - We are still not able to build releases with "artifactory release staging" since a week now, because of missing credntials artifactory tag & commit. Any ideas, any workarounds ?
          Hide
          mmaak Mathias Maak added a comment -

          workaround for us:

          • connect to a cli on the jenkins server
          • make an initial svn checkout to the svn url in a temp folder
          • login to the svn an save password unencrypted
          • now you should have in jenkins home a folder .subversion/auth/svn.simple/ with the credentials
          • these credentials are used from svn tagging plugin
          Show
          mmaak Mathias Maak added a comment - workaround for us: connect to a cli on the jenkins server make an initial svn checkout to the svn url in a temp folder login to the svn an save password unencrypted now you should have in jenkins home a folder .subversion/auth/svn.simple/ with the credentials these credentials are used from svn tagging plugin
          Hide
          andrey_stegantsov Andrey Stegantsov added a comment -

          @Mathias Maak
          > make an initial svn checkout to the svn url in a temp folder

          Could you please explain how to call "svn co" using jenkins cli ( https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI )?
          I only found groovysh.

          Show
          andrey_stegantsov Andrey Stegantsov added a comment - @Mathias Maak > make an initial svn checkout to the svn url in a temp folder Could you please explain how to call "svn co" using jenkins cli ( https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI )? I only found groovysh.
          Hide
          mmaak Mathias Maak added a comment -

          @Andrey Stegantsov
          > Could you please explain how to call "svn co" using jenkins cli ( https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI )? I only found groovysh.

          I did't mean Jenkins CLI. Connect to your Jenkins Server (Linux) via ssh (ssh user@jenkinsserver). Change to user jenkins (su - jenkins) and make the svn co.

          Show
          mmaak Mathias Maak added a comment - @Andrey Stegantsov > Could you please explain how to call "svn co" using jenkins cli ( https://wiki.jenkins-ci.org/display/JENKINS/Jenkins+CLI )? I only found groovysh. I did't mean Jenkins CLI. Connect to your Jenkins Server (Linux) via ssh (ssh user@jenkinsserver). Change to user jenkins (su - jenkins) and make the svn co.
          Hide
          andrey_stegantsov Andrey Stegantsov added a comment -

          @Mathias Maak

          Bingo. Thanks a lot!

          Show
          andrey_stegantsov Andrey Stegantsov added a comment - @Mathias Maak Bingo. Thanks a lot!
          Hide
          dmolineu D.L. Molineu added a comment -

          We're running into this same issue, running Jenkins 1.532.1 on Windows Server 2008 R2. Any tips on a fix/workaround would be much appreciated!

          Show
          dmolineu D.L. Molineu added a comment - We're running into this same issue, running Jenkins 1.532.1 on Windows Server 2008 R2. Any tips on a fix/workaround would be much appreciated!
          Hide
          zacharysyoung Zachary Young added a comment - - edited

          Is this related to the "recent" Credentials changes in Jenkins? I would expect "Tag this build" to at least have a credential selector, and a store-able config... maybe defaulting to the credential selection of the job from which "Tag this build" is clicked/called.

          Show
          zacharysyoung Zachary Young added a comment - - edited Is this related to the "recent" Credentials changes in Jenkins? I would expect "Tag this build" to at least have a credential selector, and a store-able config... maybe defaulting to the credential selection of the job from which "Tag this build" is clicked/called.
          Hide
          rinok Rino added a comment -

          Opened pull request: https://github.com/jenkinsci/svn-tag-plugin/pull/4

          And attached snapshot build (depends on svn 2.2 plugin)

          Show
          rinok Rino added a comment - Opened pull request: https://github.com/jenkinsci/svn-tag-plugin/pull/4 And attached snapshot build (depends on svn 2.2 plugin)
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Rino
          Path:
          src/main/java/hudson/plugins/svn_tag/SvnTagPlugin.java
          http://jenkins-ci.org/commit/svn-tag-plugin/172d2cec18edc96b001c2f59f579388d370ff3ef
          Log:
          JENKINS-21797: commit client created per module location

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Rino Path: src/main/java/hudson/plugins/svn_tag/SvnTagPlugin.java http://jenkins-ci.org/commit/svn-tag-plugin/172d2cec18edc96b001c2f59f579388d370ff3ef Log: JENKINS-21797 : commit client created per module location
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Rino
          Path:
          pom.xml
          http://jenkins-ci.org/commit/svn-tag-plugin/4e17b3261486a29a284dfe543a0da488246f3f5e
          Log:
          JENKINS-21797: dependency 2.2+

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Rino Path: pom.xml http://jenkins-ci.org/commit/svn-tag-plugin/4e17b3261486a29a284dfe543a0da488246f3f5e Log: JENKINS-21797 : dependency 2.2+
          Hide
          scm_issue_link SCM/JIRA link daemon added a comment -

          Code changed in jenkins
          User: Marc Schöchlin
          Path:
          pom.xml
          src/main/java/hudson/plugins/svn_tag/SvnTagPlugin.java
          http://jenkins-ci.org/commit/svn-tag-plugin/27285688a13f32b8e47643f0ea3aa2a460686ce0
          Log:
          Merge pull request #4 from rinokadijk/master

          FIXED: JENKINS-21797 Subversion-Tagging Plugin can't create tag because of missing credentials

          Compare: https://github.com/jenkinsci/svn-tag-plugin/compare/edee3b6892fa...27285688a13f

          Show
          scm_issue_link SCM/JIRA link daemon added a comment - Code changed in jenkins User: Marc Schöchlin Path: pom.xml src/main/java/hudson/plugins/svn_tag/SvnTagPlugin.java http://jenkins-ci.org/commit/svn-tag-plugin/27285688a13f32b8e47643f0ea3aa2a460686ce0 Log: Merge pull request #4 from rinokadijk/master FIXED: JENKINS-21797 Subversion-Tagging Plugin can't create tag because of missing credentials Compare: https://github.com/jenkinsci/svn-tag-plugin/compare/edee3b6892fa...27285688a13f
          Hide
          sdr984 Scott Roberts added a comment -

          Any plans to release the plugin and tag as a new version. The latest is still the build from 2011.

          Show
          sdr984 Scott Roberts added a comment - Any plans to release the plugin and tag as a new version. The latest is still the build from 2011.
          Hide
          tcb_xy Tim-Christian Bloss added a comment - - edited

          Problem also occurring on
          Jenkins LTS 1.532.3
          SVN-Tag-Plugin 1.16
          SVN-Plugin 2.3
          Debian GNU/Linux 7
          Tomcat 7.0.52
          JRE 1.7.0_55

          We'd need that new version for 1.532.3, too

          Show
          tcb_xy Tim-Christian Bloss added a comment - - edited Problem also occurring on Jenkins LTS 1.532.3 SVN-Tag-Plugin 1.16 SVN-Plugin 2.3 Debian GNU/Linux 7 Tomcat 7.0.52 JRE 1.7.0_55 We'd need that new version for 1.532.3, too
          Hide
          jglick Jesse Glick added a comment -

          1.17 released.

          Show
          jglick Jesse Glick added a comment - 1.17 released.

            People

            • Assignee:
              rinok Rino
              Reporter:
              the_brand Kevin Brand
            • Votes:
              15 Vote for this issue
              Watchers:
              24 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: