Hello,
you could achieve something like this in Hudson as well, if you create a
"Free Style" Hudson job that scans the build output und only triggers a
mvn deploy
when the log file contains "BUILD SUCCESS".
The initial job should not execute "mvn deploy", but rather a "mvn
package". You can concatenate the deploy job to the packaging job in
hudson and you would only
need one deploy job that is generic to all your projects.
HTH
Andreas
Yanko, Curtis schrieb:
In AHP Builds are made up of a Workflow which can contain one or more Jobs each
of which has multiple Steps. So, Our Maven Jobs tend to look like this:
Populate Workspace
Get Changelog (since last build)
Create a Stamp (and AHP construct but I use for Tags in SVN too)
Maven Builder (Effective POM & Settings)
Maven Builder (Build!)
Maven Builder (Site Generation)
Junit Publisher
Tag SVN
Publish Site Reports
Publish JAR
Assign Success
Assign Failure
Each of these steps run based on a criteria like
All Steps have passed
Previous Step Passed
Any Step Failed
Always
Never
So, for the most part job steps are set to all steps passed but JUNit publisher
is Always (and failure is any step failed)
More to your point, is that for me to determine if the build or test have
failed AHP uses post processing scripts. So we have a beanshell script that
parses the build log and like this.
return Fail.unless(
Logic.and(
Logic.and(
Logic.not(Output.contains("BUILD FAILURE")),
Logic.not(Output.contains("<<< FAILURE!")) <-- remove this to ignore
test failures
),
ExitCode.is(0)
)
)
We're Maven 2.0.8
Between the two concepts of job steps and how AHP determines the success and
failure of each step we can control the overall flow of the build job. When our
test fail, we can fail the build, publish the Junit result and skip stuff like
site, tagging or publishing things that might not even exist or be good.
===
-Curt
W: 860.702.9059
M: 860.881.2050
-----Original Message-----
From: Carlos Alonso [mailto:[EMAIL PROTECTED]
Sent: Friday, July 11, 2008 8:11 AM
To: Maven Users List
Subject: Re: Continuous integration build fails if tests fails
As I has understood, you create a duplicated job for every single project so as
to execute those other things?
I'm not sure of having got the idea. Could you please explain a bit deeper
please?
Thanks in advance
Yanko, Curtis escribió:
I can't speak to Hudson but it seems to me in AnthillPro we have a job
step after the build step that always runs to ensure any test get
published. So, even though the build failed we can still do other
things.
===
-Curt
W: 860.702.9059
M: 860.881.2050
-----Original Message-----
From: Carlos Alonso [mailto:[EMAIL PROTECTED]
Sent: Friday, July 11, 2008 4:41 AM
To: users@maven.apache.org
Subject: Continuous integration build fails if tests fails
Hi All.
I'm using Hudson integration environment and I've recently migrated my
scripts from ant to maven. Using ant, when some test cases failed, the
build was set to unstable and a test-results report was raised
indicating which tests failed and why. The problem is that using
maven, the build process is much simpler and maintainable, but, when
some test case fails, the whole build process fails.
Any tip to solve the situation?
Thanks.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity
to which it is addressed. If the reader of this e-mail is not the
intended recipient or his or her authorized agent, the reader is
hereby notified that any dissemination, distribution or copying of
this e-mail is prohibited. If you have received this e-mail in error,
please notify the sender by replying to this message and delete this e-mail immediately.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified
that any dissemination, distribution or copying of this e-mail is
prohibited. If you have received this e-mail in error, please notify the
sender by replying to this message and delete this e-mail immediately.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
