[JIRA] [git] (JENKINS-21681) Git Publisher only allows to push HEAD
Arlo Louis O'Keeffe commented on JENKINS-21681 Git Publisher only allows to push HEAD Sorry, if my intent was not fully clear. This is an enhancement request to allow Git Publisher to push something other than current HEAD. Yes, the problem is solved due to the authentication information being part of the repository URL. 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.
[JIRA] [git] (JENKINS-21681) Git Publisher only allows to push HEAD
Mark Waite commented on JENKINS-21681 Git Publisher only allows to push HEAD 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? 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.
[JIRA] [git] (JENKINS-21681) Git Publisher only allows to push HEAD
Arlo Louis O'Keeffe updated JENKINS-21681 Git Publisher only allows to push HEAD Change By: Arlo Louis O'Keeffe (06/Feb/14 9:46 AM) Priority: Major Blocker 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.
[JIRA] [git] (JENKINS-21681) Git Publisher only allows to push HEAD
Arlo Louis O'Keeffe
updated JENKINS-21681
Git Publisher only allows to push HEAD
Change By:
Arlo Louis O'Keeffe
(06/Feb/14 9:46 AM)
Description:
We use the [maven-jgitflow-plugin|https://bitbucket.org/atlassian/maven-jgitflow-plugin/] to manage our build workflow.The release-finish goal commits to two local branches {{develop}} and {{master}}. These need to be pushed to origin. Typically the plugin does this. Because in the latest version of Git Client Plugin the credentials are not stored locally anymore this does not work.The Git Publisher seemed like the solution but sadly it only supports pushing {{HEAD}}. It would be great if it allowed to choose what to push. HEAD should remain the default (e.g. when box is empty).
As a
There is no
workaround
I currently use the store credential helper
available other than using Git Client Plugin 1.4.3
and
have entered all passwords accordingly
Git Plugin 2
.
This allows the maven-jgitflow-plugin to push again
0
.
0.
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.
[JIRA] [git] (JENKINS-21681) Git Publisher only allows to push HEAD
Arlo Louis O'Keeffe created JENKINS-21681 Git Publisher only allows to push HEAD Issue Type: Bug Affects Versions: current Assignee: Nicolas De Loof Components: git Created: 06/Feb/14 9:01 AM Description: We use the maven-jgitflow-plugin to manage our build workflow. The release-finish goal commits to two local branches develop and master. These need to be pushed to origin. Typically the plugin does this. Because in the latest version of Git Client Plugin the credentials are not stored locally anymore this does not work. The Git Publisher seemed like the solution but sadly it only supports pushing HEAD. It would be great if it allowed to choose what to push. HEAD should remain the default (e.g. when box is empty). As a workaround I currently use the store credential helper and have entered all passwords accordingly. This allows the maven-jgitflow-plugin to push again. Environment: Jenkins 1.549 Git Client Plugin 1.6.2 Git Plugin 2.0.1 Project: Jenkins Priority: Major Reporter: Arlo Louis O'Keeffe 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.
