M5 spin status :: no aggregate or JBDS installers available yet; many bot and non-UI test failures, plus one inter-build compilation failure
by Nick Boldt
Since turning on the stable branch jobs, here's what's borked...
https://issues.jboss.org/browse/JBIDE-10349
Still trying to get a clean stable_branch aggregate build (and then JBT
builds too) - last time the aggregate failed due to missing Central,
OTDT, and OpenShift (hadn't spun clean yet).
---
Details:
- hibernate : test failure in org.hibernate.eclipse.console.test
- jbpm : test failure in org.jboss.tools.jbpm.convert.test
- jsf : test failure in org.jboss.tools.jsf.vpe.jsf.test
- maven : 15 bot test failures (same failures in trunk) ... should these
just be turned off and only run locally / manually?
- struts : COMPILE FAILED - upstream bits missing? "The import
org.jboss.tools.jst.web.validation cannot be resolved."
---
There are also a few jobs for which the latest build failed, but at
least we have one good build since branching. This suggests we're having
some stability issues w/ a few Jenkins slaves, but at least we're
getting clean spins when the server is quiet(er).
= archives : aborted build? [Dec 4 ok]
= birt : failed to find usage bits (poor timing between builds) [Dec 4 ok]
= seam : no more locks failure [Dec 4 ok]
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
2 weeks, 1 day
REMINDER :: Code freeze / Feature freeze / UI freeze for 4.7.0.AM1 / 12.9.0AM1 is TODAY, Wed, July 25
by Mat Booth
Reminder, code freeze / feature freeze / UI freeze for 4.7.0.AM1 /
12.9.0AM1 is TODAY, Wed, July 25
Please get all your stuff into github by EOD (in your timezone) on Wed so
we can spin up the builds over night and have something to stage for QE on
Thurs.
If your tests are not all green, please at least have a look at them. They
should really not be yellow or red at this point.
Thanks all
7 years, 5 months
Proposed 4.9.0.AM3-SNAPSHOT target platform change(s): cameltooling; 1.0.0.201808131436
by nboldt＠redhat.com
docker;4.1.0.201808292200
m2e;1.9.1.20180829-1411
orbit;I20180829144012
reddeer;2.3.0.Beta
simrel;20180830-1300-Simrel.2018-09.M3
webtools;S-3.11.0.M3-20180823041738
Cc: nboldt(a)redhat.com
Message-ID: <5b88aadd.taXufW4dOtGmXRHV%nboldt(a)redhat.com>
User-Agent: Heirloom mailx 12.5 7/5/10
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Here is a proposal for change(s) to the JBoss Tools / Red Hat Developer Studio / Red Hat Central target platforms.
Affected Versions:
jbosstools 4.9.0.AM3
devstudio 12.9.0.AM3
jbt/ds TPs 4.9.0.AM3-SNAPSHOT
central TPs 4.9.0.AM2-SNAPSHOT
Detail / Summary:
cameltooling;1.0.0.201808131436
docker;4.1.0.201808292200
m2e;1.9.1.20180829-1411
orbit;I20180829144012
reddeer;2.3.0.Beta
simrel;20180830-1300-Simrel.2018-09.M3
webtools;S-3.11.0.M3-20180823041738
Related JIRA(s):
https://issues.jboss.org/browse/JBIDE-26180
Pull Request(s):
(already merged - see related JIRA(s))
p2diff Report(s):
(will attach to JIRA when available)
----------
Please review the above changes, as they have been applied and are building today.
Once the target platform is built, jobs and parent pom will be updated to point
TARGET_PLATFORM_VERSION_MAX at the new version, 4.9.0.AM3-SNAPSHOT.
You can use the following to build & test the target platforms locally against
your component(s).
Build target-platform:
cd /path/to/jbosstools-target-platforms
git fetch origin pull/<pull-request-number>/head && git checkout FETCH_HEAD
# or, using hub for git
git checkout <pull-request-URL>
mvn clean install -f jbosstools/multiple/pom.xml
Then, to test the new multiple target platform against your component's build:
cd /path/to/your/jbosstools-component
mvn clean verify -Dtpc.version=4.9.0.AM3-SNAPSHOT -Dtpc.targetKind=multiple
For Central, fetch sources from jbosstools-discovery, then build as above.
----------
7 years, 6 months
ACTION REQUIRED: JBoss Tools + Developer Studio triage time
by nboldt＠redhat.com
As the current sprint 'devex #153 August 2018' draws to a close, it is time
to review your unresolved issues!
Some may be done (or will be done soon), but the JIRA(s) need resolution.
Others may need to be pushed to the next milestone (4.9.0.AM3 + 12.9.0.AM3),
to a future .x release, or LATER.
All unresolved issues for 4.9.0.AM2 + 12.9.0.AM2:
https://issues.jboss.org/issues/?jql=(project%20in%20(JBDS)%20AND%20fixVe...
All *YOUR* unresolved issues for 4.9.0.AM2 + 12.9.0.AM2:
https://issues.jboss.org/issues/?jql=(project%20in%20(JBDS)%20AND%20fixVe...
Once created, you can also begin scheduling your work for the upcoming
sprint, 'devex #154 September 2018'.
Triage tips:
* blocker/critical issues: make these your priority work for the next sprint:
move to next version & assign to the next sprint
* other issues that WILL be done in the next sprint:
move to next version & assign to the forthcoming sprint, but lower down
* non-blocker & non-critical issues not for the next sprint:
move to .x (or LATER)
7 years, 6 months
