[JIRA] (JENKINS-58313) Expose pullrequest source commit hash to pipeline env variables

[julien.henry@sonarsource.com (JIRA)]

Julien HENRY created an issue

Jenkins / JENKINS-58313 Expose pullrequest source commit hash to pipeline env variables Issue Type: New Feature Assignee: Julien HENRY Components: branch-api-plugin Created: 2019-07-03 08:34 Environment: GitHub, Bitbucket Priority: Minor Reporter: Julien HENRY Some operations on pullrequests (like reporting build statuses or creating reports) require to pass the commit hash of the pullrequest, as known by the remote system. When using the branch plugin, Jenkins can create a merge commit between the PR source and target branch. It makes it difficult for a pipeline script to retrieve the original source commit hash. My suggestion is to add a new environment variable, similar to CHANGE_BRANCH, that would expose this source commit. We could name this variable CHANGE_BRANCH_COMMIT_ID, to make it consistent with existing CHANGE_BRANCH and COMMIT_ID. See original discussion: https://groups.google.com/d/topic/jenkinsci-dev/-ojqklsaKbw/discussion Add Comment

This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

[julien.henry@sonarsource.com (JIRA)]

Julien HENRY updated an issue

Jenkins / JENKINS-58313 Expose pullrequest source commit hash to pipeline env variables

Change By: Julien HENRY Some operations on pullrequests (like reporting build statuses or creating reports) require to pass the commit hash of the pullrequest branch head , as known by the remote system. When using the branch plugin, Jenkins can may create a merge commit between the PR source and target branch. It makes it difficult for a pipeline script to retrieve the original source commit hash. My suggestion is to add a new environment variable, similar to {{CHANGE_BRANCH}}, that would expose this source commit. We could name this variable {{CHANGE_BRANCH_COMMIT_ID}}, to make it consistent with existing {{CHANGE_BRANCH}} and {{COMMIT_ID}}.

See original discussion: https://groups.google.com/d/topic/jenkinsci-dev/-ojqklsaKbw/discussion

Example of operations requiring the PR head commit hash: * https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/%7Busername%7D/%7Brepo_slug%7D/commit/%7Bnode%7D/statuses/build * https://developer.atlassian.com/server/bitbucket/how-tos/code-insights/ * https://developer.github.com/v3/repos/statuses/ * https://developer.github.com/v3/checks/runs/#create-a-check-run

Add Comment