Build times from March = 6 minutes to
May = 23 minutes, we are working on identifying the cause. I
apologize for that.
One build has an error 400 from
repo.eclipse.org, which we could look into. But most of your
failed builds have this message:
18:40:02 22:40:02 [ERROR] Cannot resolve project dependencies:
18:40:02 22:40:02 [ERROR] Software being installed: org.eclipse.egit.github.core 5.11.0.202103091610-r
18:40:02 22:40:02 [ERROR] Missing requirement: org.eclipse.egit.github.core 5.11.0.202103091610-r requires 'java.package; org.eclipse.jgit.annotations [5.11.0,5.12.0)' but it could not be found
Which part of CI is responsible for that?
The EGit M3 build picked up the M2 build of JGit instead of the M3 build.
Looks like this was my fault by pushing the JGit v5.12.0.202105261145-m3 too late.
The EGit build looks for the closest tagged JGit version matching the same major.minor version [1].
If the JGit v5.12.0.202105261145-m3 wasn't pushed when I started the EGit v5.12.0.202105261145-m3 build
it would select the v5.12.0.202105051250-m2 JGit version.
Meanwhile I ran that build again (which couldn't finish since release artefacts can't be redeployed on Nexus) and it picked up
the correct M3 build of JGit. Hence I think me pushing the JGit tag too late was causing this.
Yesterday I ran all the validation builds for M3 locally to shorten the time to get the milestone tagged on the CI.
Would be great if you could identify the root cause of the slowdown of our CI builds.
JGit build times are now 1h or more. They used to be in the range of 20-35min [2].
EGit build times increased from around 25min to around 1 hour [3].
Did we maybe loose the resource packs [4] we had for the JGit and EGit builds ?