February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-22625) Remote server with FS operations: Unable to retrieve a list of remote deployment scanners

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22625?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22625: -------------------------------- Fix Version/s: 4.5.0.AM1 > Remote server with FS operations: Unable to retrieve a list of remote deployment scanners > ----------------------------------------------------------------------------------------- > > Key: JBIDE-22625 > URL: https://issues.jboss.org/browse/JBIDE-22625 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > Previously I reported this as part of JBIDE-22605, but I think it deserves its own issue. > When I setup a remote EAP 7 server with FS operations and then start it, I always get this in the error log: > Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 7.0 > Today, I also noticed this info message in the error view: > org.eclipse.rse.core > Saved passwords are not available for migration to secure storage. Deprecated authorization classes (org.eclipse.core.runtime.compatibility.auth) are not installed. > I wonder if this is related? Do we require authentication to get the list of deployment scanners? > BTW, org.eclipse.core.runtime.compatibility was removed in JBIDE-21382 and I suggested org.eclipse.core.runtime.compatibility.auth may be removed too - JBIDE-22602. But as of now it's still in the TP. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22605) Remote server with fs operations sometimes cannot be stopped

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22605?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22605: -------------------------------- Fix Version/s: 4.5.0.AM1 > Remote server with fs operations sometimes cannot be stopped > ------------------------------------------------------------ > > Key: JBIDE-22605 > URL: https://issues.jboss.org/browse/JBIDE-22605 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > Yesterday when we were found out that remote servers don't work with management operations (JBIDE-22601) I wanted to check if at least FS operations work. > In one instance of Eclipse, stopping such server didn't work. > But then I tried in devstudio and it worked, so I assumed it was some glitch. > But today this happened to me again with the latest devstudio 10.0.0.GA B30 build - the one that contains a fix to the above mentioned JIRA. > From several attempts, it seems that this is only reproducible if you deploy a project. If you just start the server and then stop, it will stop just fine. > One more thing, regardless of whether a given server can be stopped or not, I always get this in the Error Log view during server startup: > {code}Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 7.0 marvin{code} > (Let me know if you want an additional JIRA for that.) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23571) Integration tests global refactoring: org.jboss.tools.arquillian.ui.bot.test

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23571?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-23571: ---------------------------------- Fix Version/s: 4.4.x (was: 4.4.3.AM2) > Integration tests global refactoring: org.jboss.tools.arquillian.ui.bot.test > ---------------------------------------------------------------------------- > > Key: JBIDE-23571 > URL: https://issues.jboss.org/browse/JBIDE-23571 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: arquillian > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Labels: arquillian, integration, integration-test > Fix For: 4.4.x > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.arquillian.ui.bot.test -DskipTests=false > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23733 at 2/1/17 2:36 PM: ------------------------------------------------------------ well, we're close! but not quite there yet. Here are some questions/concerns with the naming convention of jobs in the view: 1. There is an archives.it.weekly but no .smoke job. Should there be one of each? Or should the weekly job be included in the devstudio.buildflow.it.smoke config? 2. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is called .it.full -- what about .it.smoke and .it.weekly? 3. What's with this mystery job? https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Rename or delete? 4. cdi.it.smoke but no weekly... why do we need two jobs for cdi10.weekly and cdi11.weekly? Could they be merged? Or at least named consistently as .it.weekly? 5. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .smoke 6. central.it.smoke but no .weekly 7. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .it.smoke or .it.weekly 8. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .it.smoke or .it.weekly 9. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .weekly Thanks! (Note that I've also opened JBIDE-23835 to discuss why all the .it.smoke tests are failing or aborted.) was (Author: nickboldt): well, we're close! but not quite there yet. Here are some questions/concerns with the naming convention of jobs in the view: 1. There is an archives.it.weekly but no .smoke job. Should there be one of each? Or should the weekly job be included in the devstudio.buildflow.it.smoke config? 2. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is called .it.full -- what about .it.smoke and .it.weekly? 3. What's with this mystery job? https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Rename or delete? 4. cdi.it.smoke but no weekly... why do we need two jobs for cdi10.weekly and cdi11.weekly? Could they be merged? Or at least named consistently as .it.weekly? 5. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .smoke 6. central.it.smoke but no .weekly 7. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .it.smoke or .it.weekly 8. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .it.smoke or .it.weekly 9. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .weekly Thanks! > Merge .smoke and .nightly integration jobs into a single job and run them weekly > -------------------------------------------------------------------------------- > > Key: JBIDE-23733 > URL: https://issues.jboss.org/browse/JBIDE-23733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.4.3.Final > > Attachments: Screenshot from 2017-01-31 17-09-00.png > > > Purpose: > a) easier maintenance of jobs / tests > b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests > c) more frequent full integration runs (rather than once per sprint, once per week) > Tests to run as smoke tests are in this buildflow job: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Tests to merge are in this view: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23835) jbosstools .it.smoke tests fail, abort, or are unstable.

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-23835: ---------------------------------- Summary: jbosstools .it.smoke tests fail, abort, or are unstable. Key: JBIDE-23835 URL: https://issues.jboss.org/browse/JBIDE-23835 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration-tests Affects Versions: 4.4.3.Final Reporter: Nick Boldt All of the .it.smoke tests listed in this buildflow job [1] result in either an unstable build, a failed build, or an aborted build. [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... We need to get these jobs to green or they're meaningless as a measurement tool at the end of every sprint. {code}aerogear.it.smoke #14 completed: UNSTABLE batch.it.smoke #2 completed: FAILURE browsersim.it.smoke #15 completed: FAILURE cdi.it.smoke #15 completed: FAILURE cdk.devstudio.it.smoke #2 completed: UNSTABLE central.it.smoke #184 completed: FAILURE docker.it.smoke #192 completed: UNSTABLE examples.javaee.it.smoke #30 completed: FAILURE forge.it.smoke #24 completed: ABORTED freemarker.it.smoke #3 completed: ABORTED hibernate.it.smoke #18 completed: ABORTED jax-rs.it.smoke #5 completed: ABORTED jax-ws.it.smoke #5 completed: ABORTED jsf.it.smoke #3 completed: FAILURE jst.it.smoke #42 completed: FAILURE livereload.it.smoke #8 completed: FAILURE maven.it.smoke #33 completed: FAILURE vpe.it.smoke #7 completed: FAILURE websocket.it.smoke #4 completed: FAILURE {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23835) jbosstools .it.smoke tests fail, abort, or are unstable.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23835?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23835: ---------------------------------- Assignee: Rastislav Wagner > jbosstools .it.smoke tests fail, abort, or are unstable. > -------------------------------------------------------- > > Key: JBIDE-23835 > URL: https://issues.jboss.org/browse/JBIDE-23835 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.4.3.Final > Reporter: Nick Boldt > Assignee: Rastislav Wagner > > All of the .it.smoke tests listed in this buildflow job [1] result in either an unstable build, a failed build, or an aborted build. > [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > We need to get these jobs to green or they're meaningless as a measurement tool at the end of every sprint. > {code}aerogear.it.smoke #14 completed: UNSTABLE > batch.it.smoke #2 completed: FAILURE > browsersim.it.smoke #15 completed: FAILURE > cdi.it.smoke #15 completed: FAILURE > cdk.devstudio.it.smoke #2 completed: UNSTABLE > central.it.smoke #184 completed: FAILURE > docker.it.smoke #192 completed: UNSTABLE > examples.javaee.it.smoke #30 completed: FAILURE > forge.it.smoke #24 completed: ABORTED > freemarker.it.smoke #3 completed: ABORTED > hibernate.it.smoke #18 completed: ABORTED > jax-rs.it.smoke #5 completed: ABORTED > jax-ws.it.smoke #5 completed: ABORTED > jsf.it.smoke #3 completed: FAILURE > jst.it.smoke #42 completed: FAILURE > livereload.it.smoke #8 completed: FAILURE > maven.it.smoke #33 completed: FAILURE > vpe.it.smoke #7 completed: FAILURE > websocket.it.smoke #4 completed: FAILURE > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-23733 at 2/1/17 2:30 PM: ------------------------------------------------------------ well, we're close! but not quite there yet. Here are some questions/concerns with the naming convention of jobs in the view: 1. There is an archives.it.weekly but no .smoke job. Should there be one of each? Or should the weekly job be included in the devstudio.buildflow.it.smoke config? 2. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is called .it.full -- what about .it.smoke and .it.weekly? 3. What's with this mystery job? https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Rename or delete? 4. cdi.it.smoke but no weekly... why do we need two jobs for cdi10.weekly and cdi11.weekly? Could they be merged? Or at least named consistently as .it.weekly? 5. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .smoke 6. central.it.smoke but no .weekly 7. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .it.smoke or .it.weekly 8. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .it.smoke or .it.weekly 9. https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .weekly Thanks! was (Author: nickboldt): well, we're close! but not quite there yet. Here are some questions/concerns with the naming convention of jobs in the view: # There is an archives.it.weekly but no .smoke job. Should there be one of each? Or should the weekly job be included in the devstudio.buildflow.it.smoke config? # https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is called .it.full -- what about .it.smoke and .it.weekly? # What's with this mystery job? https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Rename or delete? # cdi.it.smoke but no weekly... why do we need two jobs for cdi10.weekly and cdi11.weekly? Could they be merged? Or at least named consistently as .it.weekly? # https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .smoke # central.it.smoke but no .weekly # https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .it.smoke or .it.weekly # https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .it.smoke or .it.weekly # https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .weekly Thanks! > Merge .smoke and .nightly integration jobs into a single job and run them weekly > -------------------------------------------------------------------------------- > > Key: JBIDE-23733 > URL: https://issues.jboss.org/browse/JBIDE-23733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.4.3.Final > > Attachments: Screenshot from 2017-01-31 17-09-00.png > > > Purpose: > a) easier maintenance of jobs / tests > b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests > c) more frequent full integration runs (rather than once per sprint, once per week) > Tests to run as smoke tests are in this buildflow job: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Tests to merge are in this view: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23733: ------------------------------------ well, we're close! but not quite there yet. Here are some questions/concerns with the naming convention of jobs in the view: # There is an archives.it.weekly but no .smoke job. Should there be one of each? Or should the weekly job be included in the devstudio.buildflow.it.smoke config? # https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... is called .it.full -- what about .it.smoke and .it.weekly? # What's with this mystery job? https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Rename or delete? # cdi.it.smoke but no weekly... why do we need two jobs for cdi10.weekly and cdi11.weekly? Could they be merged? Or at least named consistently as .it.weekly? # https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .smoke # central.it.smoke but no .weekly # https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .it.smoke or .it.weekly # https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .it.smoke or .it.weekly # https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... but no .weekly Thanks! > Merge .smoke and .nightly integration jobs into a single job and run them weekly > -------------------------------------------------------------------------------- > > Key: JBIDE-23733 > URL: https://issues.jboss.org/browse/JBIDE-23733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.4.3.Final > > Attachments: Screenshot from 2017-01-31 17-09-00.png > > > Purpose: > a) easier maintenance of jobs / tests > b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests > c) more frequent full integration runs (rather than once per sprint, once per week) > Tests to run as smoke tests are in this buildflow job: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Tests to merge are in this view: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23733) Merge .smoke and .nightly integration jobs into a single job and run them weekly

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23733?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23733: ------------------------------- Description: Purpose: a) easier maintenance of jobs / tests b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests c) more frequent full integration runs (rather than once per sprint, once per week) Tests to run as smoke tests are in this buildflow job: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... Tests to merge are in this view: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... was: Purpose: a) easier maintenance of jobs / tests b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests c) more frequent full integration runs (rather than once per sprint, once per week) Tests to merge are in this view: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Merge .smoke and .nightly integration jobs into a single job and run them weekly > -------------------------------------------------------------------------------- > > Key: JBIDE-23733 > URL: https://issues.jboss.org/browse/JBIDE-23733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, integration-tests > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Rastislav Wagner > Fix For: 4.4.3.Final > > Attachments: Screenshot from 2017-01-31 17-09-00.png > > > Purpose: > a) easier maintenance of jobs / tests > b) run fewer nightly jobs so that we don't block slaves from being available for other builds / tests > c) more frequent full integration runs (rather than once per sprint, once per week) > Tests to run as smoke tests are in this buildflow job: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > Tests to merge are in this view: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23677) write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23677?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23677: ---------------------------------- Assignee: Nick Boldt (was: Fred Bricon) Resolution: Done Done. > write maven enforcer test to ensure we set correct version of foundation.core (based on parent pom version) > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23677 > URL: https://issues.jboss.org/browse/JBIDE-23677 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, foundation > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.Final > > > Wrong version of foundation.core detected. Should be 4.4.3, not 4.4.2. > https://github.com/jbosstools/jbosstools-base/blob/master/foundation/plug... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 February 2017