You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@buildr.apache.org by Peter Schröder <ps...@blau.de> on 2009/11/25 13:54:09 UTC
cobertura tasks and test.using :integration
hi,
we have an issue regarding the order of task when running cobertura-tasks in the test-integration mode.
we want to package the cobertura-results, so that an reports-artifact can be created and uploaded, but the package task needs to be run before the test-integration setup and teardown. but the cobertura task needs to run the tests...
any ideas?
AW: cobertura tasks and test.using :integration
Posted by Peter Schröder <ps...@blau.de>.
i think that we wont do this right now, cause cobertura-coverage is not interesting in our system-test-setup, so we just ignore them when test.options[:integration] is set.
i will report back if we come back to this issue in the next month.
________________________________________
Von: Alex Boisvert [alex.boisvert@gmail.com]
Gesendet: Donnerstag, 26. November 2009 20:21
An: users@buildr.apache.org
Betreff: Re: cobertura tasks and test.using :integration
On Wed, Nov 25, 2009 at 10:36 PM, Peter Schröder <ps...@blau.de> wrote:
> you mean a self-defined task with a zip-task to create the report-artifact?
>
yes.
> we probably would need to create some other kind of top-level
> package-report task, because we join all created reports (cobertura, junit,
> javadoc...) into one big reports-zip and upload this to our bamboo-server,
> so that we can attach all reports to a build.
>
yes, that would be very nice. if you implement this, I would be very
interested in bringing it into buildr.
alex
Re: cobertura tasks and test.using :integration
Posted by Alex Boisvert <al...@gmail.com>.
On Wed, Nov 25, 2009 at 10:36 PM, Peter Schröder <ps...@blau.de> wrote:
> you mean a self-defined task with a zip-task to create the report-artifact?
>
yes.
> we probably would need to create some other kind of top-level
> package-report task, because we join all created reports (cobertura, junit,
> javadoc...) into one big reports-zip and upload this to our bamboo-server,
> so that we can attach all reports to a build.
>
yes, that would be very nice. if you implement this, I would be very
interested in bringing it into buildr.
alex
Re: cobertura tasks and test.using :integration
Posted by Peter Schröder <ps...@blau.de>.
you mean a self-defined task with a zip-task to create the report-artifact?
we probably would need to create some other kind of top-level package-report task, because we join all created reports (cobertura, junit, javadoc...) into one big reports-zip and upload this to our bamboo-server, so that we can attach all reports to a build.
Am 25.11.2009 um 20:58 schrieb Alex Boisvert:
> Create a package task for the cobertura reports (which is not a dependency
> of :package) and add it as a dependency of :upload ?
>
> On Nov 25, 2009 4:54 AM, "Peter Schröder" <ps...@blau.de> wrote:
>
> hi,
>
> we have an issue regarding the order of task when running cobertura-tasks in
> the test-integration mode.
>
> we want to package the cobertura-results, so that an reports-artifact can be
> created and uploaded, but the package task needs to be run before the
> test-integration setup and teardown. but the cobertura task needs to run the
> tests...
>
> any ideas?
Re: cobertura tasks and test.using :integration
Posted by Alex Boisvert <al...@gmail.com>.
Create a package task for the cobertura reports (which is not a dependency
of :package) and add it as a dependency of :upload ?
On Nov 25, 2009 4:54 AM, "Peter Schröder" <ps...@blau.de> wrote:
hi,
we have an issue regarding the order of task when running cobertura-tasks in
the test-integration mode.
we want to package the cobertura-results, so that an reports-artifact can be
created and uploaded, but the package task needs to be run before the
test-integration setup and teardown. but the cobertura task needs to run the
tests...
any ideas?