Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-21681

Extend Git Publisher to push multiple branches, including HEAD

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Component/s: git-plugin
    • Labels:
    • Environment:
      Jenkins 1.549
      Git Client Plugin 1.6.2
      Git Plugin 2.0.1
    • Similar Issues:

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

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

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              arlol Arlo Louis O'Keeffe
              Votes:
              3 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated: