Trunk moving to M7 (affects 3.3.0.M1)
by Max Rydahl Andersen
Hi,
3.3.0.M1 never really materialized last week and Eclipse M7 is already out and i.e. maven tooling is not possibly to get to run clean on M6 anyway.
so we are right now discussing moving to Eclipse M7 for trunk and cut a M release out on that instead.
Please let me know ASAP if you see any problems with M7 on your component?
Thanks,
/max
http://about.me/maxandersen
13 years, 7 months
- 1
- 2
M1 Status Update - trunk and maintenance branch
by Nick Boldt
Overall:
* 2 stuck slaves (vmg17, hudson1) reported to eng-ops@; one taken down,
the other left up because another team's currently using it.
* Hudson's next scheduled maintenance is April 29th, 2011 - 6:00AM GMT,
so I can't kick jobs to run over night :(
---
JBT 3.3.0.M1 / JBDS 5.0.0.M1:
* Savara/Scribble missing (refactored?) feature:
https://issues.jboss.org/browse/JBIDE-8817 (blocks aggregate build)
* AS - single test failure: https://issues.jboss.org/browse/JBIDE-8816
* VPE had 219 tests on Jan 11; now only 17 tests are running and of
those, 6 are failing
* Seam has 3 test failures: https://issues.jboss.org/browse/JBIDE-8759
---
JBT 3.2.1.M1 / JBDS 4.1.0.M1:
* Aggregate builder is fixed (I think!), but hit a network snag trying
to fetch latest bits because I disabled the "wait until all upstream are
done" option in the job in order to test my latest publish.sh fixes.
Respin will fix this & allow me to verify my fix worked, then I can
re-enable the block-while-upstream-spinning option.
* One last Seam test failure: https://issues.jboss.org/browse/JBIDE-8818
* AS & Deltacloud jobs time out after 2hrs; job timeout increased to
3hrs. Would respin but Hudson is in shutdown mode.
* JSF was clean (no failures) but now has 7 new tests and 14 new
failures: https://issues.jboss.org/browse/JBIDE-8819
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
13 years, 7 months
- 5
- 12