You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@maven.apache.org by Nathan Coast <na...@db.com> on 2013/07/18 17:23:17 UTC

chaining release:prepare release:perform for multi-module [I]

Classification: For internal use only

Hi all,

I appreciate the "normal" approach to executing a maven release is to 
execute release:prepare, followed by release:perform

I am attempting to set up a release job within our build server (TeamCity) 
which will atomically create a release.  Assuming successful execution.

mvn release:prepare release:perform

My concern is that this will execute prepare followed by perform upon each 
module in the reactor build order.  Where what is needed is for 
release:prepare to be executed in full, followed by release perform in 
full.

Is there any way to configure this in a single chained command?  Or will I 
have to configure multiple build jobs and link the jobs?

Regards,
Nathan




---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

RE: chaining release:prepare release:perform for multi-module [I]

Posted by Martin Gainty <mg...@hotmail.com>.

 
you can specify which goals to execute before the release to quote 
 
<goals>"A space separated list of goals to execute on deployment. Default value is either deploy or deploy site-deploy, if the project has a< distributionManagement>/<site> element.
User property is: goals.
</goals>

http://maven.apache.org/maven-release/maven-release-plugin/perform-mojo.html

Martin Gainty 
______________________________________________ 
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité

Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.

Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.

 
> To: users@maven.apache.org
> Subject: chaining release:prepare release:perform for multi-module [I]
> From: nathan.coast@db.com
> Date: Thu, 18 Jul 2013 16:23:17 +0100
> 
> Classification: For internal use only
> 
> Hi all,
> 
> I appreciate the "normal" approach to executing a maven release is to 
> execute release:prepare, followed by release:perform
> 
> I am attempting to set up a release job within our build server (TeamCity) 
> which will atomically create a release.  Assuming successful execution.
> 
> mvn release:prepare release:perform
> 
> My concern is that this will execute prepare followed by perform upon each 
> module in the reactor build order.  Where what is needed is for 
> release:prepare to be executed in full, followed by release perform in 
> full.
> 
> Is there any way to configure this in a single chained command?  Or will I 
> have to configure multiple build jobs and link the jobs?
> 
> Regards,
> Nathan
> 
> 
> 
> 
> ---
> 
> This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
> 
> Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

Re: chaining release:prepare release:perform for multi-module [I]

Posted by Ziga Gregoric <zi...@gmail.com>.

Hi Nathan,

Never used svn-settings, can't help there.
What works for me is to login with teamcity user to my build server,
run one release from command line - svn asks for credentials and saves
it (imho under ~.svnsomething, but I'm not sure). With svn credentials
saved for teamcity user, it should work for release job from teamcity
also.

Regards,
Ziga

On 19. jul. 2013, at 17:12, Nathan Coast <na...@db.com> wrote:

Classification: For internal use only

Hi Ziga,

Thanks for the pointers.

I solved the problem with a build job with two build steps -
1) release:prepare
2) release:perform

sort of obvious really. I'm now struggling with using cached SVN
credentials. I'm using this SCM provider to manage interaction with SVN
during release.

https://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/wiki/UsingWithReleasePlugin

I have configured this:
http://maven.apache.org/scm/subversion.html

with

<svn-settings>
<useAuthCache>true</useAuthCache>
</svn-settings>

However I still need to place the credentials in the settings.xml in order
for the build to succeed.

Any suggestions?
Regards,
Nathan

From:
Ziga Gregoric <zi...@gmail.com>
To:
Maven Users List <us...@maven.apache.org>,
Date:
18/07/2013 16:43
Subject:
Re: chaining release:prepare release:perform for multi-module [I]

Nathan,

Strategy working for me is to have two jobs, one doing mvn clean
install on every commit and another for release.

The release job would do mvn release:prepare release:perform
--batch-mode on my multi module project's parent pom.

With TeamCity and svn it works great, and the install job gives me a
safety net that trunk is green.

Regards,
Ziga

On 18. jul. 2013, at 17:23, Nathan Coast <na...@db.com> wrote:

Classification: For internal use only

Hi all,

