Using Clearcase and Maven3.0.3 with the -T functionality and under Jenkins
1.438 with Tomcat, I'm running into an issue when a build fails at
dependent. This failure gets marked (sometimes) for this module/artifact
and at the "parent" module. This "parent" module is usually the first
module built or the top-level parent pom.
Below are the two that I've noticed,
parent pom
artifact1
artifact2
artifact3 - that depends on artifact1
If a build is executed on the parent pom and artifact3 fails, then the
parent pom is marked as FAILURE. If an incremental build is executed on
artifact1 and artifact3 fails, then artifact1 is marked as FAILURE - even if
the artifact actually compiles. Both of these will cause other poms to be
executed when they were successful. I understand that the parent pom file
would probably be a wise choice to rebuild, but I don't understand why
artifact1 would be rebuilt if artifact3 fails.
This causes issues when an incremental build is executed after this build
failure - and can be problematic if the build is very large. I'm not sure
if this is the intended functionality. I suppose if one wanted the artifact
that's the culprit, then this would be appropriate, but I think it would be
better off to have another XML element for the build.xml file to specify
this, and not the results element.
Does anyone if this is the intended functionality? Is there something that I
may be doing wrong? Currently, the only idea that I have to get around this
is to make a script to parse the logs and refer the name from the log/status
and then hijack the incremental build with my own generated project list.
--
View this message in context:
http://jenkins.361315.n4.nabble.com/Jenkins-reporting-FAILURE-at-starting-artifact-tp4656614.html
Sent from the Jenkins users mailing list archive at Nabble.com.
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to jenkinsci-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
