Re: [platform-dev] [eclipse-dev] ATTENTION: Turn off of git protocol
|If it's helpful, we can install the following plugin to your jenkins instances https://github.com/jenkinsci/declarative-pipeline-migration-assistant-plugin (documentation 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.
Manager — Release Engineering and Technology | Eclipse Foundation
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 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 <akurtako@xxxxxxxxxx>
To: "General development mailing list of the Eclipse project." <eclipse-dev@xxxxxxxxxxx>, "Eclipse platform general developers list." <platform-dev@xxxxxxxxxxx>, "Eclipse PDE general developers list." <pde-dev@xxxxxxxxxxx>, Equinox development mailing list <equinox-dev@xxxxxxxxxxx>, "Eclipse JDT general developers list." <jdt-dev@xxxxxxxxxxx>
Date: 25-06-2021 22:13
Subject: [EXTERNAL] [jdt-dev] ATTENTION: Turn off of git protocol
Sent by: "jdt-dev" <jdt-dev-bounces@xxxxxxxxxxx>
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.gitrefs/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 refs/changes/21/180221/4" returned status code 128:
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. 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 .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 KurtakovRed Hat Eclipse Team_______________________________________________
jdt-dev mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jdt-dev
_______________________________________________eclipse-dev mailing listeclipse-dev@xxxxxxxxxxxTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/eclipse-dev
Description: Message signed with OpenPGP