-
-
Notifications
You must be signed in to change notification settings - Fork 47
Description
If you configure "Subversion Tagging" as action "After successful release build" the build is not tagged.
Console output is:
Building on master in workspace /data/jenkins/jobs/SVN-Jenkins-Test/workspace
Updating
http://svn.local/svn/jenkins_test/trunk
at revision '2017-04-04T18:27:56.228 +0200'
At revision 3
No changes for
http://svn.local/svn/jenkins_test/trunk
since the previous build
Starting to tag
No Subversion tagging for unsuccessful build.
Finished: SUCCESS
If same configuration is used as post build action for the normal build, the repository is tagged correctly.
Originally reported by mschmidt_esd, imported from: Subversion Tagging Plugin does not work with Release Plugin
- assignee:
petehayes
- status: Open
- priority: Major
- component(s): release-plugin, svn-tag-plugin
- label(s): release-plugin, svn-tag
- resolution: Unresolved
- votes: 0
- watchers: 1
- imported: 20251223-222157
Raw content of original issue
If you configure "Subversion Tagging" as action "After successful release build" the build is not tagged.
Console output is: Building on master in workspace /data/jenkins/jobs/SVN-Jenkins-Test/workspace Updating http://svn.local/svn/jenkins_test/trunk at revision '2017-04-04T18:27:56.228 +0200' At revision 3
No changes for http://svn.local/svn/jenkins_test/trunk since the previous build Starting to tag No Subversion tagging for unsuccessful build. Finished: SUCCESS If same configuration is used as post build action for the normal build, the repository is tagged correctly.
environment
Jenkins 2.46.1<br/>
Subversion Tagging Plugin 1.18<br/>
Release Plugin 2.6.1