distributionManagement is specified in the plugin parent pom, so you should either add your own distributionManagement to your pom, like here https://github.com/jenkinsci/repo-plugin/blob/master/pom.xml#L122 or migrate to the latest plugin parent.
/B On Thu, Aug 25, 2016 at 3:49 PM, Gabe Montero <[email protected]> wrote: > I ran into the same issue, and updated my ~/.m2/settings.xml file's > <server> entry to point to repo.jenkins-ci.org instead of > maven.jenkins-ci.org, > but when running mvn release:prepare release:perform afterward, the deploy > step still tries to access maven.jenkins-ci.org. > > I also tried clearing out the cache for the plugin ( > https://github.com/jenkinsci/openshift-pipeline-plugin) I'm trying to > update under ~/.m2/repository as well. Still no luck. > > Any suggestions? > > thanks > > On Saturday, August 20, 2016 at 10:41:51 PM UTC-4, Daniel Beck wrote: >> >> This host name is obsolete (and has been for years, but now Tyler pulled >> the plug). Update to the plugins POM 2.6 or newer, or override the host to >> be used to point to repo.jenkins-ci.org. >> >> > On 21.08.2016, at 04:40, Mark Waite <[email protected]> wrote: >> > >> > I received the following error message while trying to deploy a new >> version of the git client plugin: >> > >> > [INFO] [ERROR] Failed to execute goal >> > org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy >> (default-deploy) on project git-client: Failed to deploy artifacts: Could >> not transfer artifact org.jenkins-ci.plugins:git-client:hpi:1.20.1 >> from/to maven.jenkins-ci.org (http://maven.jenkins-ci.org:8 >> 081/content/repositories/releases): Connect to maven.jenkins-ci.org:8081 >> [maven.jenkins-ci.org/199.193.196.24] failed: Connection refused -> >> [Help 1] >> > >> > Any hints what mistake I've made? >> > >> > Thanks, >> > Mark Waite >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups "Jenkins Developers" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an email to [email protected]. >> > To view this discussion on the web visit https://groups.google.com/d/ms >> gid/jenkinsci-dev/4610855b-20e9-42fb-8e8b-d06c3808f78a%40googlegroups.com. >> >> > For more options, visit https://groups.google.com/d/optout. >> >> -- > You received this message because you are subscribed to the Google Groups > "Jenkins Developers" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/jenkinsci-dev/a4aadc1f-b1d6-44a2-8c64-bf86369f84b5% > 40googlegroups.com > <https://groups.google.com/d/msgid/jenkinsci-dev/a4aadc1f-b1d6-44a2-8c64-bf86369f84b5%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- Robert Sandell *Software Engineer* *CloudBees Inc.* -- You received this message because you are subscribed to the Google Groups "Jenkins Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CALzHZS2BpjOg9kxcDZpTcA06WW55OmR8nnDtOkHsVu93mwMG5g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
