[JIRA] (JENKINS-47129) Executing multiple declaritive pipelines into a scripted pipeline is not possible anymore

2019-10-22 Thread bitwise...@gmail.com (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 Liam Newman closed an issue as Not A Defect  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
 Bulk closing resolved issues.   
 

  
 
 
 
 

 
 Jenkins /  JENKINS-47129  
 
 
  Executing multiple declaritive pipelines into a scripted pipeline is not possible anymore
 

  
 
 
 
 

 
Change By: 
 Liam Newman  
 
 
Status: 
 Resolved Closed  
 

  
 
 
 
 

 
 
 

 
 
 Add Comment  
 

  
 

  
 
 
 
  
 

  
 
 
 
 

 
 This message was sent by Atlassian Jira (v7.13.6#713006-sha1:cc4451f)  
 
 

 
   
 

  
 

  
 

   





-- 
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.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-issues/JIRA.185530.1506426878000.16459.1571801052299%40Atlassian.JIRA.


[JIRA] (JENKINS-47129) Executing multiple declaritive pipelines into a scripted pipeline is not possible anymore

2018-09-18 Thread chantiv...@yahoo.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 chanti vlad edited a comment on  JENKINS-47129  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Executing multiple declaritive pipelines into a scripted pipeline is not possible anymore
 

  
 
 
 
 

 
 Hi [~abayer] , [~roel0] and [~abhishekmukherg],i am facing the exact same problem, where i was hoping to have the following set up: * git repo A stores all generic Jenkins pipelines, which need specific env variables to be parameterized * git repo B has a Jenkinsfile that gets executed pre merge on changes in the repo B. This Jenkinsfile would do some things, and then clone the repo A, set the env variable properly, load a Jenkinsfile from A and run it as "sub pipeline".Do i understand you correctly that the best way to do this is to have the generic part in repo A as scripted and not  delcarative  declarative  ?If yes, why this limitation?   
 

  
 
 
 
 

 
 
 

 
 
 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-47129) Executing multiple declaritive pipelines into a scripted pipeline is not possible anymore

2018-09-18 Thread chantiv...@yahoo.fr (JIRA)
Title: Message Title


 
 
 
 

 
 
 

 
   
 chanti vlad commented on  JENKINS-47129  
 

  
 
 
 
 

 
 
  
 
 
 
 

 
  Re: Executing multiple declaritive pipelines into a scripted pipeline is not possible anymore
 

  
 
 
 
 

 
 Hi Andrew Bayer , roel postelmans and Abhishek Mukherjee, i am facing the exact same problem, where i was hoping to have the following set up: 
 
git repo A stores all generic Jenkins pipelines, which need specific env variables to be parameterized 
git repo B has a Jenkinsfile that gets executed pre merge on changes in the repo B. This Jenkinsfile would do some things, and then clone the repo A, set the env variable properly, load a Jenkinsfile from A and run it as "sub pipeline". 
 Do i understand you correctly that the best way to do this is to have the generic part in repo A as scripted and not delcarative ? If yes, why this limitation?    
 

  
 
 
 
 

 
 
 

 
 
 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.