Problem releasing new plugin version

125 views
Skip to first unread message

antonio....@flagbit.de

unread,
May 31, 2016, 12:06:14 PM5/31/16
to Jenkins Developers
Hi Guys,

I hope someone is be able to help me or at least guide me to find the problem. I'm maintainer of the following jenkins plugin and actually trying to release a new plugin version (1.2.1). The problem is that the deploy build step is failing with the following error:

[INFO] [ERROR] Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6:deploy (default-deploy) on project bitbucket-build-status-notifier: Failed to deploy artifacts: Could not transfer artifact org.jenkins-ci.plugins:bitbucket-build-status-notifier:hpi:1.2.1 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/bitbucket-build-status-notifier/1.2.1/bitbucket-build-status-notifier-1.2.1.hpi. Return code is: 401, ReasonPhrase: Unauthorized. -> [Help 1]

I already tried all possible solutions/workarraounds proposed in this jenkins issue without success and know my crendentials are right.

Any help will be appreciated.

Thanks in advance,
Antonio

suresh kumar

unread,
May 31, 2016, 12:40:30 PM5/31/16
to Jenkins Developers
I ran into a similar problem.
If you look at: https://github.com/jenkinsci/multiple-scms-plugin/commits/master
take a look at commits 5c1e918 e87071f

antonio....@flagbit.de

unread,
Jun 1, 2016, 4:07:34 AM6/1/16
to Jenkins Developers
Hi Suresh,

thanks for your advice, I already tried using same plugin versions than you for the maven-deploy-plugin and wagon-http. I'm using maven 3.3.9 and Ubuntu 16.04, what are you using?

Thanks

Baptiste Mathus

unread,
Jun 1, 2016, 4:15:13 AM6/1/16
to Jenkins Developers
Hi,

There was a LDAP issue yesterday, so possibly you hit this at the wrong time. Did you retry since?


--
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/e9b26674-3b88-4ba4-9283-f8fd7b790c46%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

antonio....@flagbit.de

unread,
Jun 1, 2016, 4:23:56 AM6/1/16
to Jenkins Developers
Hi again Suresh,

Somehow I can't remember, seems I changed my jenkins credentials. This time was my error, updating my password fixed the problem. 

Thanks again for your time.
Antonio

suresh kumar

unread,
Jun 1, 2016, 12:56:29 PM6/1/16
to Jenkins Developers
After looking into the error message, I thought it was because of INFRA-588 issue. I almost spent very long time to identify issue and release the plugin.

-Suresh
Message has been deleted

anna....@whitesourcesoftware.com

unread,
Jun 16, 2016, 3:15:35 AM6/16/16
to Jenkins Developers
Hi ,
I tried to change my password at Jenkins but it didn't help.
I also tried to run over the solution for INFRA-588, but I'm still getting the same error:

Failed to execute goal org.apache.maven.plugins:maven-deploy-plugin:2.6: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 (http://maven.jenkins-ci.org:8081/content/repositories/releases): Failed to transfer file: http://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] 

Any ideas?
Thanks

Daniel Beck

unread,
Jun 16, 2016, 5:24:26 AM6/16/16
to jenkin...@googlegroups.com
This does not look like you applied the solutions in INFRA-588 correctly. This host name is deprecated and should not show up.

Baptiste Mathus

unread,
Jun 16, 2016, 6:01:42 AM6/16/16
to Jenkins Developers
FWIW, when you're doing `mvn deploy` (or release:perform, which does the it too), this uses the <distributionManagement> tags.

So, the recommendation is to really remove those definitions from your pom, and upgrade to the latest plugin-pom.
This way you will inherit the value from the parent pom, and using a recent one you'll be more guaranteed to have the right values (inherited, so).

To analyse/debug that issue, you want generally to see what your "effective pom" looks like.
That means, a version of the whole POM with the inheritance, imports and so all resolved in a single data structure.

To see it, simply use `mvn help:effective-pom`.

And indeed, Anna, you can see that using the command above, your last commit (changing the parent pom), fixes the <distributionManagement> tags to the right values.
(cf35d38037dfefe180c83ec2b447609d74ff08cd is wrong, ab1ee65c85701d3562a61a8b522b810f659bc158 fixes issues)

HTH

--
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.

anna....@whitesourcesoftware.com

unread,
Jun 16, 2016, 6:40:34 AM6/16/16
to Jenkins Developers, m...@batmat.net
Hi Baptiste, 
Thanks for the advice,
When building the .hpi file on my local machine everything is fine.
But when I'm running it with Jenkins I'm getting this error :

 [INFO] --- findbugs-maven-plugin:3.0.3:findbugs (findbugs) @ whitesource ---
    Jun 16, 2016 10:35:47 AM org.codehaus.groovy.runtime.m12n.MetaInfExtensionModule newModule
    WARNING: Module [groovy-all] - Unable to load extension class [org.codehaus.groovy.runtime.NioGroovyMethods]
    [INFO] Fork Value is true
         [java] Exception in thread "main" java.lang.UnsupportedClassVersionError: edu/umd/cs/findbugs/FindBugs2 : Unsupported major.minor version 51.0
         [java] 	at java.lang.ClassLoader.defineClass1(Native Method)
         [java] 	at java.lang.ClassLoader.defineClass(ClassLoader.java:643)
         [java] 	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
         [java] 	at java.net.URLClassLoader.defineClass(URLClassLoader.java:277)
         [java] 	at java.net.URLClassLoader.access$000(URLClassLoader.java:73)
         [java] 	at java.net.URLClassLoader$1.run(URLClassLoader.java:212)
         [java] 	at java.security.AccessController.doPrivileged(Native Method)
         [java] 	at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
         [java] 	at java.lang.ClassLoader.loadClass(ClassLoader.java:323)
         [java] 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
         [java] 	at java.lang.ClassLoader.loadClass(ClassLoader.java:268)
         [java] Could not find the main class: edu.umd.cs.findbugs.FindBugs2. Program will exit.
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 20.181s
    [INFO] Finished at: Thu Jun 16 10:35:48 UTC 2016
    [INFO] Final Memory: 59M/390M
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs (findbugs) on project whitesource: Execution findbugs of goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:findbugs 

Please advice
Thanks,
Anna

Daniel Beck

unread,
Jun 16, 2016, 7:39:57 AM6/16/16
to jenkin...@googlegroups.com
Use JDK 7 or newer.
> To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/144c88b7-7b48-4788-b4b0-c7c2ec1ff7be%40googlegroups.com.

Baptiste Mathus

unread,
Jun 16, 2016, 7:40:53 AM6/16/16
to Jenkins Developers
I guess you're using a JDK6 ?

If so, the recommendation is to use a JDK8 (or if you can't, at least a JDK 7).
It seems like findbugs is compiled with JDK 7 bytecode, probably.

anna....@whitesourcesoftware.com

unread,
Jun 16, 2016, 7:46:38 AM6/16/16
to Jenkins Developers, m...@batmat.net
Thanks for the advice.
I'll try it.

anna....@whitesourcesoftware.com

unread,
Jun 20, 2016, 10:28:51 AM6/20/16
to Jenkins Developers, m...@batmat.net
Hi, 
I'm still stacked.
Can anyone please help me? 
 I did all the things that written in INFRA-588 and now I'm getting this again, what's wrong?

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]


Many thanks,
Anna 
Reply all
Reply to author
Forward
0 new messages