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* 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. 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&timestamp2=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
_______________________________________________
platform-dev mailing list
platform-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/platform-dev

Reply via email to