Re: automatic builds update
If we build the Geronimo 2.2 on JDK 1.6, it will not run successfully on JDK 1.5. The reason is that, some security APIs are changed in JDK 1.6, while our GBean builder will add those public methods as its own operations, and car-maven-plugin will serialize some gbean related data in the config.ser files. So ... 2009/8/28 chi runhua chirun...@gmail.com Hi, one short question here. According to Geronimo-4089, G2.2 can be built on Java 6 and it's a new feature for G2.2. why are we still using Java 5 for 2.2 branch build? https://issues.apache.org/jira/browse/GERONIMO-4089 Jeff C On Thu, Aug 27, 2009 at 1:28 AM, Jarek Gawor jga...@gmail.com wrote: I updated the build schedule a bit more, here's the new schedule: branches/2.0: not build anymore (let me know if somebody really wants it) branches/2.1: 2am with Sun Java 5 branches/2.2: 8am and 2pm with Sun Java 5 8pm with IBM Java 5 trunk: 3am and 3pm with Sun Java 6 9am and 9pm with IBM Java 6 In short, 2.1 is now build only once per day, 2.2 is build 3 times per day with Java 5, and trunk is build 4 times per day with Java 6. Jarek On Fri, Aug 21, 2009 at 11:39 AM, Donald Woodsdwo...@apache.org wrote: How about we build 2.2 four times daily until we release it and only build the unstable trunk once or twice a day for now? -Donald Jarek Gawor wrote: Hi, I changed the schedule of automated Geronimo builds a bit since we created a branch for 2.2. Here's the new schedule (times are all in EDT): branches/2.0: not build anymore (let me know if somebody really wants it) branches/2.1: 2am and 8pm - both with Sun Java 5 branches/2.2: 8am and 2pm - both with Sun Java 5 trunk: 9am, 3pm with Sun Java 5 3am with IBM Java 5 9pm with Sun Java 6 Jarek -- Ivan
Re: automatic builds update
We want to retain support for Java 5 in 2.2. -Jack On Fri, Aug 28, 2009 at 1:25 PM, chi runhua chirun...@gmail.com wrote: Hi, one short question here. According to Geronimo-4089, G2.2 can be built on Java 6 and it's a new feature for G2.2. why are we still using Java 5 for 2.2 branch build? https://issues.apache.org/jira/browse/GERONIMO-4089 Jeff C On Thu, Aug 27, 2009 at 1:28 AM, Jarek Gawor jga...@gmail.com wrote: I updated the build schedule a bit more, here's the new schedule: branches/2.0: not build anymore (let me know if somebody really wants it) branches/2.1: 2am with Sun Java 5 branches/2.2: 8am and 2pm with Sun Java 5 8pm with IBM Java 5 trunk: 3am and 3pm with Sun Java 6 9am and 9pm with IBM Java 6 In short, 2.1 is now build only once per day, 2.2 is build 3 times per day with Java 5, and trunk is build 4 times per day with Java 6. Jarek On Fri, Aug 21, 2009 at 11:39 AM, Donald Woodsdwo...@apache.org wrote: How about we build 2.2 four times daily until we release it and only build the unstable trunk once or twice a day for now? -Donald Jarek Gawor wrote: Hi, I changed the schedule of automated Geronimo builds a bit since we created a branch for 2.2. Here's the new schedule (times are all in EDT): branches/2.0: not build anymore (let me know if somebody really wants it) branches/2.1: 2am and 8pm - both with Sun Java 5 branches/2.2: 8am and 2pm - both with Sun Java 5 trunk: 9am, 3pm with Sun Java 5 3am with IBM Java 5 9pm with Sun Java 6 Jarek
Re: automatic builds update
I updated the build schedule a bit more, here's the new schedule: branches/2.0: not build anymore (let me know if somebody really wants it) branches/2.1: 2am with Sun Java 5 branches/2.2: 8am and 2pm with Sun Java 5 8pm with IBM Java 5 trunk: 3am and 3pm with Sun Java 6 9am and 9pm with IBM Java 6 In short, 2.1 is now build only once per day, 2.2 is build 3 times per day with Java 5, and trunk is build 4 times per day with Java 6. Jarek On Fri, Aug 21, 2009 at 11:39 AM, Donald Woodsdwo...@apache.org wrote: How about we build 2.2 four times daily until we release it and only build the unstable trunk once or twice a day for now? -Donald Jarek Gawor wrote: Hi, I changed the schedule of automated Geronimo builds a bit since we created a branch for 2.2. Here's the new schedule (times are all in EDT): branches/2.0: not build anymore (let me know if somebody really wants it) branches/2.1: 2am and 8pm - both with Sun Java 5 branches/2.2: 8am and 2pm - both with Sun Java 5 trunk: 9am, 3pm with Sun Java 5 3am with IBM Java 5 9pm with Sun Java 6 Jarek
Re: automatic builds update
How about we build 2.2 four times daily until we release it and only build the unstable trunk once or twice a day for now? -Donald Jarek Gawor wrote: Hi, I changed the schedule of automated Geronimo builds a bit since we created a branch for 2.2. Here's the new schedule (times are all in EDT): branches/2.0: not build anymore (let me know if somebody really wants it) branches/2.1: 2am and 8pm - both with Sun Java 5 branches/2.2: 8am and 2pm - both with Sun Java 5 trunk: 9am, 3pm with Sun Java 5 3am with IBM Java 5 9pm with Sun Java 6 Jarek
automatic builds update
Hi, I changed the schedule of automated Geronimo builds a bit since we created a branch for 2.2. Here's the new schedule (times are all in EDT): branches/2.0: not build anymore (let me know if somebody really wants it) branches/2.1: 2am and 8pm - both with Sun Java 5 branches/2.2: 8am and 2pm - both with Sun Java 5 trunk: 9am, 3pm with Sun Java 5 3am with IBM Java 5 9pm with Sun Java 6 Jarek
automatic builds
FYI, I just changed the automatic builds (for trunk and branches/2.0) to run the testsuites with both containers (before it was tested with Tomcat only). So now a build will be successful if the testsuites pass with both containers. Jarek
Re: automatic builds with tests
Right. We have talked about this before and the majority opinion was to have a separate subject line. I have a gmail reader, but then again it's not about how I want it. I'll gladly put whatever the majority of the community decides. Start a [VOTE] thread :-)) Cheers Prasad On 9/19/07, Kevan Miller [EMAIL PROTECTED] wrote: On Sep 19, 2007, at 4:28 PM, Prasad Kashyap wrote: OK. I have enabled the unit tests to run on all builds for both trees (2.0 and trunk). The testsuite presently runs only with all 2.0 builds. I'm soon going to enable it to run on all trunk builds too. Now that all tests are running, there will be only 4 builds a day - 4 am, 10 am, 4 pm and 10 pm. Great. Seems like we talked about this, before... I wish your emails would have non-mutable Subjects. Rather than including the Revision number or number of tests passed/failed, just indicate success or failure. Details are in the body of the mail, already... For example: [BUILD] Trunk: Successful for Revision: 577451 [BUILD] 2.0: Failed for Revision: 577231 Since the revision number is always changing, each of those emails will be a separate Subject thread. [BUILD] Trunk: Successful [BUILD] branches/2.0: Failed These emails would be sorted into the same discussion thread as previous notifications... I don't know about your mail reader, but this would really reduce the amount of real estate your notifications take up. Also, much easier for me to delete ;-) --kevan
Re: automatic builds with tests
I supposed I could live with it either way. I do tend to keep the messages and I prefer to have unique threads so that if we need to start a discussion on a particular build (as we have in the past) the responses can be associated with the correct message. I personally have a filter and put any message containing [BUILD] in the subject into a build folder ... so the real estate isn't critical to me. I think we could compromise ... A common subject for successful builds (to which we typically would not need to respond) and a unique subject for failed builds. What do you think? Joe Kevan Miller wrote: On Sep 20, 2007, at 10:50 AM, Prasad Kashyap wrote: Right. We have talked about this before and the majority opinion was to have a separate subject line. I have a gmail reader, but then again it's not about how I want it. I'll gladly put whatever the majority of the community decides. Start a [VOTE] thread :-)) Just checking... If others are happy with the way things are, I can deal... --kevan
Re: automatic builds with tests
On Sep 20, 2007, at 10:50 AM, Prasad Kashyap wrote: Right. We have talked about this before and the majority opinion was to have a separate subject line. I have a gmail reader, but then again it's not about how I want it. I'll gladly put whatever the majority of the community decides. Start a [VOTE] thread :-)) Just checking... If others are happy with the way things are, I can deal... --kevan
Re: automatic builds with tests
I like the unique subjects... Is there a way we could use a gbuild user id for sending the email notices? That way people can easily setup filters to move them to a different folder -Donald Joe Bohn wrote: I supposed I could live with it either way. I do tend to keep the messages and I prefer to have unique threads so that if we need to start a discussion on a particular build (as we have in the past) the responses can be associated with the correct message. I personally have a filter and put any message containing [BUILD] in the subject into a build folder ... so the real estate isn't critical to me. I think we could compromise ... A common subject for successful builds (to which we typically would not need to respond) and a unique subject for failed builds. What do you think? Joe Kevan Miller wrote: On Sep 20, 2007, at 10:50 AM, Prasad Kashyap wrote: Right. We have talked about this before and the majority opinion was to have a separate subject line. I have a gmail reader, but then again it's not about how I want it. I'll gladly put whatever the majority of the community decides. Start a [VOTE] thread :-)) Just checking... If others are happy with the way things are, I can deal... --kevan smime.p7s Description: S/MIME Cryptographic Signature
Re: automatic builds with tests
OK. I have enabled the unit tests to run on all builds for both trees (2.0 and trunk). The testsuite presently runs only with all 2.0 builds. I'm soon going to enable it to run on all trunk builds too. Now that all tests are running, there will be only 4 builds a day - 4 am, 10 am, 4 pm and 10 pm. Cheers Prasad. On 9/17/07, Paul McMahan [EMAIL PROTECTED] wrote: +1 On Sep 14, 2007, at 4:43 PM, Jarek Gawor wrote: I know that at least the 5am build runs with tests on. I would like to change that so that each build always runs with all tests enabled. Some of the tests in testsuite/ directory actaully start the server so if they are successful we should at least know that the server starts up ok and applications can be deployed to it. That should enable us to quickly catch and address problems as people commit their changes. If people agree on this change, I'm willing to spend whatever time is necessary to make this happen. Jarek
Re: automatic builds with tests
+1 Jarek Gawor wrote: I know that at least the 5am build runs with tests on. I would like to change that so that each build always runs with all tests enabled. Some of the tests in testsuite/ directory actaully start the server so if they are successful we should at least know that the server starts up ok and applications can be deployed to it. That should enable us to quickly catch and address problems as people commit their changes. If people agree on this change, I'm willing to spend whatever time is necessary to make this happen. Jarek smime.p7s Description: S/MIME Cryptographic Signature
Re: automatic builds with tests
+1 On Sep 14, 2007, at 4:43 PM, Jarek Gawor wrote: I know that at least the 5am build runs with tests on. I would like to change that so that each build always runs with all tests enabled. Some of the tests in testsuite/ directory actaully start the server so if they are successful we should at least know that the server starts up ok and applications can be deployed to it. That should enable us to quickly catch and address problems as people commit their changes. If people agree on this change, I'm willing to spend whatever time is necessary to make this happen. Jarek
Re: automatic builds with tests
+1000 david jencks On Sep 14, 2007, at 4:43 PM, Jarek Gawor wrote: I know that at least the 5am build runs with tests on. I would like to change that so that each build always runs with all tests enabled. Some of the tests in testsuite/ directory actaully start the server so if they are successful we should at least know that the server starts up ok and applications can be deployed to it. That should enable us to quickly catch and address problems as people commit their changes. If people agree on this change, I'm willing to spend whatever time is necessary to make this happen. Jarek
automatic builds with tests
I know that at least the 5am build runs with tests on. I would like to change that so that each build always runs with all tests enabled. Some of the tests in testsuite/ directory actaully start the server so if they are successful we should at least know that the server starts up ok and applications can be deployed to it. That should enable us to quickly catch and address problems as people commit their changes. If people agree on this change, I'm willing to spend whatever time is necessary to make this happen. Jarek
Re: automatic builds with tests
Yes! This would definitely take care of at least some of MY headaches. +1 On 9/14/07, David Jencks [EMAIL PROTECTED] wrote: +1000 david jencks On Sep 14, 2007, at 4:43 PM, Jarek Gawor wrote: I know that at least the 5am build runs with tests on. I would like to change that so that each build always runs with all tests enabled. Some of the tests in testsuite/ directory actaully start the server so if they are successful we should at least know that the server starts up ok and applications can be deployed to it. That should enable us to quickly catch and address problems as people commit their changes. If people agree on this change, I'm willing to spend whatever time is necessary to make this happen. Jarek -- Erik B. Craig
