July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24243) migrate Fuse Tools builds to JBT infrastructure/process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24243?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24243: ------------------------------- Fix Version/s: 4.5.1.AM1 (was: 4.5.0.Final) > migrate Fuse Tools builds to JBT infrastructure/process > ------------------------------------------------------- > > Key: JBIDE-24243 > URL: https://issues.jboss.org/browse/JBIDE-24243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, fusetools, updatesite > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > Fuse Tooling currently has jobs under this view: https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... > * https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/staging/builds/integration-stac... > ** https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/integration/updates/integration... > which publish integration, development or stable update sites. > As part of the migration of Fuse Tooling into JBoss Tools 4.5 for Oxygen, this path will change to something like: > * http://download.jboss.org/jbosstools/*oxygen*/snapshots/builds/fuse-tooling/ > * http://download.jboss.org/jbosstools/*oxygen*/staging/updates/fuse-tooling/ > We will also need to ensure that JBT composites/aggregates are configured to pick up these features/plugins. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22799) Create integration tests PR check job for server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22799?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22799: ------------------------------------ [~mmalina] noticed you had a bad path [0] in the pr itests job [1]. So I've fixed that... but I don't think we should be running long-process itests when we know they're going to fail [2]. Therefore I would suggest (again) that we either disable running the tests we know won't work (quick hack w/ pom orchestrator), fix the tests that don't work (which no one has time for(?)), or not run itests at all for PRs since we DO run them on commits [3] and have regular tests run for PRs, too [4]. [0] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [2] https://issues.jboss.org/browse/JBIDE-24763 [3] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [now set to run every Saturday some time between 00:00 and 07:00] [4] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Create integration tests PR check job for server > ------------------------------------------------ > > Key: JBIDE-22799 > URL: https://issues.jboss.org/browse/JBIDE-22799 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Martin Malina > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22799) Create integration tests PR check job for server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22799?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22799: ------------------------------------- Unless you want to help me get the itests passing, martin ;) Might require some actual coding / debugging though =P > Create integration tests PR check job for server > ------------------------------------------------ > > Key: JBIDE-22799 > URL: https://issues.jboss.org/browse/JBIDE-22799 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Martin Malina > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22799) Create integration tests PR check job for server

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22799?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22799: ------------------------------------- I'm not entirely sure itest job for PRs is necessary. They take 2 hours to run, and that could get pretty hefty. I vote no on this issue, unless Martin can give a good reason why this is necessary? At the very least I should make sure all itests pass before we even bother with this. Otherwise we're just adding noise. I'd push this to 'later' because a) it's not extremely necessary, 2) the itests are unstable, and 3) we already have an itest job. > Create integration tests PR check job for server > ------------------------------------------------ > > Key: JBIDE-22799 > URL: https://issues.jboss.org/browse/JBIDE-22799 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Martin Malina > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22799) Create integration tests PR check job for server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22799?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22799: ------------------------------------ Since some tests fail consistently (or I should say, don't pass consistently) I would propose removing them from the suite of itests run for all builds & PRs. Then we could have a second orchestrator pom that run these "itests-extras" ... which could be run locally when you're bored, did a big refactoring, or QE wants to have a bigger suite of itests for their weekly smoke tests. If you're interested in this approach, I'll create a new pom, update the itests/pom.xml [1] to remove the failing suites, & send you a PR for review. Then jobs can be updated to use either the all-itests/pom.xml (working tests) or the all-itests/extras-pom.xml (non-working tests). [1] https://github.com/jbosstools/jbosstools-server/blob/master/all-itests/po... WDYT? > Create integration tests PR check job for server > ------------------------------------------------ > > Key: JBIDE-22799 > URL: https://issues.jboss.org/browse/JBIDE-22799 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Martin Malina > Fix For: 4.5.0.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24763) Some server itests are failing on Jenkins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24763?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24763: ------------------------------- Fix Version/s: 4.5.x > Some server itests are failing on Jenkins > ----------------------------------------- > > Key: JBIDE-24763 > URL: https://issues.jboss.org/browse/JBIDE-24763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Fix For: 4.5.x > > > Here's the job: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Currently we got around 30 failures: > {code} > All Failed Tests > Test Name > Duration > Age > org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[1] 5.3 sec 1 > org.jboss.tools.as.management.itests.AS7ManagerIntegrationTest.canGetServerState[7] 76 ms 1 > org.jboss.tools.as.ui.bot.itests.parametized.server.RuntimeDetectionDuplicatesTest.duplicateRuntimes default [0] 17 sec 1 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[4] 1.7 sec 2 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[4] 5.3 sec 2 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[1] 2.3 sec 3 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[0] 4.4 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[1] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[2] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[3] 2.2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[4] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[5] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[6] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[7] 2.3 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[8] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[9] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[10] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[11] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[12] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[13] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[14] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[15] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[16] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[17] 2 sec 6 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[0] 1.7 sec 6 > org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [0] 1 min 49 sec 6 > org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [1] 1 min 43 sec 6 > org.jboss.tools.wtp.runtimes.tomcat.itests.ServerUtilTest.testUniqueServerName 2.6 sec 6 > org.jboss.tools.wtp.runtimes.tomcat.itests.TomcatDetectionTest.testTomcatDetection 0.13 sec 6 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[2] 1.7 sec 7 > {code} > Nick already shared some details in JBIDE-22799 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24763) Some server itests are failing on Jenkins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24763?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24763: ---------------------------------- Assignee: Rob Stryker > Some server itests are failing on Jenkins > ----------------------------------------- > > Key: JBIDE-24763 > URL: https://issues.jboss.org/browse/JBIDE-24763 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.x > > > Here's the job: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Currently we got around 30 failures: > {code} > All Failed Tests > Test Name > Duration > Age > org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[1] 5.3 sec 1 > org.jboss.tools.as.management.itests.AS7ManagerIntegrationTest.canGetServerState[7] 76 ms 1 > org.jboss.tools.as.ui.bot.itests.parametized.server.RuntimeDetectionDuplicatesTest.duplicateRuntimes default [0] 17 sec 1 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[4] 1.7 sec 2 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFolderTest.testSingleDeployableFolder[4] 5.3 sec 2 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[1] 2.3 sec 3 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[0] 4.4 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[1] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[2] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[3] 2.2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[4] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[5] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[6] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[7] 2.3 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[8] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[9] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[10] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[11] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[12] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[13] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[14] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[15] 2.1 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[16] 2 sec 6 > org.jboss.tools.as.itests.ProjectRuntimeClasspathTest.testProjectRuntime[17] 2 sec 6 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[0] 1.7 sec 6 > org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [0] 1 min 49 sec 6 > org.jboss.tools.as.ui.bot.itests.parametized.server.ServerRuntimesTest.operateDeploy default [1] 1 min 43 sec 6 > org.jboss.tools.wtp.runtimes.tomcat.itests.ServerUtilTest.testUniqueServerName 2.6 sec 6 > org.jboss.tools.wtp.runtimes.tomcat.itests.TomcatDetectionTest.testTomcatDetection 0.13 sec 6 > org.jboss.tools.as.itests.server.publishing.SingleDeployableFileTest.testSingleDeployableFullPublish[2] 1.7 sec 7 > {code} > Nick already shared some details in JBIDE-22799 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20024) Problems with new Eclipse Marketplace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20024?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20024. ------------------------------ Resolution: Done Since 4 of the 5 issues linked from here are done or wontfix, I'm going to close this. Remaining issue is: Need an api to load IUs / copy from one solution to another - https://bugs.eclipse.org/bugs/show_bug.cgi?id=46986 As this has been untouched for over a year, and only bugs me ONCE a year, I'm inclined to no longer GAF. > Problems with new Eclipse Marketplace > ------------------------------------- > > Key: JBIDE-20024 > URL: https://issues.jboss.org/browse/JBIDE-20024 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > Attachments: spring-marketplace-different-updates.png > > > New Eclipse Marketplace problems: > * *WONTFIX* all features can't be optional - must have at least one required one - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469864 > * *WONTFIX* default config shows all versions of Eclipse, not latest (have to update Luna entries to show ONLY Luna compatibility) - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469869 > * *FIXED* "Add new solution version" doesn't work - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469865 > * *FIXED* 'Edit Solution' shows the same grey footnote text dozens of times - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469862 > * * Need an api to load IUs / copy from one solution to another - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469867 (untouched for over a year) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20024) Problems with new Eclipse Marketplace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20024?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20024: ------------------------------- Description: New Eclipse Marketplace problems: * *WONTFIX* all features can't be optional - must have at least one required one - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469864 * *WONTFIX* default config shows all versions of Eclipse, not latest (have to update Luna entries to show ONLY Luna compatibility) - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469869 * *FIXED* "Add new solution version" doesn't work - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469865 * *FIXED* 'Edit Solution' shows the same grey footnote text dozens of times - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469862 * * Need an api to load IUs / copy from one solution to another - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469867 (untouched for over a year) was: New Eclipse Marketplace problems: * all features can't be optional - must have at least one required one - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469864 * *WONTFIX* default config shows all versions of Eclipse, not latest (have to update Luna entries to show ONLY Luna compatibility) - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469869 * "Add new solution version" doesn't work - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469865 * Need an api to load IUs / copy from one solution to another - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469867 * 'Edit Solution' shows the same grey footnote text dozens of times - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469862 > Problems with new Eclipse Marketplace > ------------------------------------- > > Key: JBIDE-20024 > URL: https://issues.jboss.org/browse/JBIDE-20024 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > Attachments: spring-marketplace-different-updates.png > > > New Eclipse Marketplace problems: > * *WONTFIX* all features can't be optional - must have at least one required one - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469864 > * *WONTFIX* default config shows all versions of Eclipse, not latest (have to update Luna entries to show ONLY Luna compatibility) - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469869 > * *FIXED* "Add new solution version" doesn't work - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469865 > * *FIXED* 'Edit Solution' shows the same grey footnote text dozens of times - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469862 > * * Need an api to load IUs / copy from one solution to another - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469867 (untouched for over a year) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20024) Problems with new Eclipse Marketplace

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20024?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20024: ------------------------------- Fix Version/s: 4.5.0.Final (was: LATER) > Problems with new Eclipse Marketplace > ------------------------------------- > > Key: JBIDE-20024 > URL: https://issues.jboss.org/browse/JBIDE-20024 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > Attachments: spring-marketplace-different-updates.png > > > New Eclipse Marketplace problems: > * *WONTFIX* all features can't be optional - must have at least one required one - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469864 > * *WONTFIX* default config shows all versions of Eclipse, not latest (have to update Luna entries to show ONLY Luna compatibility) - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469869 > * *FIXED* "Add new solution version" doesn't work - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469865 > * *FIXED* 'Edit Solution' shows the same grey footnote text dozens of times - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469862 > * * Need an api to load IUs / copy from one solution to another - https://bugs.eclipse.org/bugs/show_bug.cgi?id=469867 (untouched for over a year) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2017