Ok thanks ! I guess I will use a classic job instead so that I can use the REST API.
On Wed, May 28, 2014 at 6:33 PM, James Nord (jnord) <jn...@cisco.com> wrote: > You can’t automate a release via the m2release plugin via a REST like > API. > > You can do it using HTTP Post and curl – just have a look at the form > befor you do a release and you should be able to craft a cURL request. > > > > e.g. > > releaseVersion=1.2.3 > > developmentVersion=1.2.4-SNAPSHOT > > > > if you’re not sure of the data you need to supply – a wireshark capture of > a test release is your friend. > > > > /James > > > > *From:* jenkinsci-users@googlegroups.com [mailto: > jenkinsci-users@googlegroups.com] *On Behalf Of *Emmanuel POT > *Sent:* 28 May 2014 17:03 > *To:* jenkinsci-users@googlegroups.com > *Cc:* m...@batmat.net > *Subject:* Re: Call Perform Maven Release through REST API > > > > Hello, > > > > Sorry I will try to be more specific. I want to use the Jenkins plugin Maven > Release <https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin>. > It takes care of committing the correct version in the pom.xml before the > release, with the possibility to tune the commit message... > > > > I create a new Maven job, and activate the plugin for it. In the UI, it > adds a new button on the left panel at job level "Perform Maven Release" > that opens a new form in which I can precise a few things including the > version. It is not a build parameter of the job that I could pass by > calling the "classic" REST API. I wonder if this specific plugin can be > called via the API, and if it is the case, how ? > > > > Maybe the answer is not to use the Maven job configuration and the plugin > above, and simply define shell steps with build parameters in a free-style > project. > > > > Cheers, > > Emmanuel > > On Wednesday, 28 May 2014 17:55:45 UTC+2, Baptiste Mathus wrote: > > Well, you certainly want too give a wee bit more precision. > > Trying to approximately answer your question though, one way to do it > could be: > 1) define a Jenkins job, and configure it so that the release works fine > (define a parameter for that build) > 2) through either jenkins-cli or the rest api, trigger the release build > remotely, passing the required parameter you speak about. > > Cheers > > Le 28 mai 2014 09:31, "Emmanuel POT" <emmanu...@gmail.com> a écrit : > > Hello, > > > > I would like to perform a maven release using the maven release plugin > remotely. Ideally, I would be able to pass as http parameters the version > to use. > > > > I googled for 30min but could not find a way to do that. Has anyone > managed to do it ? > > > > Cheers, > > emmanuel > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-use...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Jenkins Users" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to jenkinsci-users+unsubscr...@googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "Jenkins Users" group. > To unsubscribe from this topic, visit > https://groups.google.com/d/topic/jenkinsci-users/EskpKpyEv_8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > jenkinsci-users+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Jenkins Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
