[jboss-as7-dev] JBoss AS 7.0.0.Beta1 tagged...

[Shelly McGowan]

The osgi (or any other component) test suite can be easily be added as a downstream project to the AS 7 build. 

This afternoon I created two JBoss AS 7 testsuite jobs - one running with Sun JDK 1.6 and the other with OpenJDK 1.6:

http://hudson.jboss.org/hudson/job/JBoss-AS-7.0.x-testSuite-sun16/
http://hudson.jboss.org/hudson/job/JBoss-AS-7.0.x-testSuite-openjdk/

The JBoss-AS-7.0.x-testSuite-openjdk is not yet published as it fails due to a compilation error 
( http://pastebin.com/T3EH108H ).  I've had the OpenJDK version upgraded to the latest and another job
is queued.

The JBoss-AS-7.0.x-testSuite-sun16 is not completing as it is hanging running the demos.  I'm seeing
similar issues with the latest JBoss AS 7 build which Aborts due to time out as it is hanging as well:
http://hudson.jboss.org/hudson/job/JBoss-AS-7.0.x/

I'll look into it.

Rajesh offered to test and upload the community releases starting with the CR1.   For the AS 6 release, they followed this check list:
http://community.jboss.org/wiki/JBossAS6xReleaseChecklist

I created wiki to start identifying what needs to be done for an AS 7 release.  You can start filling in the blanks here:
http://community.jboss.org/wiki/JBossAS7xReleaseChecklist


Shelly McGowan
JBoss, by Red Hat


----- Original Message -----
From: "Jason Greene" <jgreene at redhat.com>
To: "Brian Stansberry" <brian.stansberry at redhat.com>
Cc: jboss-as7-dev at lists.jboss.org
Sent: Thursday, March 17, 2011 6:01:51 PM
Subject: Re: [jboss-as7-dev] JBoss AS 7.0.0.Beta1 tagged...

Exactly. We need a Hudson run that is current upstream with the osgi testsuite. A two week cycle doesn't allow for a freeze plus days of testing.

IMO we should just fix the osgi issue in beta2 which is a little over a week away.

Sent from my iPhone

On Mar 17, 2011, at 9:35 AM, Brian Stansberry <brian.stansberry at redhat.com> wrote:

> The thing that needs to be solved is automating it. For beta releases, 
> it can't be a mode of "do a code freeze, tag something and then poll 
> project leads for acceptance." CRs and GA can be more time consuming, 
> but in order to support weekly or bi-weekly beta releases there needs to 
> be something where we can tag/branch, run some job and then get a green 
> light.
> 
> On 3/17/11 10:23 AM, Thomas Diesler wrote:
>> How about creating a branch after code freeze. Any change to the branch
>> must have a "very good reason" and would trigger a new test cycle. This
>> would include external test suites that we know about. In practise WS,
>> OSGi and possibly others would have to produce a stable hudson run on
>> the latest code freeze branch.
>> 
>> On 03/17/2011 03:56 PM, David M. Lloyd wrote:
>>> I don't have any really good solution to this problem...
>>> 
>>> On 03/17/2011 05:23 AM, Thomas Diesler wrote:
>>>> David, the AS test suite needs to be comprehensive - no doubt. However,
>>>> we have a release cycle that is different from AS and continuously test
>>>> a large set of OSGi functionality against AS7 trunk one a nightly basis.
>>>> 
>>>> Following your suggested approach, I would need to duplicate every OSGi
>>>> example and functional test in the AS7 code base. Alternatively, I'm
>>>> suggesting to have a known "Code Freeze" date and give every subsystem
>>>> that has an external test suite a chance to verify/veto the intended
>>>> release code base.
>>>> 
>>>> 1.0.0.Beta1 was broken for OSGi webapps because of last minute changes -
>>>> I'm looking for ways to possibly fix Beta1 and have a reasonable process
>>>> that avoids this to happen in the future.
>>>> 
>>>> cheers
>>>> -thomas
>>>> 
>>>> On 03/16/2011 02:30 PM, David M. Lloyd wrote:
>>>>> Thomas I think ultimately we need a comprehensive in-AS test suite.
>>>>> This is the only way we're going to be able to catch problems on an
>>>>> ongoing basis. I don't think we can afford to externally validate only
>>>>> once per release - I can absolutely guarantee that this will cause
>>>>> unexpected release delays.
>>>>> 
>>>>> On 03/16/2011 04:27 AM, Thomas Diesler wrote:
>>>>>> Hi David,
>>>>>> 
>>>>>> do we have a process that allows subsystem providers to verify a
>>>>>> potential AS7 release before it gets tagged? I have an extensive OSGi
>>>>>> testsuite that runs on a nightly basis against AS7 master. I noticed
>>>>>> this morning that this commit
>>>>>> 
>>>>>> https://github.com/jbossas/jboss-as/commit/fd5696596545d9d9c2e4eb4c499bf3f1b7be62f1#server/src/main/java/org/jboss/as/server/deployment/Phase.java
>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> broke OSGi webapp support again. The related issue, which I now
>>>>>> reopened, is https://issues.jboss.org/browse/JBAS-8940
>>>>>> 
>>>>>> Can we perhaps resolve this issue before Beta1 becomes generally
>>>>>> available?
>>>>>> To move forward I'll improve OSGi test coverage to a level were it
>>>>>> covers everything that is expected to work.
>>>>>> 
>>>>>> cheers
>>>>>> -thomas
>>>>>> 
>>>>>> On 03/16/2011 02:14 AM, David M. Lloyd wrote:
>>>>>>> I've pushed out a 7.0.0.Beta1-prerelease tag and updated upstream for
>>>>>>> Beta2 development. Later this week Jason will be setting the release
>>>>>>> "code name" and uploading the binary artifacts to be made available for
>>>>>>> downloading and taking care of all that business.
>>>>>>> 
>>>>>>> Big thanks to everyone who put in extra effort to get this tag done. I
>>>>>>> expect that the official release announcement will be happening later
>>>>>>> this week.
>>>>>>> 
>>>>> 
>>> 
>> 
> 
> 
> -- 
> Brian Stansberry
> Principal Software Engineer
> JBoss by Red Hat
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

_______________________________________________
jboss-as7-dev mailing list
jboss-as7-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-as7-dev