I believe I sorted it out. I needed <server> entries for both maven.jenkins-ci.org and repo.jenkins-ci.org in my ~/.m2/settings.xml. With that, `mvn release:prepare release:perform" completed successfully for me, at least on my local host side.
Assuming the "upstream side mechanics" that result in the new plugin version showing up at https://updates.jenkins-ci.org/download/plugins, I should be good to go. Thanks to everyone for the quick responses. On Thursday, August 25, 2016 at 12:08:09 PM UTC-4, Jesse Glick wrote: > > On Thu, Aug 25, 2016 at 11:31 AM, Gabe Montero <[email protected] > <javascript:>> wrote: > > Failed to > > transfer file: > > > https://repo.jenkins-ci.org/releases/com/openshift/jenkins/openshift-pipeline/1.0.22/openshift-pipeline-1.0.22.hpi. > > > > Return code is: 401, ReasonPhrase: Unauthorized. > > @Daniel, maybe an artifact permission issue? > -- 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/29d8740d-5a10-4e21-9119-8dd2507319d2%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
