-
Bug
-
Resolution: Won't Fix
-
Major
-
None
-
Platform: All, OS: All
I have a job that is configured to show coverage reports using the cobertura
plugin. When I use the m2release plugin, it will successfully release the plugin
but the build itself will fail at the end since the cobertura action is
expecting reports. Perhaps the m2release plugin could remove all other post
actions such as the cobertura plugin when it is going to do a release?
Output:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 18 minutes 16 seconds
[INFO] Finished at: Wed Aug 26 00:33:53 CEST 2009
[INFO] Final Memory: 26M/47M
[INFO] ------------------------------------------------------------------------
Waiting for Hudson to finish collecting data
channel stopped
Publishing Cobertura coverage report...
No coverage results were found using the pattern
'**/target/site/cobertura/coverage.xml' relative to
'/home/hudson/hudson/data/jobs/Hudson plugin The Continuous Integration
Game/workspace/./'. Did you enter a pattern relative to the correct directory?
Did you generate the XML report(s) for Cobertura?
Finished: FAILURE
- depends on
-
JENKINS-4410 split release into two
-
- Open
-
[JENKINS-4399] A successful release can be marked as Failed if there are any post build actions that require reports
closing bug.
The other plugin is failing the build because it expects there to be a report and fails the build otherwise.
The plugin should use hudsons ability to verify the mojo that generates the report ran before assuming that the build report exists.
PLease open a JIRA with the relevant components.
TIm Azzopardi
added a comment - "PLease open a JIRA with the relevant components."
See https://issues.jenkins-ci.org/browse/JENKINS-12640 
as a workaround you could try appending cobertura:cobertura (or whatever is
requered to run corbetura) to the release goals so that the mojo is run
afterwards.
Personally I consider this a defect in the corbetrura and clover plugins that
fails the build if the report isn't there - it should check that the mojo was
run during the build and only fail if it ran and the report was empty.
However the correct fix for this requires splitting the preparation from the
performing of the release and I have no time to work on that for the forseable
future, and is the direction I would ultimatley like to take the plugin.