[JIRA] (JENKINS-48510) Pipeline Milestone step: Adding parameter for milestone classification

2018-10-18 Thread flydive...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Markus Maga commented on  JENKINS-48510  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline Milestone step: Adding parameter for milestone classification   
 

  
 
 
 
 

 
 Jesse Glick perhaps, suggestions welcome  But having milestones that can be bound to one or more parameters makes sense to me. But I don't see a reason not to offer this flexibility, it would give more super powers to parameterised builds   
 

  
 
 
 
 

 
 
 

 
 
 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-48510) Pipeline Milestone step: Adding parameter for milestone classification

2018-10-18 Thread flydive...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Markus Maga commented on  JENKINS-48510  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Pipeline Milestone step: Adding parameter for milestone classification   
 

  
 
 
 
 

 
 I've also been looking for something similar. Our use case is that we have a shared job for deployment, we have multiple multibranch jobs which all trigger a parameterised pipeline job. In this pipeline job I'd like to combine milestones & locks to prevent running simultaneous deployments for the same app to the same environment. I can use locks to only deploy one of each app at a time (different apps can deploy in parallel). But it would be nice to use the milestone with the suggested ordinalGroup in combination with locks using inversePrecedence: true. Do you have an alternative solution to this Antonio Muñiz? I see no need to have to create new jobs for each possible application & environment combination. Did you find any solution Tobias Peitzsch?  
 

  
 
 
 
 

 
 
 

 
 
 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.