News for hackers. Stuff that matters.

hrmpw

Re:New UX for Jenkins: Blue Ocean 1.0 on Wednesday April 05, 2017 @11:35PM (#14047735)
Are there any features that could push it over the top?
Re:New UX for Jenkins: Blue Ocean 1.0 on Wednesday April 05, 2017 @11:33PM (#14047730)
I was playing around with a combination of Pipeline and Job-DSL and created this as a POC:

https://gist.github.com/HRMPW/9b2a3ccbdc370e0a7c9cb541be229d...

This is a Job-DSL seed job written in Declarative Pipeline that pulls in your Organization based on a build parameter and creates two jobs for every repo:

1. A multibranch Pipeline job that is based on the Jenkinsfile that will work across all branches and PRs.

2. A deploy job for the repo that is defined in a "jenkinsfile.deploy" file in the repo. This isn't a multibranch job but can be run on any branch based on a parameter for the branch.

This is a very simplistic implementation but could be expanded on further.

Re:New UX for Jenkins: Blue Ocean 1.0 on Wednesday April 05, 2017 @11:28PM (#14047703)
Why do you need them to be separate Pipelines? Because it is convenient or for other reasons?

Do you want everyone of these jobs in every branch that you create? In Pull Requests? Do you want all of these jobs to automatically trigger on every push the repo?

It's possible to do all of these steps in a single Pipeline but I'm curious why you would want to separate it?