[JIRA] (JENKINS-39838) CHANGE_ variables are missing
Title: Message Title Stephen Connolly closed an issue as Not A Defect Seems like this was a configuration error (that the configuration options are non-obvious is a separate issue)... Closing this issue in any case as with the 2.0 series of GitHub Branch Source the GitHub Organization Folders plugin is dead (functionality moved to GitHub Branch Source) Jenkins / JENKINS-39838 CHANGE_ variables are missing Change By: Stephen Connolly Status: Open Closed Resolution: Not A Defect Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subs
[JIRA] (JENKINS-39838) CHANGE_ variables are missing
Title: Message Title
Christian Höltje created an issue
Jenkins / JENKINS-39838
CHANGE_ variables are missing
Issue Type:
Bug
Assignee:
Kohsuke Kawaguchi
Components:
github-organization-folder-plugin
Created:
2016/Nov/17 8:03 PM
Environment:
github-organization-folder-plugin: 1.5 branch-api-plugin: 1.11.1
Priority:
Minor
Reporter:
Christian Höltje
When using the GitHub Organization Folder, none of the builds have the CHANGE_* variables set. I have tried both sh 'env | sort` and {{echo "$ {env.CHANGE_ID} "}}.
Add Comment
[JIRA] (JENKINS-39838) CHANGE_ variables are missing
Title: Message Title
Christian Höltje updated an issue
Jenkins / JENKINS-39838
CHANGE_ variables are missing
Change By:
Christian Höltje
When using the GitHub Organization Folder, none of the builds have the {{CHANGE_*}} variables set.I have tried both {{sh 'env | sort ` ' }} and {{echo "${env.CHANGE_ID}"}}. I'm expecting these to be set:* {{CHANGE_ID}}* {{CHANGE_URL}}* {{CHANGE_TITLE}}* {{CHANGE_AUTHOR}}* {{CHANGE_AUTHOR_DISPLAY_NAME}}* {{CHANGE_AUTHOR_EMAIL}}* {{CHANGE_TARGET}}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-39838) CHANGE_ variables are missing
Title: Message Title
Christian Höltje updated an issue
Jenkins / JENKINS-39838
CHANGE_ variables are missing
Change By:
Christian Höltje
When using the GitHub Organization Folder, none of the builds have the {{CHANGE_*}} variables set.I have tried both {{sh 'env | sort'}} and {{echo "$ \ {env.CHANGE_ID}"}}.I'm expecting these to be set:* {{CHANGE_ID}}* {{CHANGE_URL}}* {{CHANGE_TITLE}}* {{CHANGE_AUTHOR}}* {{CHANGE_AUTHOR_DISPLAY_NAME}}* {{CHANGE_AUTHOR_EMAIL}}* {{CHANGE_TARGET}}
Add Comment
This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c)
--
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-39838) CHANGE_ variables are missing
Title: Message Title Andrew Turgeon commented on JENKINS-39838 Re: CHANGE_ variables are missing I want to point out the CHANGE_* variables ARE populated when then build is started from a pull request on a forked repository. When I attempt to create a branch on the main repository then create a pull request to merge into master, the variables are not populated (not entirely sure how it determines what a pull request "is" in that case). Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39838) CHANGE_ variables are missing
Title: Message Title Viachaslau Kabak commented on JENKINS-39838 Re: CHANGE_ variables are missing Could you please also add following variables: Source_branch Repository_owner (organization) repository_name sha (commit_sha) the last one is very important Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39838) CHANGE_ variables are missing
Title: Message Title Aidan Steele commented on JENKINS-39838 Re: CHANGE_ variables are missing Andrew Turgeon I was struggling with this as well and found that changing the configuration from Build origin branches also filed as PRs (default checked) to Build origin PRs (merged with base branch) was enough to get the env vars set in my jobs. Add Comment This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- 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-39838) CHANGE_ variables are missing
Title: Message Title Barathwaja S commented on JENKINS-39838 Re: CHANGE_ variables are missing Is there any progress on this? Need some of the above env. variables to be used in a project. Any ETA on this? Ref. https://issues.jenkins-ci.org/browse/JENKINS-40486 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-39838) CHANGE_ variables are missing
Title: Message Title Barathwaja S edited a comment on JENKINS-39838 Re: CHANGE_ variables are missing Is there any progress on this? Need some of the above env. variables to be used in a project. Any ETA on this? Ref. [ JENKINS-40486| https://issues.jenkins-ci.org/browse/JENKINS-40486 |JENKINS-40486 ] 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-39838) CHANGE_ variables are missing
Title: Message Title Amir Barkal edited a comment on JENKINS-39838 Re: CHANGE_ variables are missing When configuring a multibranch pipeline repository to detect Pull Requests from GitHub, I get only the following CHANGE_* env variables populated properly :CHANGE_AUTHORCHANGE_AUTHOR_DISPLAY_NAMECHANGE_BRANCHCHANGE_IDCHANGE_TARGETCHANGE_TITLECHANGE_URL The +* CHANGE_AUTHOR_EMAIL *+ var is critically missing from this list, which is paramount to alert users about regressions in their pull requests. Environment:Jenkins ver. 2.128 GitHub Branch Source Plugin 2.3.6 (latest)Pipeline: Multibranch 2.19 (latest) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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-39838) CHANGE_ variables are missing
Title: Message Title Amir Barkal commented on JENKINS-39838 Re: CHANGE_ variables are missing When configuring a multibranch pipeline repository to detect Pull Requests from GitHub, I get only the following CHANGE_* env variables populated: CHANGE_AUTHOR CHANGE_AUTHOR_DISPLAY_NAME CHANGE_BRANCH CHANGE_ID CHANGE_TARGET CHANGE_TITLE CHANGE_URL The CHANGE_AUTHOR_EMAIL var is critically missing from this list, which is paramount to alert users about regressions in their pull requests. Environment: Jenkins ver. 2.128 GitHub Branch Source Plugin 2.3.6 (latest) Pipeline: Multibranch 2.19 (latest) Add Comment This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396) -- 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.
