![]() |
|
|
|
|
Issue Type:
|
![Improvement]() Improvement
|
|
Assignee:
|
Nicolas De Loof
|
|
Components:
|
git |
|
Created:
|
11/Apr/14 12:20 AM
|
|
Description:
|
Using the Git Publisher, in post-build Actions, Tags, Branches, Notes are only allowed in that order. It would be helpful if one could choose which action would occur in what order. I care because on occasion a user will commit to a branch that I wish to push at the end of a build, during the build execution. When this occurs, the publisher will rightly refuse to push changes in the clone because the clone is now out-of-date. This is all good. However, I also push a tag on successful builds. Because the tag gets pushed first, a tag is pushed, and then the branch push fails due to the aforementioned reason.
If I were able to attempt the branch push first, then it would fail in my example, and the tag push would never happen.
|
|
Environment:
|
Git Plugin 2.0.1
Jenkins 1.532.2
|
|
Project:
|
Jenkins
|
|
Priority:
|
![Major]() Major
|
|
Reporter:
|
Scott Armit
|
|
|
|
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.
