January 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23737) Integration test: if symlink to oc exists, but target isnt, OpenShiftCommandLineToolsRequirement is failing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23737?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23737: ------------------------------------- Labels: integration_tests (was: ) > Integration test: if symlink to oc exists, but target isnt, OpenShiftCommandLineToolsRequirement is failing > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23737 > URL: https://issues.jboss.org/browse/JBIDE-23737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.3.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23737) Integration test: if symlink to oc exists, but target isnt, OpenShiftCommandLineToolsRequirement is failing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23737?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-23737. ------------------------------------ > Integration test: if symlink to oc exists, but target isnt, OpenShiftCommandLineToolsRequirement is failing > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23737 > URL: https://issues.jboss.org/browse/JBIDE-23737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.3.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23737) Integration test: if symlink to oc exists, but target isnt, OpenShiftCommandLineToolsRequirement is failing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23737?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23737: ------------------------------------------ PR was reviewed by QE, closing. > Integration test: if symlink to oc exists, but target isnt, OpenShiftCommandLineToolsRequirement is failing > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23737 > URL: https://issues.jboss.org/browse/JBIDE-23737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: integration_tests > Fix For: 4.4.3.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23737) Integration test: if symlink to oc exists, but target isnt, OpenShiftCommandLineToolsRequirement is failing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23737?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23737: ------------------------------------------ merged into jbosstools-integration-tests/master. > Integration test: if symlink to oc exists, but target isnt, OpenShiftCommandLineToolsRequirement is failing > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23737 > URL: https://issues.jboss.org/browse/JBIDE-23737 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, openshift > Affects Versions: 4.4.3.AM1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.AM2 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23514) Server adapter: adapters for non-java app should not have a JMX child (double clicking it causes error)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23514?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23514: ------------------------------------------ [~kconner] is it possible to get docker images annotated in case they are "JMX-enabled" as discussed above? > Server adapter: adapters for non-java app should not have a JMX child (double clicking it causes error) > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23514 > URL: https://issues.jboss.org/browse/JBIDE-23514 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Labels: jmx, openshift_v3, server_adapter > Fix For: 4.4.3.AM2 > > Attachments: jmx-error-nodejs.png > > > Most likely server adapters for non-java based apps should not have a jmx node. > Steps to reproduce: > # ASSERT: make sure that you have a nodejs app (with a service) running in OpenShift (ex. created via nodejs-example template) > # ASSERT: make sure the build is finished, the pod is running. > # ASSERT: make sure that you have a server adapter for your service > # ASSERT: make sure that it is in "[Started, Synchronized]" state) > # EXEC: unfold the server adapter and double click on the JMX child > Result: > An error shows up > !jmx-error-nodejs.png! > {code} > java.io.IOException: org.jolokia.client.exception.J4pRemoteException: Service Unavailable > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:328) > at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:83) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:111) > at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29) > at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > Caused by: org.jolokia.client.exception.J4pRemoteException: Service Unavailable at org.jolokia.client.J4pClient.extractJsonResponse(J4pClient.java:278) > at org.jolokia.client.J4pClient.execute(J4pClient.java:191) > at org.jolokia.client.J4pClient.execute(J4pClient.java:168) > at org.jolokia.client.J4pClient.execute(J4pClient.java:117) > at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:315) > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

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

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23594?page=com.atlassian.jira.plugi... ] Rastislav Wagner reassigned JBIDE-23594: ---------------------------------------- Assignee: Rastislav Wagner Resolution: Done PR applied. Resolving > Integration tests global refactoring: org.jboss.tools.vpe.ui.bot.test > --------------------------------------------------------------------- > > Key: JBIDE-23594 > URL: https://issues.jboss.org/browse/JBIDE-23594 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: visual-page-editor-core > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Rastislav Wagner > Labels: integration, integration_tests, vpe > Fix For: 4.4.3.AM2 > > > Maven command: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.vpe.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-23212) move to tycho 1.0 (was 0.27.0) :: mvn clean verify checks old features versions against baseline

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23212: ------------------------------- Sprint: (was: devex #126 January 2017) > move to tycho 1.0 (was 0.27.0) :: mvn clean verify checks old features versions against baseline > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-23212 > URL: https://issues.jboss.org/browse/JBIDE-23212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, tycho > Fix For: 4.4.3.AM2 > > > The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar). > I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23212) move to tycho 1.0 (was 0.27.0) :: mvn clean verify checks old features versions against baseline

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23212?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23212: ------------------------------- Sprint: devex #126 January 2017 > move to tycho 1.0 (was 0.27.0) :: mvn clean verify checks old features versions against baseline > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-23212 > URL: https://issues.jboss.org/browse/JBIDE-23212 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, tycho > Fix For: 4.4.3.AM2 > > > The check with baseline seems broken to me as it does not seem to work with features. When feature.source is checked, the baseline artifact (feature.source.jar) is compared to the wrong artifact (feature.jar). > I reproduced the problem by updating jbosstool-central root POM (only the parent POM version has been changed) and the mvn verify build failed on org.jboss.tools.maven.feature. The output can be seen in one of the PR check -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23536: ------------------------------- Sprint: devex #126 January 2017 > components.py should store the assigned user > -------------------------------------------- > > Key: JBIDE-23536 > URL: https://issues.jboss.org/browse/JBIDE-23536 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, release, release-eng > Fix For: 4.4.3.AM2 > > > The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22172) create automated install test for JBDS installer jar + all early access content in Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22172?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22172: ------------------------------- Sprint: devex #125 December 2016, devex #126 January 2017 (was: devex #125 December 2016) > create automated install test for JBDS installer jar + all early access content in Central > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22172 > URL: https://issues.jboss.org/browse/JBIDE-22172 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, install-tests > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > > To better automate staging & release, we need a way to run a smoke test of a given installer jar, then to install all the GA & EA content in Central. > Steps to script: > a. wget installer jar > b. headless install (via -console or install.xml script) > c. install grinder or p2director install all the things in Central. -- 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 January 2017