Date
1 - 3 of 3
[tsc][releng][integration] Jenkins pipelines with Blue Ocean
Anil Belur
Hello all,
I have installed Jenkins Blue Ocean on the ODL sandbox environment. Although Blue Ocean is installed on the Jenkins Sandbox environment, all existing CI jobs need to be migrated to pipelines [2.] and Jenkinsfile to be created for each of the Job templates.
On the left hand side of the Jenkins Sandbox landing page you should now be able see "Blue Ocean" link.
Note: Blue Ocean does not support tabs and all jobs would be listed on a single giant page.
Regards,
Anil Belur
Anil Belur
Robert Varga
n 01/10/2021 09:30, Anil Belur wrote:
Now pardon my ignorance, but what is the relationship between JJB YAMLs and Jenkinsfile? What I am looking for is some hint as to how I would go about converting them.
Thanks,
Robert
Hello all,Awesome, this is what we want to be aiming for and we will be establishing MRI project release process in terms of pipelines as soon as we get the green light :)
I have installed Jenkins Blue Ocean on the ODL sandbox environment. Although Blue Ocean is installed on the Jenkins Sandbox environment, all existing CI jobs need to be migrated to pipelines [2.] and Jenkinsfile to be created for each of the Job templates.
Now pardon my ignorance, but what is the relationship between JJB YAMLs and Jenkinsfile? What I am looking for is some hint as to how I would go about converting them.
On the left hand side of the Jenkins Sandbox landing page you should now be able see "Blue Ocean" link.I think this will be fine -- we expect to have far fewer jobs than we currently have.
Note: Blue Ocean does not support tabs and all jobs would be listed on a single giant page.
Thanks,
Robert
Regards,
Anil Belur
[1.] https://jenkins.opendaylight.org/sandbox/ <https://jenkins.opendaylight.org/sandbox/>
[2.] https://jenkins.opendaylight.org/sandbox/blue/organizations/jenkins/pipelines <https://jenkins.opendaylight.org/sandbox/blue/organizations/jenkins/pipelines>
[3.] https://gerrit.linuxfoundation.org/infra/admin/repos/releng/pipelines <https://gerrit.linuxfoundation.org/infra/admin/repos/releng/pipelines>
On 10/1/21 02:47, Robert Varga wrote:
That being said, all verify/merge/release operations all end up going through the same pipeline with the LF pipeline library that we've been developing. So, yes, all your projects that migrate to pipelines will effectively go down to just one or a few named pipelines.
-Andy-
--
Andrew J Grimberg
Manager Release Engineering
The Linux Foundation
Now pardon my ignorance, but what is the relationship between JJB YAMLs and Jenkinsfile? What I am looking for is some hint as to how I would go about converting them.So, pipelines live in a .jenkinsfile that resides at the root level of a repository. We will still need JJB to stub in the reading of that file which then defines _all_ the pipelines for a given project.
That being said, all verify/merge/release operations all end up going through the same pipeline with the LF pipeline library that we've been developing. So, yes, all your projects that migrate to pipelines will effectively go down to just one or a few named pipelines.
The saving grace here is that Blue Ocean doesn't load all known jobs right away. It's got infinite scroll and will do so as you scroll down, or you can use the search feature to find jobs that match the search. It _does_ work with the freestyle jobs, but not as well as a native pipeline.On the left hand side of the Jenkins Sandbox landing page you should now be able see "Blue Ocean" link.I think this will be fine -- we expect to have far fewer jobs than we currently have.
Note: Blue Ocean does not support tabs and all jobs would be listed on a single giant page.
-Andy-
--
Andrew J Grimberg
Manager Release Engineering
The Linux Foundation