If it's helpful, we can install the following plugin to your jenkins instances https://github.com/jenkinsci/declarative-pipeline-migration-assistant-plugin <https://github.com/jenkinsci/declarative-pipeline-migration-assistant-plugin> (documentation https://docs.cloudbees.com/docs/admin-resources/latest/pipelines/declarative-pipeline-migration-assistant <https://docs.cloudbees.com/docs/admin-resources/latest/pipelines/declarative-pipeline-migration-assistant>).
In order to manage expectations, the EF Releng has no experience with this plugin. But given it's maintained by Cloudbees for its own commercial offering, my guess is that it's pretty robust. Cheers, Mikaël Barbero Manager — Release Engineering and Technology | Eclipse Foundation 🐦 @mikbarbero Eclipse Foundation <http://www.eclipse.org/>: The Platform for Open Innovation and Collaboration > On 26 Jun 2021, at 08:08, Sravan K Lakkimsetti <sravankum...@in.ibm.com> > wrote: > > Hi Alex, > > This is an excellent idea. We should move to Jenkins File in all the jobs. I > did move some jobs last year. But the number of jobs to be done is over > whelming for me. If we do this we have to divide and conquer here. > There are two steps here. > 1. Convert the jobs to Jenkins pipelines from freestyle > 2. Add pipelines to respective git repositories. > > Thanks and Regards, > Sravan > > Sravan Kumar Lakkimsetti > IBM India Pvt Ltd, > Embassy Golf Links Business Park, D Block, > Off Indiranagar-Kormangla Inner Ring Road, > Bangalore - 560071, India > > <graycol.gif>Aleksandar Kurtakov ---25-06-2021 22:13:53---It is quite likely > that you'll start seeing gerrit verification builds and other jenkins jobs > failin > > From: Aleksandar Kurtakov <akurt...@redhat.com <mailto:akurt...@redhat.com>> > To: "General development mailing list of the Eclipse project." > <eclipse-...@eclipse.org <mailto:eclipse-...@eclipse.org>>, "Eclipse platform > general developers list." <platform-dev@eclipse.org > <mailto:platform-dev@eclipse.org>>, "Eclipse PDE general developers list." > <pde-...@eclipse.org <mailto:pde-...@eclipse.org>>, Equinox development > mailing list <equinox-...@eclipse.org <mailto:equinox-...@eclipse.org>>, > "Eclipse JDT general developers list." <jdt-...@eclipse.org > <mailto:jdt-...@eclipse.org>> > Date: 25-06-2021 22:13 > Subject: [EXTERNAL] [jdt-dev] ATTENTION: Turn off of git protocol > Sent by: "jdt-dev" <jdt-dev-boun...@eclipse.org > <mailto:jdt-dev-boun...@eclipse.org>> > > > > > It is quite likely that you'll start seeing gerrit verification builds and > other jenkins jobs failing with " Command "git fetch --tags --force > --progress -- git://git.eclipse.org/gitroot/platform/eclipse.platform.ui.git > <git://git.eclipse.org/gitroot/platform/eclipse.platform.ui.git>refs/changes/21/180221/4" > It is quite likely that you'll start seeing gerrit verification builds and > other jenkins jobs failing with " > Command "git fetch --tags --force --progress -- > git://git.eclipse.org/gitroot/platform/eclipse.platform.ui.git > <http://git.eclipse.org/gitroot/platform/eclipse.platform.ui.git> > refs/changes/21/180221/4" returned status code 128: > 18:15:40 stdout: > 18:15:40 stderr: fatal: read error: Connection reset by peer" > > This is due to https://bugs.eclipse.org/bugs/show_bug.cgi?id=574076 > <https://bugs.eclipse.org/bugs/show_bug.cgi?id=574076>. Fix is as simple as > changing to https url as done here > https://ci.eclipse.org/platform/job/eclipse.platform.ui-Gerrit/jobConfigHistory/showDiffFiles?timestamp1=2021-05-07_05-05-43×tamp2=2021-06-25_12-29-31 > > <https://ci.eclipse.org/platform/job/eclipse.platform.ui-Gerrit/jobConfigHistory/showDiffFiles?timestamp1=2021-05-07_05-05-43×tamp2=2021-06-25_12-29-31> > . > Unfortunately this would be quite time consuming to figure out every single > place where git:// url is used so keep an eye and fix your Jenkins jobs > accordingly. > > I want to start another conversation as it seems good timing: > Isn't it time to start using Jenkinsfile for each git repository and use that > to trigger gerrit builds? > That would make our scripts easier to grep and find/automate such changes in > the future. If there are few others interested in helping out and finding out > such work beneficial I would like to discuss with them how we can best handle > this change. > > -- > Aleksandar Kurtakov > Red Hat Eclipse Team_______________________________________________ > jdt-dev mailing list > jdt-...@eclipse.org <mailto:jdt-...@eclipse.org> > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/jdt-dev > <https://www.eclipse.org/mailman/listinfo/jdt-dev> > > > > > _______________________________________________ > eclipse-dev mailing list > eclipse-...@eclipse.org <mailto:eclipse-...@eclipse.org> > To unsubscribe from this list, visit > https://www.eclipse.org/mailman/listinfo/eclipse-dev > <https://www.eclipse.org/mailman/listinfo/eclipse-dev>
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ platform-dev mailing list platform-dev@eclipse.org To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/platform-dev
