[JIRA] (JENKINS-42708) Expose the GIT_URL, BRANCH and COMMIT that originally triggered the build

[eero.aaltonen@iki.fi (JIRA)]

Eero Aaltonen created an issue

Jenkins / JENKINS-42708 Expose the GIT_URL, BRANCH and COMMIT that originally triggered the build Issue Type: Improvement Assignee: Mark Waite Components: git-plugin Created: 2017/Mar/13 9:19 AM Priority: Minor Reporter: Eero Aaltonen Problem: For a Jenkins Job monitoring multiple Git SCMs, the  GIT_URL GIT_BRANCH GIT_COMMIT variables lose information on which repository change triggered the build. The Jenkins job polling / notify logic faithfully keeps track of built commits, but this is lost when the multi-SCM build starts. Request: I propose adding the environment variables that identify which URL/COMMIT/BRANCH caused the build to trigger. I am trying to use this together with commit Commit Notifications, so in my case the original commit included in the notification would be fine. Add Comment

This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e)

[eero.aaltonen@iki.fi (JIRA)]

Eero Aaltonen updated an issue

Jenkins / JENKINS-42708 Expose the GIT_URL, BRANCH and COMMIT that originally triggered the build

Change By: Eero Aaltonen *Problem:*

For a Jenkins Job monitoring multiple Git SCMs, the  GIT_URL GIT_BRANCH GIT_COMMIT

variables lose information on *which repository change* triggered the build. The Jenkins job polling / notify logic faithfully keeps track of built commits, but this is lost when the multi-SCM build starts. *Request:*

I propose adding the environment variables that identify which URL/COMMIT/BRANCH caused the build to trigger. I am trying to use this together with

commit   [Commit Notifications|https://blog.mikesir87.io/2013/04/continuous-integration-with-stash-and-jenkins/], so in my case the original commit included in the notification would be fine.

Add Comment

[eero.aaltonen@iki.fi (JIRA)]

Eero Aaltonen commented on JENKINS-42708

Re: Expose the GIT_URL, BRANCH and COMMIT that originally triggered the build JENKINS-29840 is a related issue.

Add Comment

[eero.aaltonen@iki.fi (JIRA)]

Eero Aaltonen updated an issue

Jenkins / JENKINS-42708

Expose the GIT_URL, BRANCH and COMMIT that originally triggered the build

Change By: Eero Aaltonen *Problem:* For a Jenkins Job monitoring * multiple *  Git SCMs, the

GIT_URL GIT_BRANCH GIT_COMMIT variables lose information on *which repository change* triggered the build. The Jenkins job polling / notify logic faithfully keeps track of built commits, but this is lost when the multi-SCM build starts. *Request:* I propose adding the environment variables that identify which URL/COMMIT/BRANCH caused the build to trigger. I am trying to use this together with

[Commit Notifications|https://blog.mikesir87.io/2013/04/continuous-integration-with-stash-and-jenkins/], so in my case the original commit included in the notification would be fine.

Add Comment

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

Mark Waite assigned an issue to Unassigned

Jenkins / JENKINS-42708 Expose the GIT_URL, BRANCH and COMMIT that originally triggered the build

Change By: Mark Waite Assignee: Mark Waite

Add Comment

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

Mark Waite closed an issue as Won't Fix

Won't implement further changes to support multiple SCM plugin. Use the Jenkins pipeline for multiple SCM use cases.

Jenkins / JENKINS-42708 Expose the GIT_URL, BRANCH and COMMIT that originally triggered the build

Change By: Mark Waite Status: Open Closed Resolution: Won't Fix

Add Comment

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