Looking for a Build Team perspective

[Ashwin E <as...@ge.com>]

I'm not looking from a developer's perspective,i'm looking from a build team
perspective...Dev teanm continously submits new/updated files and I need to
deploy it into the application.....I've identified the process that i can
implement using Maven-Continnum...I'll list the process...correct me or add
your inputs to it..

1.Dev checks in files into CVS
2.Maven runs :deploy goal, and deploys into the remote location
3.Now that the new/updated files have been deployed.How do I restart the
server?So that the changes can be reflected?

Is the process correct?
-- 
View this message in context: http://www.nabble.com/Looking-for-a-Build-Team-perspective-tf3808306s177.html#a10778280
Sent from the Maven - Users mailing list archive at Nabble.com.


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

Re: Looking for a Build Team perspective

[Jerome Lacoste <je...@gmail.com>]

On 5/24/07, Ashwin E <as...@ge.com> wrote:
>
> I'm not looking from a developer's perspective,i'm looking from a build team
> perspective...Dev teanm continously submits new/updated files and I need to
> deploy it into the application.....I've identified the process that i can
> implement using Maven-Continnum...I'll list the process...correct me or add
> your inputs to it..
>
> 1.Dev checks in files into CVS
> 2.Maven runs :deploy goal, and deploys into the remote location
> 3.Now that the new/updated files have been deployed.How do I restart the
> server?So that the changes can be reflected?
>
> Is the process correct?


1. dev checks new files into CVS

2. your CI server monitors CVS and triggers a build when a change
happens. It notifies the users of the build results. Build encompasses
running some tests, usually the unit tests and maybe some or all of
your integration tests. You can decide there to deploy the snapshots
into your corporate snapshot repository and make them available to all
your developers (this could happen upon change, or at a specific time.
E.g. daily, or every hour. Whatever suits you best).

3. periodically you run a full integration test build. This is usually
slower and thus happens less often than the simple build. The
integration test build will typically use your latest snapshots, start
the target server, run the integration tests and stop the integration
test server.

now if you want to deploy your latest application onto a live server,
it depends if this is going to be a test or production server. With a
production server, you probably want to be able to rollback if you
have a problem. See
http://www.martinfowler.com/articles/continuousIntegration.html#AutomateDeployment
You can look into capistrano from rails, it should give you some ideas
as well. http://manuals.rubyonrails.com/read/book/17

Now how to trigger this automatic deployment? You can make this
operation part of any of these CI triggered builds or you can decide
to make it manual only. Hint:automated is good. This is usually done
periodically but depends on your usage of the target server (you don't
want to necessary redeploy while people are using the server for
tests). So you could make this part of your integration build, e.g. at
the end of it.

If you need to restart the server (either as part of your integration
tests or as part of your deployment onto your test/production server),
cargo may be an option (http://cargo.codehaus.org/).

Also look into the Book JUnit in Action (Manning, V.Massol)
(http://www.manning.com/massol/)

Cheers,

Jerome

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