Hi,
the job is configured in a way that when the testsuite fails, old zip is
archived.
( See
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-testsui...
and the archived zip at
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-testsui...
)
Could someone please add `set +e` at the beginning, or add `... || true`
after `mvn` running the testsuite, or something such what would let the
zip run at the end?
Thanks,
Ondra
On 12/11/2012 02:42 AM, Brian Stansberry wrote:
On 12/8/12 2:27 AM, Ondrej Zizka wrote:
> Hi all,
>
> I'd like to try to leverage JUnitDiff for AS CI.
> JUnitDiff example:
>
http://dev39.mw.lab.eng.bos.redhat.com/~ozizka/projects/junitdiff/AGG_TES...
> (older version, I don't have nice enough data to show with new)
>
> Could we please archive the test report files of this job?
>
http://lightning.mw.lab.eng.bos.redhat.com/jenkins/job/as7-master-testsui...
> All I need is something like this at the end:
>
> find testsuite/ -name 'TEST-*.xml' -or -name '*-output.txt' |
zip
> testsuite-reports.zip -@
>
> and have testsuite-reports.zip archived.
Done.
> The zip currently has 2.7 MB if there are no or few errors. The job
> keeps 100 runs. That's 270 MB, I think that's no problem.
>
> JUnitDiff has an integration with Jenkins - a plugin which can create
> these reports automatically.
> It could help detect intermittent tests more easily; also, it could help
> with certain analysis, like test failures corelation etc.
> So if it proves useful, we could add it to the builds.
> If not, at least me and Honza Brazdil will have some real data to test
> JUnitDiff with :)
>
> Thanks,
> Ondra
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
>