[JIRA] (JENKINS-34938) Access commit SHA of webhook payload in Jenkinsfile

2016-11-08 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick resolved as Won't Do  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-34938  
 
 
  Access commit SHA of webhook payload in Jenkinsfile   
 

  
 
 
 
 

 
Change By: 
 Jesse Glick  
 
 
Status: 
 Open Resolved  
 
 
Resolution: 
 Won't Do  
 

  
 
 
 
 

 
 
 

 
 
 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-34938) Access commit SHA of webhook payload in Jenkinsfile

2016-11-02 Thread aburdajew...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan BURDAJEWICZ commented on  JENKINS-34938  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Access commit SHA of webhook payload in Jenkinsfile   
 

  
 
 
 
 

 
  thanks Jesse Glick. I Think this can be closed.  
 

  
 
 
 
 

 
 
 

 
 
 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-34938) Access commit SHA of webhook payload in Jenkinsfile

2016-10-13 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-34938  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Access commit SHA of webhook payload in Jenkinsfile   
 

  
 
 
 
 

 
 

the commit that triggers the build
 Not a very well-defined concept in Jenkins. There may be no such commit, or many.  
 

  
 
 
 
 

 
 
 

 
 
 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-34938) Access commit SHA of webhook payload in Jenkinsfile

2016-10-12 Thread aburdajew...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan BURDAJEWICZ commented on  JENKINS-34938  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Access commit SHA of webhook payload in Jenkinsfile   
 

  
 
 
 
 

 
 I understand this is not gonna resolved this. Originally, the idea of this RFE is to guarantee that the commit that triggers the build is the commit that is being checkout too.  
 

  
 
 
 
 

 
 
 

 
 
 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-34938) Access commit SHA of webhook payload in Jenkinsfile

2016-10-05 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-34938  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Access commit SHA of webhook payload in Jenkinsfile   
 

  
 
 
 
 

 
 Yes, that is true in Jenkins generally. How do think the stated RFE is going to address that?  
 

  
 
 
 
 

 
 
 

 
 
 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-34938) Access commit SHA of webhook payload in Jenkinsfile

2016-07-05 Thread aburdajew...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Allan BURDAJEWICZ commented on  JENKINS-34938  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Access commit SHA of webhook payload in Jenkinsfile   
 

  
 
 
 
 

 
 The problem is that it is not possible to trigger one build per commit.  
 

  
 
 
 
 

 
 
 

 
 
 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-34938) Access commit SHA of webhook payload in Jenkinsfile

2016-07-05 Thread jgl...@cloudbees.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Jesse Glick commented on  JENKINS-34938  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Access commit SHA of webhook payload in Jenkinsfile   
 

  
 
 
 
 

 
 Yes, that is by design. Jenkins will build the latest branch head. What is the problem?  
 

  
 
 
 
 

 
 
 

 
 
 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.