Baz wrote:
All,
What is the best practice for handling build outputs, reports and
archives? Here are the brief environments:
1. Build scheduling systerm such as CruiseControl.
2. Maven 2.0.
3. #1 and #2 running nightly, continuous and ad-hoc builds.
Outputs:
1. Build tree.
2. Build outputs.
3. Junit outputs.
4. Code coverage outputs.
Where should they go so that they can be easily access? Is there any
general practice with M2?
For example, I am thinking of running the followings:
1. "mvn test" to compile and test.
2. "mvn site" to generate html pages (I believe "mvn site" only create
reports, html and statistics but not the build output/binaries)
3. Archive both #1 and #2 into some share directories arranged by
directory structure such as
\\<server_name>\<root_dir>\<project>\<version>\<date/id>. This
structure will be pointed by a webserver for users to access.
Comments?
Why not use Continuum [1]?
Continuum is designed to build Maven-projects.. If you modify the
site-configuration a bit Continuum should do what you want pretty much
out of the box if you can set up apache to serve the generated output.
btw, continuum-1.1-alpha is on its way. It has a lot of additional
features compared with 1.0.3.
[1] http://maven.apache.org/continuum/
--
Erik Drolshammer
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
