From: <rya...@jb...> - 2005-07-19 04:08:06
|
Features: + stderr & stdout logged to server/config/log/output.log and server/config/log/error.log. + A shutdown hook is registered with the VM to kill remaining jboss instances on shutdown. + If server does not respond to Shutdown request, the java.lang.Process is destroyed. + Supports nested java task arguments: jvmarg, arg, sysproperty + Core functionality is pure j2se code in test module; no dependencies on Ant or JBoss classes. + I have a schema for configuration with JBossXB, which could allow for shared configurations between the Ant testsuite and an eclipse plugin. However, Ant's xerces is incompatible with JbossXB. TODO: + Replace all start-jboss usage with server:start + Document usage + throw exception if server fails to stop instead of silently destroying process + possbily extend to controlling standalone tomcat instances? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3885386#3885386 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3885386 |
From: <rya...@jb...> - 2005-07-26 03:44:58
|
The server tasks have been fully deployed to jboss-head/testsuite. Next week, I will be migrating this to jboss-4.0 so that we can have valid test runs for that branch as well. Also, I moved these tasks to the test project so that they may be used by other projects like ejb3 (and potentially external ones, too). Note:There still may be something wrong with the server shutdown (under cruisecontrol) which these tasks may mask. If the server fails to shutdown, it's process is destroyed. Really, if a server fails to shutdown, there should be a build failure View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3886520#3886520 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3886520 |
From: <rya...@jb...> - 2005-08-18 22:33:24
|
These tasks are now documented here: http://wiki.jboss.org/wiki/Wiki.jsp?page=ServerControllerTasks View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3890686#3890686 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3890686 |
From: <rya...@jb...> - 2005-08-18 23:09:34
|
Yes, we are planning to do this: http://jira.jboss.com/jira/browse/JBQA-142 This is planned for cruisecontrol-1.4 which should be released ~ Sept 9th. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3890692#3890692 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3890692 |
From: <ad...@jb...> - 2005-08-18 23:06:05
|
Related to the STDERR/STDOUT would it be possible to allow the name of log/server.log to be overridden for each start/stop and collected by the cruisecontrol process? And the same for testsuite/output/log/test.log That way, we can see more detail why a test failed without having to try to reproduce it locally which might not always be possible? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3890691#3890691 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3890691 |
From: <cle...@jb...> - 2005-08-19 02:33:46
|
Ant-JRunit already supports output for System.out and System.err for individual tests. Maybe we should modify our XSL to support such thing. Did we disable System.out and System.err for tests for any reason? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3890710#3890710 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3890710 |
From: <rya...@jb...> - 2005-08-19 16:15:48
|
The AntRunner already captures system.out & system.err from testcases, doesn't it? I see it in the testuite/output/reports/TEST-*.xml files. We are talking about system.out & err from the servers under test, not the test cases. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3890838#3890838 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3890838 |
From: <rya...@jb...> - 2005-08-22 23:59:22
|
Ok, I'm going to merge these Ant tasks in to 4.0 as they seem to be holding up well enough in head. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3891158#3891158 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3891158 |
From: sethladd1 <do-...@jb...> - 2005-09-26 22:17:22
|
Hello, If we wanted to use these tasks in our own Ant scripts, what JAR would contain the tasks? Also, are the compatible with 4.0.0 ? Thanks, Seth View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3897238#3897238 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3897238 |
From: <rya...@jb...> - 2005-09-28 15:10:15
|
This is not included in the jboss dist. You will need to compile 4.0.x. http://wiki.jboss.org/wiki/Wiki.jsp?page=CVSRepository http://docs.jboss.org/jbossas/jboss4guide/r3/html/apc.html It will be under test/output/lib/jboss-test.jar. At the moment, it requires no other depedencies. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3897723#3897723 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3897723 |