Release WhiteSource plugin

34 views
Skip to first unread message

anna....@whitesourcesoftware.com

unread,
Jun 21, 2016, 4:12:56 AM6/21/16
to Jenkins Developers
Hi, 
I've tried to go over INFRA-588 issue and upgrade my parent pom to 2.8 ,but I'm still getting this error while trying to upload my plugin
Please advice

   [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 26.905s
    [INFO] Finished at: Mon Jun 20 14:04:56 UTC 2016
    [INFO] Final Memory: 56M/404M
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.8.2:deploy (default-deploy) on project whitesource: Failed to deploy artifacts: Could not transfer artifact org.jenkins-ci.plugins:whitesource:hpi:1.7.2 from/to maven.jenkins-ci.org (https://repo.jenkins-ci.org/releases/): Failed to transfer file: https://repo.jenkins-ci.org/releases/org/jenkins-ci/plugins/whitesource/1.7.2/whitesource-1.7.2.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
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1:01.100s
[INFO] Finished at: Mon Jun 20 14:04:57 UTC 2016
[INFO] Final Memory: 28M/350M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-release-plugin:2.5.3:perform (default-cli) on project whitesource: Maven execution failed, exit code: '1' -> [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:


Thanks,
Anna

Joachim Kuhnert

unread,
Jun 21, 2016, 4:55:34 AM6/21/16
to jenkin...@googlegroups.com

Hello,

 

I have no experiences with the new pom but for the old one it always worked for me to set username and password in the .m2/settings.xml and not using –Dpassword= and –Dusername=…

I could not find if you use these variables but perhaps this helps.

 

Best Regards,

Joachim

---------------------------------------------------

Joachim Kuhnert

fon: +49 30 394 09 683 39

 

PikeTec GmbH, Waldenserstr. 2-4, 10551 Berlin

Management: Eckard Bringmann, Andreas Krämer, Jens Lüdemann

Location of the company: Berlin (Germany)

Trade register: Amtsgericht Berlin HRB 105491 B

Website: www.piketec.com

--
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/38551b3f-cecc-4b07-a9b2-4cc7afd33927%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

anna....@whitesourcesoftware.com

unread,
Jun 21, 2016, 5:48:22 AM6/21/16
to Jenkins Developers, Joachim...@piketec.com
Hi, 
Thanks for the answer.
I'm not using –Dpassword= and –Dusername=… 

Baptiste Mathus

unread,
Jun 21, 2016, 8:44:31 AM6/21/16
to Jenkins Developers
I guess (some day, I'll have to test all that to enrich the FAQ) you should be using the ssh protocol in https://github.com/jenkinsci/whitesource-plugin/blob/master/pom.xml#L42 instead of https.
I have in mind to write a Docker image to help with that (releasing).

So, I suspect your issue is now unrelated to INFRA-588.
I'd guess (again) that passing the -Dusername to the CLI might actually be useful in that https very case.

Reply all
Reply to author
Forward
0 new messages