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

Extend Git Publisher to push multiple branches, including HEAD

    • Icon: New Feature New Feature
    • Resolution: Unresolved
    • Icon: Major Major
    • git-plugin
    • Jenkins 1.549
      Git Client Plugin 1.6.2
      Git Plugin 2.0.1

      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.

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

          Arlo Louis O'Keeffe created issue -
          Arlo Louis O'Keeffe made changes -
          Description Original: 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 workaround I currently use the store credential helper and have entered all passwords accordingly. This allows the maven-jgitflow-plugin to push again.
          New: 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).

          There is no workaround available other than using Git Client Plugin 1.4.3 and Git Plugin 2.0.0.
          Arlo Louis O'Keeffe made changes -
          Priority Original: Major [ 3 ] New: Blocker [ 1 ]
          Mark Waite made changes -
          Issue Type Original: Bug [ 1 ] New: New Feature [ 2 ]
          Summary Original: Git Publisher only allows to push HEAD New: Extend Git Publisher to push multiple branches, including HEAD
          Mark Waite made changes -
          Priority Original: Blocker [ 1 ] New: Major [ 3 ]
          Kanstantsin Shautsou made changes -
          Labels New: git-publisher
          Kanstantsin Shautsou made changes -
          Remote Link New: This issue links to "git-plugin/pull/303 (Web Link)" [ 12109 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 153680 ] New: JNJira + In-Review [ 178572 ]
          Nicolas De Loof made changes -
          Assignee Original: Nicolas De Loof [ ndeloof ]

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

              Created:
              Updated: