Status: Closed (View Workflow)
Jenkins 2.204.1 with repository-connector-plugin 1.2.6
Following to Sonatype disabling  the HTTP access to Maven Central on January 15th 2020, the plugin doesn't work anymore (if using the default configuration) as requests to http://repo1.maven.org/maven2/ now returns 501 HTTPS Required . More info from Sonatype can be found here .
A code upgrade is required to now use https://repo1.maven.org/maven2/ as the default configuration.
In the meantime, the current workaround consists to manually edit the link (and add the "s" to "http") in Jenkins Configuration (/jenkins/configure). Also, for systems installed programmatically, one easy workaround consists to drop in the Jenkins install folder (/var/lib/jenkins on Debian systems) the file org.jvnet.hudson.plugins.repositoryconnector.RepositoryConfiguration.xml. The template for this file can be created while manually editing the link on a scratch instance.
A more elaborated workaround might consist to programmatically configure the plugin. While doing so, one might also take the opportunity to use their repository proxy (nexus, artifactory). Here comes the code snippet I used to configure the plugin (with the standard Maven Central).
def repos = GlobalConfiguration.all().get(RepositoryConfiguration.class).repositoryMap
repos.put("central", new Repository("central", "default", "https://repo1.maven.org/maven2", null, null, false))
- is duplicated by
JENKINS-62581 Artifact resolver using http maven central
Still this issue prevails in our project Jenkins also. Is this fixed?
I just created the fix and opened a pull request. See