[jbosstools-dev] JBT 3.2.1.CR1 / JBDS 4.1.0.CR1 status

[Nick Boldt]

After respins, the only job that's non-blue is the .tests job, which is 
notorious for being red (it has had a single failing test for the past 
two builds [1], [2]). Unfortunately this job takes 5-7hrs to run, and is 
only 3-1/2 hrs into its last run.

[1]http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Stable_Branch/portlet/dashboard_portlet_9/job/jbosstools-3.2_stable_branch.tests/209/testReport/org.jboss.tools.seam.ui.test.wizard/Seam20XOperationsTestSuite220GA/org_jboss_tools_seam_ui_test_wizard_Seam20WARNewOperationTest/ 

[2]http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Stable_Branch/portlet/dashboard_portlet_9/job/jbosstools-3.2_stable_branch.tests/210/testReport/org.jboss.ide.eclipse.as.archives.integration.test/ASArchivesIntegrationTestSuite/testAll/

I'll let it grind for a while and if I'm not completely asleep in an 
hour or so, I may in fact pull off the latest good builds for JBT 
aggregate and JBDS product so that they're ready to go first-thing for 
QE tomorrow, BEFORE the 10am/4pm meeting.

Either way, we're looking good for tomorrow's release of CR1 candidate 
to QE.

N

On 05/31/2011 07:22 PM, Brian Fitzpatrick wrote:
> Yay!! We'll look at the non-blue respins tomorrow, but that's awesome!
>
> Thanks for the great news Nick! Then we can kick it on the CR2 work and hopefully put JBT 3.2.1 / JBDS 4.1 to rest. :)
>
> --Fitz
>
> _______________________________
> Brian Fitzpatrick (aka "Fitz")
> Senior Software Engineer, SOA-P
> JBoss by Red Hat
>
> ----- Original Message -----
> From: "Nick Boldt"<nboldt at redhat.com>
> To: external-exadel-list at redhat.com, jbosstools-dev at lists.jboss.org, jbds-pm-list at redhat.com
> Sent: Tuesday, May 31, 2011 4:48:07 PM
> Subject: [jbosstools-dev] JBT 3.2.1.CR1 / JBDS 4.1.0.CR1 status
>
> CR1 status: GREEN!
>
> ----
>
> Aside from some builds that have failed for no good reason (and are
> being respun to prove to me it's no good reason, just a Hudson snafu or
> swimlane problem), we're essentially ready for CR1.
>
> Found a minor (and probably intermittent) test failure
> (https://issues.jboss.org/browse/JBIDE-9043) but I've set that for CR2.
>
> Looks like JBT and JBDS builds are all blue, except for these respins [0]:
>
> * examples,
> * maven,
> * seam (used to have 362 tests but last good build only had 294 [1])
> * smooks,
> * struts,
> * teiid 7.4,
>
> * continuous (all-in-one compilation test), and
> * tests (all-in-one all tests)
>
> [0]
> http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Stable_Branch/portlet/dashboard_portlet_9/
>
> [1]
> http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Stable_Branch/portlet/dashboard_portlet_9/job/jbosstools-3.2_stable_branch.component--seam/
>
> So, we should be good to go tomorrow after the
> US-morning/Europe-afternoon status meeting to declare a build for QE.
>
> The usual URLs for nightlies are in play, but after that declaration
> I'll move stuff into a stable folder so it won't disappear&  QE can
> begin testing, and we'll reopen for CR2 work.
>
> Cheers,
>

-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com