river-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Costers (JIRA)" <j...@apache.org>
Subject [jira] Commented: (RIVER-349) Setup separate Hudson job for QA testing
Date Sun, 29 Aug 2010 21:33:53 GMT

    [ https://issues.apache.org/jira/browse/RIVER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904038#action_12904038

Jonathan Costers commented on RIVER-349:

I just setup the following in Hudson:

-> polls svn hourly, runs "ant all.clean release", which builds everything, executes Junit
tests and creates release zip files
This should now take less than 30min to complete

River-trunk-QA (new):
-> polls dvn daily, runs "ant all.clean all.jars qa.run", which builds all JARs and runs
the QA suite
This takes hours to complete

You can look at these jobs, their build attempts etc here: https://hudson.apache.org/hudson/view/River/

Unfortunately, Hudson seems to be experiencing overload, I'm not able to test my changes to
River-trunk at the moment.
River-trunk-QA has already been successfully executed once.

> Setup separate Hudson job for QA testing
> ----------------------------------------
>                 Key: RIVER-349
>                 URL: https://issues.apache.org/jira/browse/RIVER-349
>             Project: River
>          Issue Type: Improvement
>          Components: build
>         Environment: Hudson
>            Reporter: Jonathan Costers
>            Assignee: Jonathan Costers
> As discussed on river-dev, we should probably to split our CI build job in different
> - a job that builds the latest revision, runs JUnit tests and creates release bundles
(hourly poll from svn) - fast
> - a job that builds the latest revision and runs QA test suite (daily poll from svn)
- slow

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message