[jbosstools-dev] ACTION REQUIRED: JBT 4.1.2.CR1 / JBDS 7.1.1.CR1 build status

The following issues block the release of CR1 to QE, due to incorrect parent pom reference in root pom: Server : https://issues.jboss.org/browse/JBIDE-16681 OpenShift : https://issues.jboss.org/browse/JBIDE-16683 LiveReload : https://issues.jboss.org/browse/JBIDE-16686 Please apply these PRs: https://github.com/jbosstools/jbosstools-server/pull/205 https://github.com/jbosstools/jbosstools-openshift/pull/364 https://github.com/jbosstools/jbosstools-livereload/pull/76 Then you can close the above JIRAs, and kick your jobs: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... Mickael sent out an email on Thursday [1] reminding everyone to do the above, but as that process deviates from the usual task JIRA notification method, a few projects forgot / didn't see the email. [1] http://lists.jboss.org/pipermail/jbosstools-dev/2014-February/008612.html The result is that we won't have a build ready for QE by EOD tonight. ---- In addition to the above blocking issues, there are a few projects with test failures, including (but not limited to) these: Hibernate : https://issues.jboss.org/browse/JBIDE-16669 Webservices: : https://issues.jboss.org/browse/JBIDE-16670 These may in fact be configuration problems w/ the new "virt" slaves, but figured it was worth documenting the issues in case there's a larger problem here. Suspect we can solve this simply by excluding the "virt" slaves or by having the slaves fixed to include whatever is missing for running tests. If the test owners can speculate as to what's missing in the above JIRAs, that might help me communicate that to eng-ops in order to get the missing config added. Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com