|
||||||||
|
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/groups/opt_out.
I'm not sure I understand. Are you saying that in an earlier version of the plugin, you were able to define two Git Publisher actions, one that pushed to the develop branch, and one that pushed to the master branch? Did that give you the result you wanted?
The Git Publisher help says "Specify remote branches to push the current HEAD to, as of the completion of the build." Are you intending to push current HEAD to both develop and master?
I'm not sure if you're phrasing this as an enhancement request (add the Git Publisher ability to push something other than the current HEAD) or as a bug report that something regressed (you were previously able to push separate branches and now you can't).
Can you clarify your intent? Did you solve the problem in Git client plugin 1.4.3 and Git plugin 2.0.0 by embedding the authentication information in the Git repository URL? Or, did you make a build step which performed the push using Git commands?