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

Enhance Git Plugin LocalBranch to better support Maven release builds

    Details

    • Type: Improvement
    • Status: Closed (View Workflow)
    • Priority: Minor
    • Resolution: Fixed
    • Component/s: git-plugin
    • Labels:
      None
    • Similar Issues:

      Description

      Maven SCM support for branches relies on the local branch name being the same as the remote branch name. Tools such as the maven-release-plugin will push changes using the same local and remote branch names as explained at https://maven.apache.org/scm/git.html

      Ex. git push pushUrl currentBranch:currentBranch

      Jenkins jobs that perform a maven release MUST configure the LocalBranch extension with the correct branch name sans the remote name. For example, if building a release for origin/master, you must configure LocalBranch to be master.

      To facilitate this requirement, LocalBranch values of "**" or null should be allowed and result in using the remote branch name.

      Pull Request covering this feature submitted https://github.com/jenkinsci/git-plugin/pull/381

        Attachments

          Issue Links

            Activity

            michael_giroux michael giroux created issue -
            michael_giroux michael giroux made changes -
            Field Original Value New Value
            Description Maven SCM support for branches relies on the local branch name being the
            same as the remote branch name. Tools such as the maven-release-plugin
            will push changes using the same local and remote branch names as
            explained at https://maven.apache.org/scm/git.html

            Ex. git push pushUrl currentBranch:currentBranch

            Jenkins jobs that perform a maven release MUST configure the LocalBranch extension with the correct branch name sans the remote name. For example, if building a release for origin/master, you must configure LocalBranch to be master.

            To facilitate this requirement, LocalBranch values of "**" or null should be allowed and result in using the remote branch name.
            Maven SCM support for branches relies on the local branch name being the same as the remote branch name. Tools such as the maven-release-plugin will push changes using the same local and remote branch names as explained at https://maven.apache.org/scm/git.html

            Ex. git push pushUrl currentBranch:currentBranch

            Jenkins jobs that perform a maven release MUST configure the LocalBranch extension with the correct branch name sans the remote name. For example, if building a release for origin/master, you must configure LocalBranch to be master.

            To facilitate this requirement, LocalBranch values of "**" or null should be allowed and result in using the remote branch name.

            Pull Request covering this feature submitted https://github.com/jenkinsci/git-plugin/pull/381
            markewaite Mark Waite made changes -
            Status Open [ 1 ] Resolved [ 5 ]
            Resolution Fixed [ 1 ]
            rtyler R. Tyler Croy made changes -
            Workflow JNJira [ 169082 ] JNJira + In-Review [ 198532 ]
            svenackermann Sven Ackermann made changes -
            Link This issue relates to JENKINS-39573 [ JENKINS-39573 ]
            markewaite Mark Waite made changes -
            Status Resolved [ 5 ] Closed [ 6 ]

              People

              • Assignee:
                markewaite Mark Waite
                Reporter:
                michael_giroux michael giroux
              • Votes:
                2 Vote for this issue
                Watchers:
                5 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: