[JIRA] (JENKINS-42224) Need ability to create reusable chunks of Declarative Pipeline

2019-04-04 Thread nro...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Roosevelt commented on  JENKINS-42224  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Need ability to create reusable chunks of Declarative Pipeline
 

  
 
 
 
 

 
 I would like this as well. But also, it seems like we can make some of those blocks one line, and we could use a preprocessor, if necessary. Just starting to get into this, but seems like groovy should support this already.  
 

  
 
 
 
 

 
 
 

 
 
 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-42224) Need ability to create reusable chunks of Declarative Pipeline

2019-04-04 Thread nro...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Nick Roosevelt commented on  JENKINS-42224  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Need ability to create reusable chunks of Declarative Pipeline
 

  
 
 
 
 

 
 I would like this as well. But also, it seems like we can make some of those blocks one line, and we could use a preprocessor, if necessary. Just starting to get into this, but seems like groovy should support this already.  
 

  
 
 
 
 

 
 
 

 
 
 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-42224) Need ability to create reusable chunks of Declarative Pipeline

2018-04-03 Thread tobilarsch...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Tobias Larscheid commented on  JENKINS-42224  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Need ability to create reusable chunks of Declarative Pipeline
 

  
 
 
 
 

 
 I just opened https://issues.jenkins-ci.org/browse/JENKINS-50548 for defining reusable stages, maybe it is interesting for you as well.  
 

  
 
 
 
 

 
 
 

 
 
 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-42224) Need ability to create reusable chunks of Declarative Pipeline

2017-02-27 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-42224  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Need ability to create reusable chunks of Declarative Pipeline
 

  
 
 
 
 

 
 Ok, been thinking about this some. =) I think we could avoid some of the hassles of inserting GroovyShellDecoratorImpl all over the place for compile-time validating etc by instead putting the Declarative chunks in the resources directory of libraries and using the libraryResource step to get them as strings - then we can use the same logic as in the validateDeclarativePipeline step to do the validation without worrying about breaking other things outside of the Declarative scope. That may or may not make sense. =) The next challenge is figuring out how to insert the chunk into the runtime model. Still working on 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-42224) Need ability to create reusable chunks of Declarative Pipeline

2017-02-21 Thread andrew.ba...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Andrew Bayer commented on  JENKINS-42224  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Need ability to create reusable chunks of Declarative Pipeline
 

  
 
 
 
 

 
 This is an interesting and legitimately challenging problem - needs thinking.  
 

  
 
 
 
 

 
 
 

 
 
 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-42224) Need ability to create reusable chunks of Declarative Pipeline

2017-02-21 Thread bitwise...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman created an issue  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Jenkins /  JENKINS-42224  
 
 
  Need ability to create reusable chunks of Declarative Pipeline
 

  
 
 
 
 

 
Issue Type: 
  Improvement  
 
 
Assignee: 
 Andrew Bayer  
 
 
Components: 
 pipeline-model-definition-plugin  
 
 
Created: 
 2017/Feb/21 4:15 PM  
 
 
Priority: 
  Minor  
 
 
Reporter: 
 Liam Newman  
 

  
 
 
 
 

 
 There is no way to write reusable chunks of Declarative Pipeline configuration.  Jenkinsfile has no facility for this, and shared libraries support only scripted groovy (classes, steps, globals).   
 

  
 
 
 
 

 
 
 

 
 
 Add Comment