Issue Type: Bug 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 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.

Reply via email to