[JIRA] [git-plugin] (JENKINS-33202) Enhance Git Plugin LocalBranch to better support Maven release builds

2 views
Skip to first unread message

michael_giroux@choicehotels.com (JIRA)

unread,
Feb 28, 2016, 10:22:04 AM2/28/16
to jenkinsc...@googlegroups.com
michael giroux created an issue
 
Jenkins / Improvement JENKINS-33202
Enhance Git Plugin LocalBranch to better support Maven release builds
Issue Type: Improvement Improvement
Assignee: Mark Waite
Components: git-plugin
Created: 28/Feb/16 3:21 PM
Priority: Minor Minor
Reporter: michael giroux

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.

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265)
Atlassian logo

michael_giroux@choicehotels.com (JIRA)

unread,
Feb 28, 2016, 10:30:01 AM2/28/16
to jenkinsc...@googlegroups.com
michael giroux updated an issue
Change By: michael giroux
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

scm_issue_link@java.net (JIRA)

unread,
Mar 18, 2016, 8:13:02 AM3/18/16
to jenkinsc...@googlegroups.com
SCM/JIRA link daemon commented on Improvement JENKINS-33202
 
Re: Enhance Git Plugin LocalBranch to better support Maven release builds

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

mark.earl.waite@gmail.com (JIRA)

unread,
Mar 18, 2016, 8:14:02 AM3/18/16
to jenkinsc...@googlegroups.com

Merged to the master branch 17 Mar 2016, will be included in the git plugin 2.4.3 and later releases.

mark.earl.waite@gmail.com (JIRA)

unread,
Mar 19, 2016, 3:29:04 PM3/19/16
to jenkinsc...@googlegroups.com
Mark Waite resolved as Fixed
 

Included in git plugin 2.4.3, released 19 Mar 2016.

Change By: Mark Waite
Status: Open Resolved
Resolution: Fixed

mark.earl.waite@gmail.com (JIRA)

unread,
Jul 14, 2019, 8:04:02 AM7/14/19
to jenkinsc...@googlegroups.com
Mark Waite closed an issue as Fixed
Change By: Mark Waite
Status: Resolved Closed
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
Reply all
Reply to author
Forward
0 new messages