Just a reminder that if you're getting notifications from Jenkins that your
build is red, *you need to take ownership* of that and solve the issue. You
should be seeing the same build problems locally, so it's easy enough to
increment your plugins and features to x.y.(z+1) to resolve the baseline
comparison check failure.
If the problem is/was some cryptic error about source features finding the
wrong version of source plugin, that should be fixed after moving from
Tycho 0.26 -> Tycho 1.0. Ref:
https://issues.jboss.org/browse/JBIDE-23212
If you need help, feel free to ping me.
Note that I'm on PTO from Mar 3-12, so the window for help is closing soon.
:D
Cheers,
Nick
On Thu, Feb 23, 2017 at 2:43 PM, Nick Boldt <nboldt(a)redhat.com> wrote:
Since QE signed off on the 4.4.3.Final/10.3.0.GA bits a couple days
ago, the _4.4.neon and _10.0.neon jobs are now being run against the
jbosstools-4.4.x branches.
These jobs are for now using the Neon.2 target platform
(4.62.0.Final), but will be updated to Neon.3 once RC4 is available in
a couple weeks.
Should you need us to move up faster to Neon.3, please ask for such a
change here:
https://issues.jboss.org/browse/JBIDE-23963
Jobs can be found here:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devst...
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com