[JIRA] (JENKINS-47226) Provide easy access to git branch name in (single branch) Pipeline build

2018-10-31 Thread stephen.alan.conno...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Stephen Connolly assigned an issue to Unassigned  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Removing myself as assignee. My current work assignments do not provide sufficient bandwidth to review these issues and in the majority of cases I am only assigned by virtue of being the default assignee. For the credentials-api and scm-api related plugins I have permission to allocate time reviewing changes to these APIs themselves to ensure these APIs remain cohesive, but that can be handled through PR reviews rather than assigning issues in JIRA  
 

  
 
 
 
 

 
 Jenkins /  JENKINS-47226  
 
 
  Provide easy access to git branch name in (single branch) Pipeline build   
 

  
 
 
 
 

 
Change By: 
 Stephen Connolly  
 
 
Assignee: 
 Stephen Connolly  
 

  
 
 
 
 

 
 
 

 
 
 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-47226) Provide easy access to git branch name in (single branch) Pipeline build

2018-10-16 Thread m...@thedigitalmachine.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Michael Behrns-Miller commented on  JENKINS-47226  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Provide easy access to git branch name in (single branch) Pipeline build   
 

  
 
 
 
 

 
 Ability to build and deploy a specific dockerized branch is seriously crippled by the lack of a branch name variable in Pipeline's Jenkinsfile. Instead, you have to hardcode the branch name in the Jenkinsfile for a given branch, and end up with a bunch of branch merging confusion. An alternative is to move to multibranch pipeline, but that has different keys, different commit triggers, etc. which is just too much. If this variable was available it would definitely simplify our CI. Thanks!  
 

  
 
 
 
 

 
 
 

 
 
 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.