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, 4 days
ACTION REQUIRED: test-drive Tycho 0.23.0
by Nick Boldt
Soon, Tycho 0.23.0 will be available.
If possible, I'd like to build JBT 4.3.0.Beta1 / JBDS 9.0.0.Beta1 using
Tycho 0.23.0.
If you add the code below to your settings.xml, then build with
-DtychoVersion=0.23.0, you'll be able to see if anything breaks w/ Tycho
0.23.0.
If it does, please open a JIRA.
Thanks!
-------- Forwarded Message --------
Subject: [tycho-user] Tycho 0.23.0 staged
Date: Thu, 28 May 2015 16:07:55 +0000
From: Sievers, Jan <jan.sievers(a)sap.com>
Reply-To: Tycho user list <tycho-user(a)eclipse.org>
To: Tycho user list (tycho-user(a)eclipse.org) <tycho-user(a)eclipse.org>
CC: Tycho developers list (tycho-dev(a)eclipse.org) <tycho-dev(a)eclipse.org>
Tycho milestone release 0.23.0 has been staged.
For details of new features and bugfixes, see release notes [1].
Please help by testing the staged milestone build. To use it, change
your tycho version to 0.23.0 and add snippet [2] to your pom.
NOTE: if you build products for MacOSX against p2 repositories older
than eclipse Mars, there is a known bug [3]
We plan to promote this release in one week unless major regressions are
found.
Regards,
Tycho team
[1] http://wiki.eclipse.org/Tycho/Release_Notes/0.23
[2]
<pluginRepositories>
<pluginRepository>
<id>tycho-staged</id>
<url>https://oss.sonatype.org/content/repositories/orgeclipsetycho-1021/</url>
</pluginRepository>
</pluginRepositories>
[3] https://wiki.eclipse.org/Tycho/Release_Notes/0.23#p2
_______________________________________________
tycho-user mailing list
tycho-user(a)eclipse.org
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/tycho-user
10 years, 8 months
Jira Pullrequest workflow improvements
by Max Rydahl Andersen
Hi,
Just to let all know that JBIDE and JBDS (and all other projects using
git PR workflow
or CDW v1) on jira have had a nice change[1] in behaviour yesterday.
For a while now you had to manually set the pull request status by
attaching git pull requests into the field.
Now as can see on JBIDE-19857[2] this status change happens
automatically when jira detects a PR with proper jira reference and it
shows up in the Development section of jira.
The upside here is you don't have to set that status and we can now
query on "pull request sent",
downside is that it does take jira 30 minutes or so to notice it.
Thus if it is urgent you get the PR noticed then the old way is still to
be preferred.
[1] https://issues.jboss.org/browse/ORG-2458
[2]
https://issues.jboss.org/browse/JBIDE-19857?page=com.atlassian.jira.plugi...
/max
http://about.me/maxandersen
10 years, 9 months
REMINDER: JBT 4.3 / JBDS 9.0 Beta1 Code Freeze is next week!
by Nick Boldt
Reminder of upcoming dates:
2015/05/28: Mars RC2 EPP bundles available
2015/06/03: 4.50.0.Beta1 target platform release day
2015/06/04: 4.3.0.Beta1 / 9.0.0.Beta1 code freeze day
2015/06/04: 4.3.0.Beta1 / 9.0.0.Beta1 N&N complete day
2015/06/05: 4.3.0.Beta1 / 9.0.0.Beta1 build day
PLEASE NOTE: I'd like to get the QE staging done on *Friday* instead of
the weekend, if possible.
2015/06/08: 4.3.0.Beta1 / 9.0.0.Beta1 QE / testing begins
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
10 years, 9 months
Who would I ping for new sysprop to all runtime installer jars?
by Rob Stryker
https://issues.jboss.org/browse/JBIDE-19852
When using dl-runtimes to install DV or FSW, it runs the installer jar.
The installer jar does not respect the installation path the user set in
the dl-runtimes wizard. It can't, obviously, bc we never transmit it to
the installer at all.
It'd be great if we could agree on some sysprop we can set when running
java -jar dv-6.1-installer.jar such that the installer checks it for a
default installation folder.
Any ideas who I would ping over getting something like that implemented
on the runtimes side?
- Rob Stryker
10 years, 9 months
