| 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? |
