![]() |
|
|
|
|
Issue Type:
|
![Bug]() Bug
|
|
Assignee:
|
k2nakamura
|
|
Components:
|
svn-tag |
|
Created:
|
29/Oct/14 3:21 PM
|
|
Description:
|
When a build was successfull and there was already a matching svn tag, the previous tag gets deleted.
That should not happen, as this massively breaks traceability of releases.
When talking about a "tested, quality approved release 2.2" , nobody knows if "the old 2.2" or "the new 2.2" was working as specified in quality assurance, while the other did not.
Therefore a global option to prevent removal of svn tags would be really appreciated.
In case there a situations where deletion of old svn tags is desired, there could also a be job-based override option for this, but an option to prevent those tag deletions by accident really would help maintaining traceability of release versions.
|
|
Environment:
|
Jenkins 1.565.3
Tomcat 7.0.54, amd64
Oracle JRE 1.7.0u71, amd64
Debian GNU/Linux, amd64, de_DE.UTF-8
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Critical]() Critical
|
|
Reporter:
|
Tim-Christian Bloss
|
|
|
|
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira
|
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.
