I've missed the "Use custom workspace" option under the maven advanced configuration - I can use this to set up a "remedy" job for the real job, which operates on the workspace of the real job.
On Tue, Feb 5, 2013 at 8:25 AM, Ilko Iliev <[email protected]> wrote: > Thanks for the info. > > Wipe out the workspace will leave the versions as changed during the > prepare stage. IMHO this feature will be very helpful to revert to a stable > stage w/out too much extra "magic". It's true that the tag must be removed > manually, if it has been created, but in our case this could be done direct > from the IDE. On opposite, the build infrastructure is not in our > (developers) full control and it is not so trivial to execute rollback from > the shell because of the file permissions. > > On 04.02.2013, at 18:39, Eric Pyle <[email protected]> wrote: > > I've seen release:rollback implemented as a Batch Task in a Maven build > job. This was at my previous employer so I don't have access to the job > anymore to give the details, but I think it is pretty straightforward. This > way you can keep the rollback function together with the regular build job > with no funny business about the SCM. > > It's true that if Maven has created tags, they won't be automatically > deleted, but you can do that manually if needed. You may want to run maven > release -DdryRun=true first to make sure there are no Maven errors before > running the real build. DryRun won't commit any changes to source control. > > Regards, > Eric > > On 2/4/2013 12:28 PM, teilo wrote: > > Hi, > > It’s not supported (which is why the RFE is still open) and comments in > the wiki are not monitored by the plugin maintainer. > > "Wipe out workspace" is probably the best form or release:rollback J > maven won’t delete the tag if it created it anyway - so depending on > what failed you may well need to do something by hand anyway. > > Regards, > > /James > > On Monday, 4 February 2013 16:58:34 UTC, Ilko wrote: >> >> Hi, >> >> I came accross the request for release:rollback on failed release[1], >> however it is still marked as opened. From the wiki of the plugin[2] I >> can't figure out, if this feature is implemented or not and the RFE is one >> and half year old. Can someone give me an info? Or is there some other way >> to perform release:rollback after failed release? My very ugly solution was >> to set the SCM to "None", run Pre-Build step with -B release:rollback goal >> and then dummy clean Build step, but as you can see this can only work with >> test jobs, because all config must be cleared :-( >> >> TIA >> >> [1] https://issues.jenkins-ci.org/browse/JENKINS-8263 >> [2] https://wiki.jenkins-ci.org/display/JENKINS/M2+Release+Plugin >> > -- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > > > > -- 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
