|Re: [jgit-dev] JGit Bot failing with "hudson" error|
Hi Anna,That's a strange problem, earlier this week we fixed the bazel build starting from branch stable-5.13 andmerged that up to master. While doing that I ran both the bazel build and the maven build for each of thebranches and they succeeded.Since Tuesday all builds on branch stable-6.4 or newer fail with strange classpath issues.I ran git bisect between stable-6.3 and master and found that jgit commit b398bb91ab28b799ea39dc2d1b5bd0b849392443(https://git.eclipse.org/r/c/jgit/jgit/+/196333) is causing the problem. This change configured the dash license-tool-pluginto fail the build if any dependency isn't yet license-approved by Eclipse. This commit was introduced on branch stable-6.4and submitted on Oct 15, 2022. This worked for 6 months and started failing this Tuesday. I think the problem is that wedepend on the plugin since it didn't yet publish a release. This means we depend on thelatest build published for this plugin which can change any time.2 commits were merged for the plugin on Apr 24I guess one of them is the culprit.I conclude that the dash license-tool-plugin recentlyb398bb91ab28b799ea39dc2d1b5bd0b849392443 fixes the problem for the jgit build.I will try to build the dash license-tool-plugin locally and bisect its history to identify the change that broke the jgit build.
-MatthiasOn Thu, Apr 27, 2023 at 7:14 PM Anna Papitto via jgit-dev <jgit-dev@xxxxxxxxxxx> wrote:Hi Matthias,Thanks for taking a look!The portion that you highlighted seems to say that the org.osgi.framework.BundleActivator class is not found in org.eclipse.jgit-6.6.0-SNAPSHOT.jar classpath.How did you determine that is due to a network error in the japicmp plugin?Is 6.6.0 actually the previous jgit release, or is it the upcoming one?If 6.6.0 is the previous jgit release, how could we get the japicmp plugin to succeed?If 6.6.0 is actually the upcoming release, is it possible that recent dependency changes https://git.eclipse.org/r/c/jgit/jgit/+/201348 (and https://git.eclipse.org/r/c/jgit/jgit/+/201464) have disrupted the classpath?Best,AnnaOn Wed, Apr 26, 2023 at 2:23 PM Sohn, Matthias <matthias.sohn@xxxxxxx> wrote:I think this job failed due to this error:
00:49:41 [ERROR] Failed to execute goal com.github.siom79.japicmp:japicmp-maven-plugin:0.17.1:cmp (default) on project org.eclipse.jgit.archive: Execution default of goal com.github.siom79.japicmp:japicmp-maven-plugin:0.17.1:cmp failed: Could not load 'Class not found: org.osgi.framework.BundleActivator': org.osgi.framework.BundleActivator. Please make sure that all libraries have been added to the classpath (CLASSPATH=:/home/jenkins/agent/workspace/stable/jgit.gerrit-pipeline.java11/repo/org.eclipse.jgit/target/org.eclipse.jgit-6.6.0-SNAPSHOT.jar:/home/jenkins/agent/workspace/stable/jgit.gerrit-pipeline.java11/repo/org.eclipse.jgit.archive/target/org.eclipse.jgit.archive-6.6.0-SNAPSHOT.jar:) or try the option '--ignore-missing-classes'. -> [Help 1]
The japicmp plugin is used to compute API changes compared to the previous jgit release.
I guess there was a network issue when japicmp tried to access the artefacts of the previous release.
Does anyone familiar with the JGit Bot build system have an idea about why all CL uploads from today (April 25) are failing with a "hudson" error?
https://ci.eclipse.org/jgit/job/stable/job/jgit.gerrit-pipeline.java11/3577/console shows an example failure:
https://git.eclipse.org/r/q/status:open+-is:wip+repo:jgit/jgit shows all recent verifications failing:
Anna Papitto (she)
Google San Francisco--_______________________________________________Anna Papitto (she)Software EngineerGit-on-BorgGoogle San Francisco
jgit-dev mailing list
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jgit-dev
Back to the top