maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Nathan Coast <nathan.co...@db.com>
Subject Re: chaining release:prepare release:perform for multi-module [I]
Date Fri, 19 Jul 2013 15:11:57 GMT
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 <ziga.gregoric@gmail.com>
To:
Maven Users List <users@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 <nathan.coast@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







---

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


Mime
View raw message