continuum-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Johnson, Jonathan" <jjohn...@454.com>
Subject RE: Why Continuum?
Date Wed, 22 Feb 2006 15:24:13 GMT
Continuum checks for changes and builds on a time based schedule.  An
alternate (and better) approach would be to build after changes have
been applied.  Continuous integration tools have the ability to listen
or get notified by the SCM system when changes have been made.  You can
configure the build to launch shortly after changes have been made to
the codebase.  The intelligence behind the feature launches a build
after changes have been made but wait long enough to ensure it does not
launch a build while more changes are being committed.  A common problem
with timed builds is if team mebers are in the middle of committing
changes the build may fail.

The Continuum team is planning this feature:

http://maven.apache.org/continuum/planned-features.html



-----Original Message-----
From: Torsten Curdt [mailto:tcurdt@apache.org] 
Sent: Tuesday, February 21, 2006 6:49 PM
To: continuum-users@maven.apache.org
Subject: Re: Why Continuum?


On 22.02.2006, at 08:34, Johnson, Jonathan wrote:

> For instance Continuum does not have the feature yet to invoke
> builds based on SCM changes.

Huh? ...it queries the SCM periodically to check for changes.
If there are changes it kicks off a build.

cheers
--
Torsten


LEGAL NOTICE:
Unless expressly stated otherwise, this message is confidential and may be privileged. It
is intended for the addressee(s) only. Access to this e-mail by anyone else is unauthorized.
If you are not an addressee, any disclosure or copying of the contents or any action taken
(or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee,
please inform the sender immediately.



Mime
View raw message