Where are the maven jenkins-ci dependencies?

Using Jenkins Ask a question
1

Hello, I have some unit tests failing on our Jenkins shared librairies and it seems it is because maven can’t get the or.jenkins-ci dependencies.

 required artifacts missing:
[main] ERROR org.apache.maven.cli.MavenCli -   org.jenkins-ci.plugins:jobConfigHistory:jar:1259.v8f2448483000
[main] ERROR org.apache.maven.cli.MavenCli -   org.jenkins-ci.plugins.workflow:workflow-job:jar:1436.vfa_244484591f
[main] ERROR org.apache.maven.cli.MavenCli -   org.jenkins-ci.plugins:git:jar:5.4.1
[main] ERROR org.apache.maven.cli.MavenCli -   org.jenkins-ci.plugins:branch-api:jar:2.1178.v969d9eb_c728e
[main] ERROR org.apache.maven.cli.MavenCli -   org.jenkins-ci.plugins.workflow:workflow-cps:jar:3961.ve48ee2c44a_b_3
[main] ERROR org.apache.maven.cli.MavenCli -   org.jenkins-ci.main:jenkins-core:jar:2.462.2
[main] ERROR org.apache.maven.cli.MavenCli -   org.jenkins-ci.plugins:matrix-auth:jar:3.2.2
[main] ERROR org.apache.maven.cli.MavenCli -   org.jenkins-ci.plugins:embeddable-build-status:jar:237.v37e2c03964c9

It’s not a central connexion error, only org.jenkins-ci dependencies fails:

mvn dependency:get -DartifactId=git -DgroupId=org.jenkins-ci.plugins -Dversion=5.7.0 -Dpackaging=jar -Drepository=https://repo1.maven.org/maven2
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------

 mvn dependency:get -DartifactId=gson -DgroupId=com.google.code.gson -Dversion=2.12.1 -Dpackaging=jar -Drepository==https://repo1.maven.org/maven2
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------

If you look directly at Central Repository: org/jenkins-ci it’s basically empty

Any help appreciated

2

What are you trying to build? Note that Jenkins has it’s own repository Index of public/

3

Thanks! I’ve just checked we don’t have this repo in our virtual public repository.
I’m not sure if it was removed by mistake or it was working from some old cache from central.