Just thought I could share this not-so-new info,
in case anybody struggles with this like I just did..:
1. assuming you're using a version of git around 1.8.5.2 (the one I use)
2. I use maven 3.1.1, but that is just FYI
3. you'll need to force maven-release-plugin 2.5, as per later below
4. (otherwise your release will fail committing the non-SNAPSHOT)
5. make sure your git origin is your actual plugin repo to release (
jenkinsci/pluginToRelease)
6. if your jenkins-ci and github accounts' credentials differ, have this
in your maven settings.xml:
<servers>
<server>
<id>maven.jenkins-ci.org</id>
<username>yourJenkinsCIuser</username>
<password>yourJenkinsCIpwd</password>
</server>
</servers>
7. cd to your plugin git repo to release
8. mvn org.apache.maven.plugins:maven-release-plugin:2.5:prepare
9. then, if all looks fairly ok,
10. mvn org.apache.maven.plugins:maven-release-plugin:2.5:perform
11. (you can combine the above commands into one, say, next time you
release..)
12. I had to also do a git push, even though that looked more like a
no-op (but then git status disagreed)
13. so, the above allowed me to make release 1.9
of github.com/jenkinsci/description-setter-plugin (e.g.)
14. references I used to "come up with" the above:
1. groups.google.com/forum/#!topic/jenkinsci-dev/qkmbl3HrYgk
2.
jenkins-ci.361315.n4.nabble.com/Unable-to-deploy-plugin-to-repo-tc3093159.html#a3093270
3.
wiki.jenkins-ci.org/display/JENKINS/Hosting+Plugins#HostingPlugins-PreparePOMforrelease
-The last ref above (3.) is of particular importance; you need to follow
it..
/Marco
--
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-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
