Getting a 401 when trying to upload my plugin to Artifactory

[Adam Chevalier]

Hi, I'm trying to deploy my plugin (testrail-plugin) to the Jenkins Artifactory and keep getting 401s.

I get the following error

http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

[INFO] ------------------------------------------------------------------------

[INFO] BUILD FAILURE

[INFO] ------------------------------------------------------------------------

[INFO] Total time: 01:18 min

[INFO] Finished at: 2017-04-16T08:46:35-05:00

[INFO] Final Memory: 67M/372M

[INFO] ------------------------------------------------------------------------

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project testrail: Failed to deploy artifacts: Could not transfer artifact org.jenkinsci.plugins:testrail:hpi:1.0.5 from/to maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): Failed to transfer file: https://repo.jenkins-ci.org/releases/org/jenkinsci/plugins/testrail/1.0.5/testrail-1.0.5.hpi. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]

[ERROR] 

[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.

[ERROR] Re-run Maven using the -X switch to enable full debug logging.

[ERROR] 

[ERROR] For more information about the errors and possible solutions, please read the following articles:

[ERROR] [Help 1]http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

I've tried everything suggested in the wiki to resolve this issue. I made sure my permissions are setup correctly in the repository-permissions-updater (and my PR was approved). I've triple checked that my ssh keys are correctly setup and my git credentials are all correct. I'm at a loss at this point.

I would appreciate any help you could render. If required, I can produce my effective-pom

[Mark Waite]

I think that is not the correct destination for Jenkins artifacts.  Double check the destination, or check other plugins for their destinations.

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 jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/bd845af9-c71f-443f-afd6-a396af94afa7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Daniel Beck]

> On 16.04.2017, at 22:34, Adam Chevalier <chevali...@gmail.com> wrote:
>
> I can produce my effective-pom

Please do, and also provide the Maven settings.xml (with passwords removed).

[Adam Chevalier]

I've attached my effective pom and maven settings with passwords removed.

Mark, I'll compare my destination with other plugins, thanks for the suggestion.

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/7Bmo4frIlYs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-dev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/2359DCDD-9331-45AE-BFAA-3CB9711B46D4%40beckweb.net.

[Adam Chevalier]

My pom had not distribution node, this is probably the issue. I'll test it quick and let you know.

[Adam Chevalier]

I added a distributionManagement node (copied the one found in the accurev plugin) and tried from there. Maven seemed to do more things than before, but ultimately came to the same 401 error.

My new effective pom is attached.

[Adam Chevalier]

It's been a couple weeks so I thought I would check in. I'm still unable to finish the maven release: perform step.