Has anyone been able to make any progress on this?

I have a new Jenkins 2 cluster up and running, and I've created declarative 
Jenkinsfile pipelines for each app repo. This works excellent for building 
all app branches and PR's. However, we have some more generic parameterized 
deploy jobs that we'd like to add. The Github Organization plugin is also 
currently used for automatically scanning all of our repos, and when 
Jenkinsfile's are found, jobs are automatically built - but under the 
org/repo/branch namespace.

We have a generic jenkins repo that hosts some legacy Jenkins Job DSL 
plugin scripts. Ideally, we'd like to add a Jenkinsfile to this repo, and 
have that job define these generic deploy and utility jobs. (perhaps via 
groovy loads) I would prefer to use the newer Jenkinsfile-based syntax - 
declarative or scripted is fine. I am hoping that I don't have to resort 
back to the Jenkins Jobs DSL plugin though. 

Is there any simple way to accomplish this?

On Monday, October 3, 2016 at 5:40:49 AM UTC-4, Sorin Ionuț Sbârnea wrote:
>
> Did you finish your implementation? Groovy is far from being my native 
> language and it would be really helpful if you could share a snippet that 
> is doing the subdirectory Jenkinsfile discovery and loading.
>
> On Thursday, July 21, 2016 at 1:43:18 AM UTC+1, slide wrote:
>>
>> The way I am planning on doing this is with the findFiles and load 
>> functions. I'll use findFiles in my Jenkinsfile to look for other build 
>> files further in the repo and create jobs from those to run. The other 
>> files will not necessarily be the same setup as a Jenkinsfile, but will use 
>> the pipeline syntax.
>>
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a219dde2-d90c-4ab9-a738-51ab6487a800%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to