[JIRA] (JENKINS-47617) CHANGE_BRANCH no longer reporting branch name, but instead PR

2018-02-08 Thread r.ach...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rein Achten edited a comment on  JENKINS-47617  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CHANGE_BRANCH no longer reporting branch name, but instead PR   
 

  
 
 
 
 

 
 I've just pinpointed this to v2.2.4 of the bitbucket-branch-source-plugin. In v2.2.3, {{CHANGE_BRANCH}} is still set according to expectation. Looking through the diffs, it seems to be caused by the changes on context of [the following pull request|https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/63] (for JENKINS-45775).[~stephenconnolly] I'm not familiar with the plugin and don't completely understand the [rationale|https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/63/files#r129575824] behind using {{branchName}} instead of {{pull.getSource().getBranch().getName()}} [here|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/761fa289a13ff5750f7fdb8be0c980e688143197/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketSCMSource.java# L65 L657 ], but I reckon this is causing the problem. Can you shed your light on this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
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-47617) CHANGE_BRANCH no longer reporting branch name, but instead PR

2018-02-08 Thread r.ach...@gmail.com (JIRA) 
Title: Message Title


 
 
 
 

 
 
 

 
   
 Rein Achten edited a comment on  JENKINS-47617  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: CHANGE_BRANCH no longer reporting branch name, but instead PR   
 

  
 
 
 
 

 
 I've just pinpointed this to v2.2.4 of the bitbucket-branch-source-plugin. In v2.2.3, {{CHANGE_BRANCH}} is still set according to expectation. Looking through the diffs, it seems to be caused by the changes on context of [the following pull request|https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/63] (for JENKINS-45775). [~stephenconnolly] I'm not familiar with the plugin and don't completely understand the [rationale|https://github.com/jenkinsci/bitbucket-branch-source-plugin/pull/63/files#r129575824] behind using {{branchName}} instead of {{pull.getSource().getBranch().getName()}} [here|https://github.com/jenkinsci/bitbucket-branch-source-plugin/blob/761fa289a13ff5750f7fdb8be0c980e688143197/src/main/java/com/cloudbees/jenkins/plugins/bitbucket/BitbucketSCMSource.java#L65], but I reckon this is causing the problem. Can you shed your light on this?  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

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

 
   
 

  
 

  
 

   





-- 
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.