Thanks for the pointer Baptiste. My new plugin does not even have a yml file present in https://github.com/jenkins-infra/repository-permissions-updater/ <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater%2F&sa=D&sntz=1&usg=AFQjCNFcWVq8KHaUItF9eFurQcXeiQVuGw> . I hadn't created a new plugin since this was put into place and missed the prior announcements regarding it.
I'll file a PR to *create* the file, with myself added to the account, and go from there. thanks again On Saturday, October 1, 2016 at 11:54:28 AM UTC-4, Baptiste Mathus wrote: > > Hi Gabe, > Seems not exactly the same. > > Check you're in > https://github.com/jenkins-infra/repository-permissions-updater/ > <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fjenkins-infra%2Frepository-permissions-updater%2F&sa=D&sntz=1&usg=AFQjCNFcWVq8KHaUItF9eFurQcXeiQVuGw> > > as you should. If not file a PR to add your account to allow yourself. > > (Beware, it's your Jenkins ID, not GitHub) > > Le 1 oct. 2016 4:59 PM, "Gabe Montero" <[email protected] <javascript:>> > a écrit : > >> I'm trying to publish a new plugin (vs. the existing plugin I ultimately >> got working with everyone's help back in August), and this time I got the >> same error Mark posted back in August (though on my plugin file vs. the >> metadata.xml file): >> >> [INFO] [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on >> project openshift-login: Failed to deploy artifacts: Could not transfer >> artifact org.openshift.jenkins:openshift-login:hpi:0.1 from/to >> maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases): Access >> denied to: >> https://repo.jenkins-ci.org/releases/org/openshift/jenkins/openshift-login/0.1/openshift-login-0.1.hpi, >> >> ReasonPhrase: Forbidden. -> [Help 1] >> >> Any chance that updating the whitelist like Daniel did back in August be >> necessary / help here? >> >> thanks >> >> On Thursday, August 25, 2016 at 12:29:23 PM UTC-4, Gabe Montero wrote: >>> >>> 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]> >>>> 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] <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/jenkinsci-dev/389fd949-8c09-4c7a-a058-2ea673e35282%40googlegroups.com >> >> <https://groups.google.com/d/msgid/jenkinsci-dev/389fd949-8c09-4c7a-a058-2ea673e35282%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> 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/ffd89f5f-dfa1-4d35-b792-2162d8dff565%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