I appreciate the "normal" approach to executing a maven release is to
execute release:prepare, followed by release:perform

I am attempting to set up a release job within our build server (TeamCity)
which will atomically create a release. Assuming successful execution.

mvn release:prepare release:perform

My concern is that this will execute prepare followed by perform upon each
module in the reactor build order. Where what is needed is for
release:prepare to be executed in full, followed by release perform in
full.

Is there any way to configure this in a single chained command? Or will I
have to configure multiple build jobs and link the jobs?

Regards,
Nathan

---

This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and delete this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for
additional EU corporate and regulatory disclosures.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

---

Please refer to http://www.db.com/en/content/eu_disclosures.htm for
additional EU corporate and regulatory disclosures.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: chaining release:prepare release:perform for multi-module [I]

Posted by Nathan Coast <na...@db.com>.

Classification: For internal use only

Hi Ziga,

Thanks for the pointers.

I solved the problem with a build job with two build steps -
1) release:prepare
2) release:perform

sort of obvious really. I'm now struggling with using cached SVN
credentials. I'm using this SCM provider to manage interaction with SVN
during release.

https://code.google.com/a/apache-extras.org/p/maven-scm-provider-svnjava/wiki/UsingWithReleasePlugin

I have configured this:
http://maven.apache.org/scm/subversion.html

with

<svn-settings>
<useAuthCache>true</useAuthCache>
</svn-settings>

However I still need to place the credentials in the settings.xml in order
for the build to succeed.

Any suggestions?
Regards,
Nathan

From:
Ziga Gregoric <zi...@gmail.com>
To:
Maven Users List <us...@maven.apache.org>,
Date:
18/07/2013 16:43
Subject:
Re: chaining release:prepare release:perform for multi-module [I]

Nathan,

Strategy working for me is to have two jobs, one doing mvn clean
install on every commit and another for release.

The release job would do mvn release:prepare release:perform
--batch-mode on my multi module project's parent pom.

With TeamCity and svn it works great, and the install job gives me a
safety net that trunk is green.

Regards,
Ziga

On 18. jul. 2013, at 17:23, Nathan Coast <na...@db.com> wrote:

Classification: For internal use only

Hi all,

I appreciate the "normal" approach to executing a maven release is to
execute release:prepare, followed by release:perform

I am attempting to set up a release job within our build server (TeamCity)
which will atomically create a release. Assuming successful execution.

mvn release:prepare release:perform

Is there any way to configure this in a single chained command? Or will I
have to configure multiple build jobs and link the jobs?

Regards,
Nathan

---

Please refer to http://www.db.com/en/content/eu_disclosures.htm for
additional EU corporate and regulatory disclosures.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

---

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: chaining release:prepare release:perform for multi-module [I]

Posted by Ziga Gregoric <zi...@gmail.com>.

Nathan,

Strategy working for me is to have two jobs, one doing mvn clean
install on every commit and another for release.

The release job would do mvn release:prepare release:perform
--batch-mode on my multi module project's parent pom.

With TeamCity and svn it works great, and the install job gives me a
safety net that trunk is green.

Regards,
Ziga

On 18. jul. 2013, at 17:23, Nathan Coast <na...@db.com> wrote:

Classification: For internal use only

Hi all,

I appreciate the "normal" approach to executing a maven release is to
execute release:prepare, followed by release:perform

I am attempting to set up a release job within our build server (TeamCity)
which will atomically create a release.  Assuming successful execution.

mvn release:prepare release:perform

My concern is that this will execute prepare followed by perform upon each
module in the reactor build order.  Where what is needed is for
release:prepare to be executed in full, followed by release perform in
full.

Is there any way to configure this in a single chained command?  Or will I
have to configure multiple build jobs and link the jobs?

Regards,
Nathan




---

This e-mail may contain confidential and/or privileged information. If
you are not the intended recipient (or have received this e-mail in
error) please notify the sender immediately and delete this e-mail.
Any unauthorized copying, disclosure or distribution of the material
in this e-mail is strictly forbidden.

Please refer to http://www.db.com/en/content/eu_disclosures.htm for
additional EU corporate and regulatory disclosures.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org