February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23889) jbosstools-composite-install_master sends lots of nag emails when something goes awry (as it should)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23889?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-23889. ------------------------------------ Resolution: Done Build #27718 took place on Feb 8th, and job has looped failing at very high frequency (several times per minutes whereas expectation is every 30 minutes) for at least 2 days, until Build #29675. That is about ~2000 builds in two days. But it seems that the delay of 30 minutes is working properly again, so this issue seems fixed magically. > jbosstools-composite-install_master sends lots of nag emails when something goes awry (as it should) > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-23889 > URL: https://issues.jboss.org/browse/JBIDE-23889 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.4.4.AM1 > > Attachments: composite.png > > > jbosstools-composite-install_master re-runs itself on failure. However, it seems like the SLEEP_TIME parameter is now ignored, resulting on constant re-run of the job and a lot of spam (multiple mails per minutes). Additionally to spam, this adds a relatively big load on Jenkins and slaves queue. > I've removed the re-run on failure block of the downstream job trigger as a temporary workaround. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24014) org.jboss.tools.foundation.core: Version has not incremented in 4.4.x and master branches

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24014?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24014 at 2/28/17 2:34 PM: ------------------------------------------------------------- Pull request (master): https://github.com/jbosstools/jbosstools-base/pull/557 Pull request (4.4.x): https://github.com/jbosstools/jbosstools-base/pull/558 was (Author: nickboldt): Pull request: https://github.com/jbosstools/jbosstools-base/pull/557 > org.jboss.tools.foundation.core: Version has not incremented in 4.4.x and master branches > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24014 > URL: https://issues.jboss.org/browse/JBIDE-24014 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: foundation > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.5.0.AM1 > > > {code} > 02:23:37 [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines (default) on project org.jboss.tools.foundation.core: Version have moved backwards for (org.jboss.tools.foundation.core/1.3.3.AM1-v20170224-0218-B1387). Baseline has 1.3.3.Final-v20170217-0505-B33) with delta: 0.0.0 -> [Help 1] > {code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > Solution: upversion your plugin(s)/feature(s) to a new version in 4.4.x and master branches. > Perhaps you want 1.3.4 in 4.4.x branch, and 1.3.100 in the master branch? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24014) org.jboss.tools.foundation.core: Version has not incremented in 4.4.x and master branches

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24014?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24014: ---------------------------------- Assignee: Jeff MAURY (was: Rob Stryker) > org.jboss.tools.foundation.core: Version has not incremented in 4.4.x and master branches > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24014 > URL: https://issues.jboss.org/browse/JBIDE-24014 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: foundation > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 4.5.0.AM1 > > > {code} > 02:23:37 [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines (default) on project org.jboss.tools.foundation.core: Version have moved backwards for (org.jboss.tools.foundation.core/1.3.3.AM1-v20170224-0218-B1387). Baseline has 1.3.3.Final-v20170217-0505-B33) with delta: 0.0.0 -> [Help 1] > {code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > Solution: upversion your plugin(s)/feature(s) to a new version in 4.4.x and master branches. > Perhaps you want 1.3.4 in 4.4.x branch, and 1.3.100 in the master branch? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24014) org.jboss.tools.foundation.core: Version has not incremented in 4.4.x and master branches

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24014?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24014: ------------------------------------ Pull request: https://github.com/jbosstools/jbosstools-base/pull/557 > org.jboss.tools.foundation.core: Version has not incremented in 4.4.x and master branches > ----------------------------------------------------------------------------------------- > > Key: JBIDE-24014 > URL: https://issues.jboss.org/browse/JBIDE-24014 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: foundation > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.5.0.AM1 > > > {code} > 02:23:37 [ERROR] Failed to execute goal org.eclipse.tycho.extras:tycho-p2-extras-plugin:1.0.0:compare-version-with-baselines (default) on project org.jboss.tools.foundation.core: Version have moved backwards for (org.jboss.tools.foundation.core/1.3.3.AM1-v20170224-0218-B1387). Baseline has 1.3.3.Final-v20170217-0505-B33) with delta: 0.0.0 -> [Help 1] > {code} -- https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > Solution: upversion your plugin(s)/feature(s) to a new version in 4.4.x and master branches. > Perhaps you want 1.3.4 in 4.4.x branch, and 1.3.100 in the master branch? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23652) coretests composite site not updated when publishing to /static and /stable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23652?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23652 at 2/28/17 2:18 PM: ------------------------------------------------------------- Same problem in * http://download.jboss.org/jbosstools/static/neon/stable/updates/core/ (points to ../, which has no composite pointer to latest - need to copy same composite*.xml from non-static path here) * http://download.jboss.org/jbosstools/static/neon/stable/updates/central/ (no composite) * http://download.jboss.org/jbosstools/static/neon/stable/updates/earlyaccess/ (no composite) * https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/ (composite out of date) Should have unchanging composites here, too: * http://download.jboss.org/jbosstools/neon/stable/updates/earlyaccess/ (should point to equivalent /static path) * http://download.jboss.org/jbosstools/neon/stable/updates/central/ (should point to equivalent /static path) * http://download.jboss.org/jbosstools/neon/development/updates/integration... (should point to /static path) Need to update staging script [1] and re-run it via Jenkins job [2] to verify fixed. [1] https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-releng-pu... was (Author: nickboldt): Same problem in * http://download.jboss.org/jbosstools/static/neon/stable/updates/core/ (points to ../, which has no composite pointer to latest - need to copy same composite*.xml from non-static path here) * http://download.jboss.org/jbosstools/static/neon/stable/updates/central/ (no composite) * http://download.jboss.org/jbosstools/static/neon/stable/updates/earlyaccess/ (no composite) Should have unchanging composites here, too: * http://download.jboss.org/jbosstools/neon/stable/updates/earlyaccess/ (should point to equivalent /static path) * http://download.jboss.org/jbosstools/neon/stable/updates/central/ (should point to equivalent /static path) * http://download.jboss.org/jbosstools/neon/development/updates/integration... (should point to /static path) Need to update staging script [1] and re-run it via Jenkins job [2] to verify fixed. [1] https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/p... [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-releng-pu... > coretests composite site not updated when publishing to /static and /stable > --------------------------------------------------------------------------- > > Key: JBIDE-23652 > URL: https://issues.jboss.org/browse/JBIDE-23652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Labels: releasework > Fix For: 4.4.4.AM1 > > > Realized the other day that the composite*.xml files in http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ and http://download.jboss.org/jbosstools/neon/stable/updates/coretests/ were not updated after 4.4.0.Alpha1... and probably should be part of what's updated when we release to /development, /stable, /static, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23652) coretests composite site not updated when publishing to /static and /stable

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23652?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23652: ------------------------------------ And it seems that while this is updated and accurate [1], this is not [2]. [1] https://devstudio.redhat.com/static/10.0/stable/updates/discovery.earlyac... [2] https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/10... So, we need to ensure that BOTH places are updated when running the merge script. [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Job updated to merge IS content to /static/ and non-static URLs. Additional problem: https://devstudio.redhat.com/10.0/stable/updates/discovery.earlyaccess/co... not updated correctly - contains 10.3 and the 4.61 TP. > coretests composite site not updated when publishing to /static and /stable > --------------------------------------------------------------------------- > > Key: JBIDE-23652 > URL: https://issues.jboss.org/browse/JBIDE-23652 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Labels: releasework > Fix For: 4.4.4.AM1 > > > Realized the other day that the composite*.xml files in http://download.jboss.org/jbosstools/static/neon/stable/updates/coretests/ and http://download.jboss.org/jbosstools/neon/stable/updates/coretests/ were not updated after 4.4.0.Alpha1... and probably should be part of what's updated when we release to /development, /stable, /static, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24019) test failures in webservices

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24019?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24019: ------------------------------- Description: See https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... When I run the same build locally (`mvn clean install`), I get null pointers - and they're not all related to ancient JRE5 tests. See attached: [^org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt] Running again now with {code}mvn clean install -Djbosstools.test.jre.5=${JAVA_HOME} -Djbosstools.test.jre.6=${JAVA_HOME} \ -Djbosstools.test.jre.7=${JAVA_HOME} -Djbosstools.test.jre.8=${JAVA_HOME}{code} See attached: [^org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite_v2.txt] and [^.log] Could the problem be this? {code}!ENTRY org.eclipse.wst.common.project.facet.core 4 0 2017-02-28 11:14:37.082 !MESSAGE Project facet wst.jsdt.web has not been defined. It is used in plugin org.eclipse.jst.server.core. {code} (Wondering if we ought to update the parent pom to have smart defaults for these jbosstools.test.jre.* variables. WDYT? see JBIDE-24020) was: See https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... When I run the same build locally (`mvn clean install`), I get null pointers - and they're not all related to ancient JRE5 tests. See attached: [^org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt] Running again now with {code}mvn clean install -Djbosstools.test.jre.5=${JAVA_HOME} -Djbosstools.test.jre.6=${JAVA_HOME} \ -Djbosstools.test.jre.7=${JAVA_HOME} -Djbosstools.test.jre.8=${JAVA_HOME}{code} See attached: [^org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite_v2.txt] and [^.log] (Wondering if we ought to update the parent pom to have smart defaults for these jbosstools.test.jre.* variables. WDYT? see JBIDE-24020) > test failures in webservices > ---------------------------- > > Key: JBIDE-24019 > URL: https://issues.jboss.org/browse/JBIDE-24019 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.0.AM1 > > Attachments: .log, org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt, org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite_v2.txt > > > See https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > When I run the same build locally (`mvn clean install`), I get null pointers - and they're not all related to ancient JRE5 tests. > See attached: [^org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt] > Running again now with {code}mvn clean install -Djbosstools.test.jre.5=${JAVA_HOME} -Djbosstools.test.jre.6=${JAVA_HOME} \ > -Djbosstools.test.jre.7=${JAVA_HOME} -Djbosstools.test.jre.8=${JAVA_HOME}{code} > See attached: [^org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite_v2.txt] and [^.log] > Could the problem be this? > {code}!ENTRY org.eclipse.wst.common.project.facet.core 4 0 2017-02-28 11:14:37.082 > !MESSAGE Project facet wst.jsdt.web has not been defined. It is used in plugin org.eclipse.jst.server.core. > {code} > (Wondering if we ought to update the parent pom to have smart defaults for these jbosstools.test.jre.* variables. WDYT? see JBIDE-24020) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24020) set better defaults for jbosstools.test.jre.* in parent pom?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24020?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24020: ---------------------------------- Assignee: Jeff MAURY > set better defaults for jbosstools.test.jre.* in parent pom? > ------------------------------------------------------------ > > Key: JBIDE-24020 > URL: https://issues.jboss.org/browse/JBIDE-24020 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.0.AM1 > > > A few builds, such as jbosstools-server and jbosstools-webservices, rely on some ancient JREs which are not actually available on the machines on which builds or tests are run. > These JREs are defined in the parent pom here: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > Then in Jenkins, the actual paths are defined. > But to run locally & not have tests fail, you therefore need set these via commandline or in your settings.xml file. > So, why not set a better default that works on Windows/Linux/MacOS? How about this? > {code} > -Djbosstools.test.jre.5=${JAVA_HOME} > -Djbosstools.test.jre.6=${JAVA_HOME} > -Djbosstools.test.jre.7=${JAVA_HOME} > -Djbosstools.test.jre.8=${JAVA_HOME}{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24020) set better defaults for jbosstools.test.jre.* in parent pom?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24020?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24020: ------------------------------- Fix Version/s: 4.5.0.AM1 > set better defaults for jbosstools.test.jre.* in parent pom? > ------------------------------------------------------------ > > Key: JBIDE-24020 > URL: https://issues.jboss.org/browse/JBIDE-24020 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.0.AM1 > > > A few builds, such as jbosstools-server and jbosstools-webservices, rely on some ancient JREs which are not actually available on the machines on which builds or tests are run. > These JREs are defined in the parent pom here: > https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... > Then in Jenkins, the actual paths are defined. > But to run locally & not have tests fail, you therefore need set these via commandline or in your settings.xml file. > So, why not set a better default that works on Windows/Linux/MacOS? How about this? > {code} > -Djbosstools.test.jre.5=${JAVA_HOME} > -Djbosstools.test.jre.6=${JAVA_HOME} > -Djbosstools.test.jre.7=${JAVA_HOME} > -Djbosstools.test.jre.8=${JAVA_HOME}{code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24019) test failures in webservices

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24019?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24019: ------------------------------- Attachment: .log > test failures in webservices > ---------------------------- > > Key: JBIDE-24019 > URL: https://issues.jboss.org/browse/JBIDE-24019 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Fix For: 4.5.0.AM1 > > Attachments: .log, org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt, org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite_v2.txt > > > See https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/DevStudio/view/... > When I run the same build locally (`mvn clean install`), I get null pointers - and they're not all related to ancient JRE5 tests. > See attached: [^org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite.txt] > Running again now with {code}mvn clean install -Djbosstools.test.jre.5=${JAVA_HOME} -Djbosstools.test.jre.6=${JAVA_HOME} \ > -Djbosstools.test.jre.7=${JAVA_HOME} -Djbosstools.test.jre.8=${JAVA_HOME}{code} > See attached: [^org.jboss.tools.ws.creation.core.test.JBossWSCreationCoreTestSuite_v2.txt] > (Wondering if we ought to update the parent pom to have smart defaults for these jbosstools.test.jre.* variables. WDYT? see JBIDE-24020) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

7 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2017