[INFRA-900] Inconsistent results for repo.jenkins-ci.org and jcentral

[jenkins-infra-bot]

Hi,

I am trying to use jenkins test harness to test some jenkins-job-dsl jobs. For best results I have to install plugins (golang, sbt, github pull request builder, etc.).

While doing this I have figured out that, repo.jenkins-ci.org and jcentral have totally different artifacts for the same artifact-id.

For example for for netbeans insane:

http://repo.jenkins-ci.org/releases/org/netbeans/modules/org-netbeans-insane/RELEASE72/ - the actual jar file is missing
https://jcenter.bintray.com/org/netbeans/modules/org-netbeans-insane/RELEASE72/ - contains the jar file

For the golang plugin:

http://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/golang/1.1/ - all files are there
https://jcenter.bintray.com/org/jenkins-ci/plugins/golang/1.1/ - *.hpi are missing

The problem is here, that gradle finds the artifact in whatever repository is configured to has priority. Then it tries to download the .hpi/.jar files and cannot find them.

When I configure jcentral first I dont get the hpi files for the golang plugin, when I configure the jenkins repo first I cannot get the jar file for netbeans-insane

---

Originally reported by bjoernhaeuser, imported from: Inconsistent results for repo.jenkins-ci.org and jcentral

• status: Open
• priority: Major
• resolution: Unresolved
• imported: 2022/01/10

[jenkins-infra-bot]

rtyler:

I'm not sure I understand the problem here, I don't believe whatever this netbeans module is, is released through our repositories.

I can't find it in JCenter either (https://jcenter.bintray.com/org/netbeans/:modules/org-netbeans-insane/)

[jenkins-infra-bot]

bjoernhaeuser:

No, in Jcenter only RELEASE73 is referenced: https://jcenter.bintray.com/org/netbeans/insane/RELEASE73/

The RELEASE72 dependency is coming from here: https://github.com/jenkinsci/jenkins-test-harness/blob/master/pom.xml#L135

[jenkins-infra-bot]

rtyler:

I'm still not convinced there is an issue here. The POM refers to a very different artifact than what you're referencing in JCenter.

The groupID of org.netbeans.modules would map to a URL path org/netbeans/modules not org/netbeans/insane.

I think this is an issue of either an outdated POM, or perhaps it's referencing a groupId/artifactId which has since been deleted. In repo.jenkins-ci.org pretty much everything (from my understanding) that isn't in org/jenkinsci is mirrored from JCenter.

[jenkins-infra-bot]

danielbeck:

Let's ask Jesse Glick why he uploaded only pom and sources for org-netbeans-insane-RELEASE72 in our Artifactory.

One possible approach is to reference repo.jenkins-ci.org/repo as that's the virtual repository of all repos, both local stuff and mirrored.

[jenkins-infra-bot]

rtyler:

Daniel, I'm bouncing this over to you to follow up with Jesse Glick since I clearly don't understand this issue

[jenkins-infra-bot]

manonnen:

The incomplete org.netbeans.modules:org-netbeans-insane:RELEASE72 package can cause issues with Gradle dependency resolution, as explained in this Gradle bug:

https://github.com/gradle/gradle/issues/3666

 

It would be good if either the missing jar file (as available on JCenter) would also be uploaded to the jenkins-ci repo or if the artifact would be removed completely. What is the use of hosting only the sources JAR anyway?

[jenkins-infra-bot]

0x89:

Please remove the incomplete  org.netbeans.modules:org-netbeans-insane:RELEASE72 package.

[jenkins-infra-bot]

0x89:

One possible approach is to reference repo.jenkins-ci.org/repo as that's the virtual repository of all repos, both local stuff and mirrored.

tried that, didn't work.

[jenkins-infra-bot]

danielbeck:

Jesse Glick Ping

[jenkins-infra-bot]

danielbeck:

Based on a recent investigation, JCenter is the worst and needs to die in a fire. We're never going to align with that repo's messed up content.

(Individual artifacts – sure. But we won't use it as a reference for anything. That we include it in the virtual repo and download dependencies from there is bad enough.)

[jenkins-infra-bot]

amirbarkal:

We're also suffering from the missing "org-netbeans-insane-RELEASE72" artifact in https://repo.jenkins-ci.org/releases.
The error in gradle:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':compileIntegrationTestGroovy'.
> Could not resolve all files for configuration ':integrationTestCompileClasspath'.
   > Could not find org-netbeans-insane.jar (org.netbeans.modules:org-netbeans-insane:RELEASE72).
     Searched in the following locations:
  https://repo.jenkins-ci.org/releases/org/netbeans/modules/org-netbeans-insane/RELEASE72/org-netbeans-insane-RELEASE72.jar

[jenkins-infra-bot]

cvakiitho:

Workaround is to add nebeans repo at the top of repositories in gradle: 

repositories {
 maven { url "https://netbeans.apidesign.org/maven2" }