[JIRA] (JENKINS-52490) Plugin should provide GIT_COMMIT_MESSAGE as Environment Variable

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

Mark Waite updated an issue

Jenkins / JENKINS-52490 Plugin should provide GIT_COMMIT_MESSAGE as Environment Variable Change By: Mark Waite Summary: Plugin should provide GIT_COMMITTER_MESSAGE GIT_COMMIT_MESSAGE as Enviornment Environment Variable Add Comment

This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

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

Mark Waite updated an issue

Jenkins / JENKINS-52490 Plugin should provide GIT_COMMIT_MESSAGE as Environment Variable

Change By: Mark Waite Summary: Plugin should provide GIT_COMMITTER_MESSAGE GIT_COMMIT_MESSAGE as Environment Variable

Add Comment

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

Mark Waite edited a comment on JENKINS-52490

Re: Plugin should provide GIT_COMMIT_MESSAGE as Environment Variable This is already available for Pipeline jobs by using the {{GIT_COMMIT}} (sha1 of the commit) value returned in the map of the {{checkout}} step.  Use that SHA1 to call a shell step and read the commit message into your Pipeline. {noformat}     branch = 'JENKINS-50401'     checkout_result = checkout([$class: 'GitSCM',                 branches: [[name: branch]],                 extensions: [[$class: 'CloneOption', honorRefspec: true, noTags: true],                      [$class: 'LocalBranch', localBranch: branch]                      ],                 userRemoteConfigs: [[refspec: "+refs/heads/${branch}:refs/remotes/origin/${branch}",                      url: 'https://github.com/MarkEWaite/jenkins-bugs.git']]])     commit_message = sh returnStdout: true, script: "git log -n 1 ${checkout_result.GIT_COMMIT)" {noformat} If that same information is needed in a Freestyle project, you'll need to use a similar technique from within the build script.

Add Comment

[imranrazakhan@gmail.com (JIRA)]

imran khan commented on JENKINS-52490

Re: Plugin should provide GIT_COMMIT_MESSAGE as Environment Variable

Till the time we didnt get GIT_COMMIT_MESSAGE, Following step will work in declarative jenkins piepline GIT_MESSAGE = powershell (returnStdout: true, script: 'git log -1 --format=%B ${GIT_COMMIT}').trim()

Add Comment

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

Mark Waite edited a comment on JENKINS-52490

Re: Plugin should provide GIT_COMMIT_MESSAGE as Environment Variable

This is already available for Pipeline jobs by using the {{GIT_COMMIT}} (sha1 of the commit) value returned in the map of the {{checkout}} step.  Use that SHA1 to call a shell step and read the commit message into your Pipeline. {noformat}     branch = 'JENKINS-50401'     checkout_result = checkout([$class: 'GitSCM',                 branches: [[name: branch]],                 extensions: [[$class: 'CloneOption', honorRefspec: true, noTags: true],                      [$class: 'LocalBranch', localBranch: branch]                      ],                 userRemoteConfigs: [[refspec: "+refs/heads/${branch}:refs/remotes/origin/${branch}",                      url: 'https://github.com/MarkEWaite/jenkins-bugs.git']]])

commit_message = sh ( returnStdout: true, script: "git log -n 1 ${checkout_result.GIT_COMMIT)" )

{noformat} If that same information is needed in a Freestyle project, you'll need to use a similar technique from within the build script.

Add Comment

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

Mark Waite edited a comment on JENKINS-52490

Re: Plugin should provide GIT_COMMIT_MESSAGE as Environment Variable

This is already available for Pipeline jobs by using the {{GIT_COMMIT}} (sha1 of the commit) value returned in the map of the {{checkout}} step.  Use that SHA1 to call a shell step and read the commit message into your Pipeline. {noformat}     branch = 'JENKINS-50401'     checkout_result = checkout([$class: 'GitSCM',                 branches: [[name: branch]],                 extensions: [[$class: 'CloneOption', honorRefspec: true, noTags: true],                      [$class: 'LocalBranch', localBranch: branch]                      ],                 userRemoteConfigs: [[refspec: "+refs/heads/${branch}:refs/remotes/origin/${branch}",                      url: 'https://github.com/MarkEWaite/jenkins-bugs.git']]])

commit_message = sh(returnStdout: true, script: "git log -n 1 ${checkout_result.GIT_COMMIT ) } ")

{noformat} If that same information is needed in a Freestyle project, you'll need to use a similar technique from within the build script.

Add Comment

[knurek.j@gmail.com (JIRA)]

J Knurek commented on JENKINS-52490

Re: Plugin should provide GIT_COMMIT_MESSAGE as Environment Variable

I've had a try at implemented what is needed for this feature. I actually haven't tested it, or added any unit tests, because I'm not even sure this is a valid approach. So I'd appreciate some feedback on the PR before continuing: https://github.com/jenkinsci/git-plugin/pull/796

Add Comment

This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)

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

Mark Waite commented on JENKINS-52490

Re: Plugin should provide GIT_COMMIT_MESSAGE as Environment Variable

I am piv vacation for the rest of this week. Other maintainers may be available, but I am not. I generally don't accept pull requests that lack tests. However, I'm willing to recite for direction before tests are written

Add Comment

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

Mark Waite edited a comment on JENKINS-52490

Re: Plugin should provide GIT_COMMIT_MESSAGE as Environment Variable

I am piv vacation for 've reviewed and commented on the rest of this week [pull request|https://github . Other maintainers may be available, but I am not. I generally don't accept com/jenkinsci/git-plugin/ pull requests that lack tests /796] . However, I'm willing to recite for direction before tests are written

Add Comment