[JIRA] (JENKINS-56176) GIT_REVISION macro replaced with GIT_COMMIT but without support for length
Title: Message Title Mark Waite commented on JENKINS-56176 Re: GIT_REVISION macro replaced with GIT_COMMIT but without support for length Thanks. Those details were sufficient that I can see the regression in my environment. Git plugin 3.9 changes the build name as you described and git plugin 4.0.0-rc leaves it an empty string. That is especially surprising for me, since that is not an area of the plugin that I believed had changed. I'll investigate further and seek a fix before the release of git plugin 4.0.0. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56176) GIT_REVISION macro replaced with GIT_COMMIT but without support for length
Title: Message Title
Ian Davis updated an issue
Jenkins / JENKINS-56176
GIT_REVISION macro replaced with GIT_COMMIT but without support for length
Change By:
Ian Davis
Support for GIT_REVISION macro appears to be replaced by GIT_COMMIT however the replacement does not support the length parameter. Consequently "Build Name Setter" plugin is unable to set build names based on only the first few chars of the SHA so build names are massive.To reproduce:1. Use Jenkins 2.150.2, Git plugin 4.0.0-rc, build name setter 1.6.92. Setup a build using a freestyle project that points to a git repo3. Under "Build Environment" settings for the project select "Set Build Name" and specify name as "${BUILD_NUMBER} - ${GIT_BRANCH} - ${GIT_COMMIT,length=4}" & enable "Set build name before build starts"4. Manually trigger a build5. View the build console output and see:*01:04:17* Set build name.*01:04:17* Unrecognized macro 'GIT_COMMIT' in '1170-origin/merge/QtSimLinuxFixes-${GIT_COMMIT,length=4}'
Add Comment
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)
--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56176) GIT_REVISION macro replaced with GIT_COMMIT but without support for length
Title: Message Title
Ian Davis updated an issue
Jenkins / JENKINS-56176
GIT_REVISION macro replaced with GIT_COMMIT but without support for length
Updated description with details about how to reproduce.
Change By:
Ian Davis
Support for GIT_REVISION macro appears to be replaced by GIT_COMMIT however the replacement does not support the length parameter. Consequently "Build Name Setter" plugin is unable to set build names based on only the first few chars of the the SHA so build names are massive. To reproduce:1. Use Jenkins 2.150.2, Git plugin 4.0.0-rc, build name setter 1.6.92. Setup a build using a freestyle project that points to a git repo3. Under "Build Environment" settings for the project select "Set Build Name" and specify name as "${BUILD_NUMBER}-${GIT_BRANCH}-${GIT_COMMIT,length=4}" & enable "Set build name before build starts"4. Manually trigger a build5. View the build console output and see:*01:04:17* Set build name.*01:04:17* Unrecognized macro 'GIT_COMMIT' in '1170-origin/merge/QtSimLinuxFixes-${GIT_COMMIT,length=4}'
Add Comment
This message was sent by Atlassian Jira
[JIRA] (JENKINS-56176) GIT_REVISION macro replaced with GIT_COMMIT but without support for length
Title: Message Title Mark Waite commented on JENKINS-56176 Re: GIT_REVISION macro replaced with GIT_COMMIT but without support for length Please provide the steps you're using to duplicate the problem. This seems like an incompatibility between git plugin 3.x and git plugin 4.0 and I would like to investigate further before git plugin 4.0.0 is released to general availability. Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56176) GIT_REVISION macro replaced with GIT_COMMIT but without support for length
Title: Message Title Mark Waite assigned an issue to Unassigned Jenkins / JENKINS-56176 GIT_REVISION macro replaced with GIT_COMMIT but without support for length Change By: Mark Waite Assignee: Mark Waite Add Comment This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-56176) GIT_REVISION macro replaced with GIT_COMMIT but without support for length
Title: Message Title Ian Davis created an issue Jenkins / JENKINS-56176 GIT_REVISION macro replaced with GIT_COMMIT but without support for length Issue Type: Bug Assignee: Mark Waite Components: git-plugin Created: 2019-02-18 07:22 Environment: Jenkins = 2.150.2 Git plugin = 4.0.0-rc Build Name Setter = 1.6.9 Token Macro = 2.5 Priority: Major Reporter: Ian Davis Support for GIT_REVISION macro appears to be replaced by GIT_COMMIT however the replacement does not support the length parameter. Consequently "Build Name Setter" plugin is unable to set build names based on only the first few chars the the SHA so build names are massive. Add Comment
