Failing on first trial to release plugin to jenkins-ci.org

26 views
Skip to first unread message

Moshe Cohen

unread,
Jun 18, 2016, 7:37:44 PM6/18/16
to Jenkins Developers
Hi,

I have created a plugin (that works locally) and I am following https://wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins in order to have it hosted.
Today it was forked and I reached the command "mvn release:prepare release:perform -Dusername=... -Dpassword=..." .

Unfortunately, this fails and I have no clue how to continue.
The first error line is   "    [ERROR] Failed to execute goal org.codehaus.mojo:findbugs-maven-plugin:3.0.3:check (findbugs) on project aqua-security-scanner: failed with 1 bugs and 0 errors -> [Help 1]"

Attached are the full output of the above command and also my pom.xml file .

Thank you

output.txt
pom.xml

Baptiste Mathus

unread,
Jun 19, 2016, 2:04:18 AM6/19/16
to Jenkins Developers

Hi,

FindBugs issue unrelated to release.

Use mvn clean verify locally to reproduce outside the context of a release.
Reading the logs, switch missing the default case.

Cheers

--
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/4497d2b2-ed6a-43f1-a505-66ab49bb1f1d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Moshe Cohen

unread,
Jun 19, 2016, 8:11:43 AM6/19/16
to Jenkins Developers, m...@batmat.net
Oops.  Thank you, I was confused by many iterations that I didn't see the error I sent was actually an obvious one.

I have cleaned that up but I still fail due to something that seems like a Git authentication issue.
Please see bottom of attached output1.txt or output2.txt .


Another issue, though probably not related is that in output1.txt there are ERRORs with stack traces towards the top.
Just running the mvn command again, after release.properties and pom.xml.releaseBackup have been created, produces output2.txt where these errors do not appear.

I am very grateful for your assistance.
Thank you
output2.txt
output1.txt

Baptiste Mathus

unread,
Jun 19, 2016, 8:32:04 AM6/19/16
to Jenkins Developers
I think you shouldn't pass the -Dusername & password to the command.

I suspect the git maven api tries to use user:password@url format, when you're actually using the ssh protocol. And as it's not prefixed with the protocol in your case, I guess maven things it's http[s] and fails.

I for one never put anything else than release:prepare release:perform and it works fine (and I released a new version only a few days ago).

My 2 cents

Moshe Cohen

unread,
Jun 19, 2016, 9:10:56 AM6/19/16
to jenkin...@googlegroups.com
I had to create the settings.xml file and then it worked, finnaly.
Thank you.

Do you know why those ERRORS with stack traces appear the first time, although it still succeeds ?





Baptiste Mathus

unread,
Jun 19, 2016, 9:36:02 AM6/19/16
to Jenkins Developers
Depends what you are talking about. I've got not ERRORS nor stacktraces during my releases IIRC.

Moshe Cohen

unread,
Jun 19, 2016, 9:40:17 AM6/19/16
to jenkin...@googlegroups.com
I was referring to the ones that appear in the output1.txt file that I attached previously. Attached here again.

output1.txt

Robert Sandell

unread,
Jun 20, 2016, 5:52:55 AM6/20/16
to jenkin...@googlegroups.com
It seems like it couldn't find the hpi plugin and it was only looking in the maven central repo, not in repo.jenkins-ci.org.
IIUC you didn't have a settings.xml before and therefore no settings to tell maven to go look for maven plugins in the jenkins repo.
But since the plugin was cached in your local repo the build could continue.

/B


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



--
Robert Sandell
Software Engineer
CloudBees Inc.

Moshe Cohen

unread,
Jun 20, 2016, 6:01:25 AM6/20/16
to jenkin...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages