[JENKINS-21681] Extend Git Publisher to push multiple branches, including HEAD

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).

There is no workaround available other than using Git Client Plugin 1.4.3 and Git Plugin 2.0.0.

---
Originally reported by arlol, imported from: Extend Git Publisher to push multiple branches, including HEAD

• status: Open
  
• priority: Major
  
• component(s): git-plugin
  
• label(s): git-publisher
  
• resolution: Unresolved
  
• votes: 3
  
• watchers: 5
  
• imported: 2025-12-02
  

Raw content of original issue

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).


There is no workaround available other than using Git Client Plugin 1.4.3 and Git Plugin 2.0.0.

environment

```
Jenkins 1.549

Git Client Plugin 1.6.2

Git Plugin 2.0.1
```