You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@river.apache.org by "Jonathan Costers (JIRA)" <ji...@apache.org> on 2010/08/29 23:25:53 UTC
[jira] Created: (RIVER-349) Setup separate Hudson job for QA
testing
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 pieces:
- 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.
[jira] Resolved: (RIVER-349) Setup separate Hudson job for QA
testing
Posted by "Jonathan Costers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Costers resolved RIVER-349.
------------------------------------
Fix Version/s: AR3
Resolution: Fixed
setup build jobs as described
> 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
> Fix For: AR3
>
>
> As discussed on river-dev, we should probably to split our CI build job in different pieces:
> - 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.
[jira] Closed: (RIVER-349) Setup separate Hudson job for QA testing
Posted by "Jonathan Costers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jonathan Costers closed RIVER-349.
----------------------------------
> 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
> Fix For: AR3
>
>
> As discussed on river-dev, we should probably to split our CI build job in different pieces:
> - 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.
[jira] Work started: (RIVER-349) Setup separate Hudson job for QA
testing
Posted by "Jonathan Costers (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/RIVER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on RIVER-349 started by Jonathan Costers.
> 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 pieces:
> - 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.
[jira] Commented: (RIVER-349) Setup separate Hudson job for QA
testing
Posted by "Jonathan Costers (JIRA)" <ji...@apache.org>.
[ 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:
River-trunk:
-> 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 pieces:
> - 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.