-
Improvement
-
Resolution: Fixed
-
Minor
-
None
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
- relates to
-
JENKINS-39573 local branch option does not work well together with merge before build
-
- Open
-
[JENKINS-33202] Enhance Git Plugin LocalBranch to better support Maven release builds
Description |
Original:
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. |
New:
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 |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Workflow | Original: JNJira [ 169082 ] | New: JNJira + In-Review [ 198532 ] |
Link | New: This issue relates to JENKINS-39573 [ JENKINS-39573 ] |
Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
Code changed in jenkins
User: Mark Waite
Path:
src/main/resources/hudson/plugins/git/extensions/impl/LocalBranch/help.html
http://jenkins-ci.org/commit/git-plugin/fb68e5070c309916e78b27557fbc4d36b63ba071
Log:
Add LocalBranch help text for
JENKINS-33202