You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@continuum.apache.org by Ba...@fastmobile.com on 2006/07/21 18:07:40 UTC
Release strategy with Continuum
I was wondering if anyone has developed any best practices for performing a release with maven when using continuum? To cut things down to the basics, seems you pretty much have to:
1. Stop continuum
2. Perform the release (including deployment of jars to repository)
3. Restart continuum
Is this pretty much what everyone else is doing, or have other people found better ways of managing releases in a continuous integration environment.
Thanks,
Baron
RE: Deploying the application after the build
Posted by Vincent Massol <vi...@massol.net>.
Hi Adam,
> -----Original Message-----
> From: Adam [mailto:punkinshred@gmail.com]
> Sent: samedi 22 juillet 2006 07:16
> To: continuum-users@maven.apache.org
> Subject: Re: Deploying the application after the build
>
> We tried this with Cargo but, ran into some problems with the way it
> was starting the Tomcat server during the build and not allowing a
> Continuum build to finish because the server was running in the build.
> We eventually wrote a Maven Plugin that did this for us. I think
> there is a maven:tomcat plugin (in the sandbox still?) that is worth
> looking into.
FWIW we run Cargo in CI builds with no problem...
Could you please provide more details about the issues you ran into when
starting the Tomcat server with Cargo (what would be even better would be if
you could post them to the cargo list as feedback)? Seen the number of users
of Cargo I don't see there's any hard problem that cannot be overcome and
we're happy to work with you on solving it. I checked and didn't see any
email from you on the Cargo list. Feel free to post there as this is where
you can get support.
Thanks
-Vincent
> On 7/21/06, Wayne Fay <wa...@gmail.com> wrote:
> > Sounds like a job for the Cargo M2 plugin:
> > http://cargo.codehaus.org/
> >
> > Wayne
> >
> > On 7/21/06, Prashanth Krishnamurthy <pk...@yahoo.com> wrote:
> > > Once the build is done, I want the application (.war
> > > file ) to be deployed on a server running on different
> > > machine. How do I do this? Please help.
> > >
> > > thanks
> > > --Prashanth
> > >
> > > __________________________________________________
> > > Do You Yahoo!?
> > > Tired of spam? Yahoo! Mail has the best spam protection around
> > > http://mail.yahoo.com
> > >
> >
>
>
> --
> Adam Altemus
> punkinshred@gmail.com
___________________________________________________________________________
D�couvrez un nouveau moyen de poser toutes vos questions quelque soit le sujet !
Yahoo! Questions/R�ponses pour partager vos connaissances, vos opinions et vos exp�riences.
http://fr.answers.yahoo.com
Re: Deploying the application after the build
Posted by Adam <pu...@gmail.com>.
We tried this with Cargo but, ran into some problems with the way it
was starting the Tomcat server during the build and not allowing a
Continuum build to finish because the server was running in the build.
We eventually wrote a Maven Plugin that did this for us. I think
there is a maven:tomcat plugin (in the sandbox still?) that is worth
looking into.
On 7/21/06, Wayne Fay <wa...@gmail.com> wrote:
> Sounds like a job for the Cargo M2 plugin:
> http://cargo.codehaus.org/
>
> Wayne
>
> On 7/21/06, Prashanth Krishnamurthy <pk...@yahoo.com> wrote:
> > Once the build is done, I want the application (.war
> > file ) to be deployed on a server running on different
> > machine. How do I do this? Please help.
> >
> > thanks
> > --Prashanth
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Tired of spam? Yahoo! Mail has the best spam protection around
> > http://mail.yahoo.com
> >
>
--
Adam Altemus
punkinshred@gmail.com
Re: Deploying the application after the build
Posted by Wayne Fay <wa...@gmail.com>.
Sounds like a job for the Cargo M2 plugin:
http://cargo.codehaus.org/
Wayne
On 7/21/06, Prashanth Krishnamurthy <pk...@yahoo.com> wrote:
> Once the build is done, I want the application (.war
> file ) to be deployed on a server running on different
> machine. How do I do this? Please help.
>
> thanks
> --Prashanth
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
RE: Release strategy with Continuum
Posted by Ba...@fastmobile.com.
Thanks for the feedback. Definitely good to know others are in the same boat, and I definitely never would've thought of the scm bootstrapping solution.
Thanks,
Baron
-----Original Message-----
From: dan tran [mailto:dantran@gmail.com]
Sent: Fri 7/21/2006 8:49 PM
To: continuum-users@maven.apache.org
Subject: Re: Release strategy with Continuum
and if http://jira.codehaus.org/browse/MRELEASE-100 implemented
than all you need is
mvn release:release
-D
On 7/21/06, Wayne Fay <wa...@gmail.com> wrote:
>
> We build official releases "manually". But Dan's suggestion seems
> reasonable.
>
> Wayne
>
> On 7/21/06, dan tran <da...@gmail.com> wrote:
> > you can add a build defintion to you current project that do this.
> >
> > mvn scm:bootstrap -Dgoals="-B,release:prepare,release:perform"
> >
> > schedule it to somewhere in far future and run it ( one click) later
> >
> >
> > never try it thou ;-)
> >
> > -D
> >
> >
> > On 7/21/06, Baron.Reznik@fastmobile.com <Ba...@fastmobile.com>
> wrote:
> > >
> > > I was wondering if anyone has developed any best practices for
> performing
> > > a release with maven when using continuum? To cut things down to the
> basics,
> > > seems you pretty much have to:
> > >
> > > 1. Stop continuum
> > > 2. Perform the release (including deployment of jars to repository)
> > > 3. Restart continuum
> > >
> > > Is this pretty much what everyone else is doing, or have other people
> > > found better ways of managing releases in a continuous integration
> > > environment.
> > >
> > > Thanks,
> > > Baron
> > >
> >
> >
>
Re: Release strategy with Continuum
Posted by dan tran <da...@gmail.com>.
and if http://jira.codehaus.org/browse/MRELEASE-100 implemented
than all you need is
mvn release:release
-D
On 7/21/06, Wayne Fay <wa...@gmail.com> wrote:
>
> We build official releases "manually". But Dan's suggestion seems
> reasonable.
>
> Wayne
>
> On 7/21/06, dan tran <da...@gmail.com> wrote:
> > you can add a build defintion to you current project that do this.
> >
> > mvn scm:bootstrap -Dgoals="-B,release:prepare,release:perform"
> >
> > schedule it to somewhere in far future and run it ( one click) later
> >
> >
> > never try it thou ;-)
> >
> > -D
> >
> >
> > On 7/21/06, Baron.Reznik@fastmobile.com <Ba...@fastmobile.com>
> wrote:
> > >
> > > I was wondering if anyone has developed any best practices for
> performing
> > > a release with maven when using continuum? To cut things down to the
> basics,
> > > seems you pretty much have to:
> > >
> > > 1. Stop continuum
> > > 2. Perform the release (including deployment of jars to repository)
> > > 3. Restart continuum
> > >
> > > Is this pretty much what everyone else is doing, or have other people
> > > found better ways of managing releases in a continuous integration
> > > environment.
> > >
> > > Thanks,
> > > Baron
> > >
> >
> >
>
RE: Deploying the application after the build
Posted by "Bravo, Kris" <kr...@cingular.com>.
Use plugin which corresponds to your server of choice, or check out
cargo (not sure how far along this is). Mojo has some weblogic, jboss
and tomcat plugins.
Do me a favor and feed back whether or not you successfully remote
deploy. I'm curious about the status of this type of action.
kris bravo
-----Original Message-----
From: Prashanth Krishnamurthy [mailto:pkrishna25@yahoo.com]
Sent: Friday, July 21, 2006 3:24 PM
To: continuum-users@maven.apache.org
Subject: Deploying the application after the build
Once the build is done, I want the application (.war file ) to be
deployed on a server running on different machine. How do I do this?
Please help.
thanks
--Prashanth
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Deploying the application after the build
Posted by Prashanth Krishnamurthy <pk...@yahoo.com>.
Once the build is done, I want the application (.war
file ) to be deployed on a server running on different
machine. How do I do this? Please help.
thanks
--Prashanth
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
Re: Release strategy with Continuum
Posted by Wayne Fay <wa...@gmail.com>.
We build official releases "manually". But Dan's suggestion seems reasonable.
Wayne
On 7/21/06, dan tran <da...@gmail.com> wrote:
> you can add a build defintion to you current project that do this.
>
> mvn scm:bootstrap -Dgoals="-B,release:prepare,release:perform"
>
> schedule it to somewhere in far future and run it ( one click) later
>
>
> never try it thou ;-)
>
> -D
>
>
> On 7/21/06, Baron.Reznik@fastmobile.com <Ba...@fastmobile.com> wrote:
> >
> > I was wondering if anyone has developed any best practices for performing
> > a release with maven when using continuum? To cut things down to the basics,
> > seems you pretty much have to:
> >
> > 1. Stop continuum
> > 2. Perform the release (including deployment of jars to repository)
> > 3. Restart continuum
> >
> > Is this pretty much what everyone else is doing, or have other people
> > found better ways of managing releases in a continuous integration
> > environment.
> >
> > Thanks,
> > Baron
> >
>
>
Re: Release strategy with Continuum
Posted by dan tran <da...@gmail.com>.
you can add a build defintion to you current project that do this.
mvn scm:bootstrap -Dgoals="-B,release:prepare,release:perform"
schedule it to somewhere in far future and run it ( one click) later
never try it thou ;-)
-D
On 7/21/06, Baron.Reznik@fastmobile.com <Ba...@fastmobile.com> wrote:
>
> I was wondering if anyone has developed any best practices for performing
> a release with maven when using continuum? To cut things down to the basics,
> seems you pretty much have to:
>
> 1. Stop continuum
> 2. Perform the release (including deployment of jars to repository)
> 3. Restart continuum
>
> Is this pretty much what everyone else is doing, or have other people
> found better ways of managing releases in a continuous integration
> environment.
>
> Thanks,
> Baron
>