401 unauthorized when attempting plugin release

21 views
Skip to first unread message

Philip Madden

unread,
Jun 22, 2022, 10:43:48 AM6/22/22
to Jenkins Developers
Plugin: https://github.com/jenkinsci/hashicorp-vault-pipeline-plugin
Release Tag: https://github.com/jenkinsci/hashicorp-vault-pipeline-plugin/tree/hashicorp-vault-pipeline-1.4
maven version: 3.8.4

After following the instructions here, i'm currently receiving a 401 unauthorized error when attempting to run mvn release:perform from my new machine.

I can confirm i can log into artifactory (https://repo.jenkins-ci.org) as I used this to generate my maven settings file (I have tried both encrypted and plain text passwords in my .m2/settings.xml file) but I am unable to publish artifacts.

I also have permissions in the "repository-permissions-updater" repo

Can someone please advise?

Regards

Phil M

Gavin Mogan

unread,
Jun 22, 2022, 12:17:51 PM6/22/22
to Jenkins Developers
I see you are enabling cd so I guess this is moot now but did you have the actual error message including url?

--
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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/a95b42a2-3eaa-44f7-927c-d465a1dadef4n%40googlegroups.com.

Daniel Beck

unread,
Jun 22, 2022, 12:22:37 PM6/22/22
to jenkin...@googlegroups.com
On Wed, Jun 22, 2022 at 4:43 PM Philip Madden <philma...@gmail.com> wrote:
Plugin: https://github.com/jenkinsci/hashicorp-vault-pipeline-plugin
Release Tag: https://github.com/jenkinsci/hashicorp-vault-pipeline-plugin/tree/hashicorp-vault-pipeline-1.4
maven version: 3.8.4

After following the instructions here, i'm currently receiving a 401 unauthorized error when attempting to run mvn release:perform from my new machine.

I can confirm i can log into artifactory (https://repo.jenkins-ci.org) as I used this to generate my maven settings file (I have tried both encrypted and plain text passwords in my .m2/settings.xml file) but I am unable to publish artifacts.

401 means your Maven settings are wrong, unrelated to plugin release permissions. (You can also confirm by trying to `mvn deploy` a snapshot, there's no permission requirement for that.)

Which of the strategies on the linked docs page did you use to obtain your settings.xml files? Did you try the other option to see whether the result is different?
Reply all
Reply to author
Forward
0 new messages