May 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24318) Analyze watch replacement

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24318?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-24318: ------------------------------------- Fix Version/s: 4.5.0.AM1 > Analyze watch replacement > ------------------------- > > Key: JBIDE-24318 > URL: https://issues.jboss.org/browse/JBIDE-24318 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: openshift, openshift_v3 > Fix For: 4.5.0.AM1 > > > Analyze how the watch and watch manager can be implemented when switching to the fabric8 client -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22680) Create CI jobs running integration tests on incoming PRs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22680?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22680: ------------------------------- Sprint: devex #132 May 2017 > Create CI jobs running integration tests on incoming PRs > -------------------------------------------------------- > > Key: JBIDE-22680 > URL: https://issues.jboss.org/browse/JBIDE-22680 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, qa > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Once we have integration tests running against a given source (JBIDE-22679), let's create the CI jobs to run those automatically and vote on incoming pull requests. > *STEPS TO SETUP PR CHECK JOB: * > 1.Update your tests pom.xml to install locally build plugins. See https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... > 2. Create your job here https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... you can use cdi11.prcheck job as your template > - specify who is the job maintainer > - dont forget to change GitHub project to monitor the correct one > - change Trigger Setup -> Commit status context to {name-of-the-component}-Integration-tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22680) Create CI jobs running integration tests on incoming PRs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22680?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22680: ------------------------------- Sprint: (was: devex #132 May 2017) > Create CI jobs running integration tests on incoming PRs > -------------------------------------------------------- > > Key: JBIDE-22680 > URL: https://issues.jboss.org/browse/JBIDE-22680 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, qa > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Once we have integration tests running against a given source (JBIDE-22679), let's create the CI jobs to run those automatically and vote on incoming pull requests. > *STEPS TO SETUP PR CHECK JOB: * > 1.Update your tests pom.xml to install locally build plugins. See https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... > 2. Create your job here https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... you can use cdi11.prcheck job as your template > - specify who is the job maintainer > - dont forget to change GitHub project to monitor the correct one > - change Trigger Setup -> Commit status context to {name-of-the-component}-Integration-tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22680) Create CI jobs running integration tests on incoming PRs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22680?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22680: ------------------------------- Sprint: devex #132 May 2017 > Create CI jobs running integration tests on incoming PRs > -------------------------------------------------------- > > Key: JBIDE-22680 > URL: https://issues.jboss.org/browse/JBIDE-22680 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, qa > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Once we have integration tests running against a given source (JBIDE-22679), let's create the CI jobs to run those automatically and vote on incoming pull requests. > *STEPS TO SETUP PR CHECK JOB: * > 1.Update your tests pom.xml to install locally build plugins. See https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... > 2. Create your job here https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... you can use cdi11.prcheck job as your template > - specify who is the job maintainer > - dont forget to change GitHub project to monitor the correct one > - change Trigger Setup -> Commit status context to {name-of-the-component}-Integration-tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22680) Create CI jobs running integration tests on incoming PRs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22680?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22680: ------------------------------- Fix Version/s: 4.5.0.AM1 (was: 4.4.x) > Create CI jobs running integration tests on incoming PRs > -------------------------------------------------------- > > Key: JBIDE-22680 > URL: https://issues.jboss.org/browse/JBIDE-22680 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, qa > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Once we have integration tests running against a given source (JBIDE-22679), let's create the CI jobs to run those automatically and vote on incoming pull requests. > *STEPS TO SETUP PR CHECK JOB: * > 1.Update your tests pom.xml to install locally build plugins. See https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... > 2. Create your job here https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... you can use cdi11.prcheck job as your template > - specify who is the job maintainer > - dont forget to change GitHub project to monitor the correct one > - change Trigger Setup -> Commit status context to {name-of-the-component}-Integration-tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22680) Create CI jobs running integration tests on incoming PRs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22680?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-22680: ---------------------------------- Assignee: Nick Boldt (was: Rastislav Wagner) > Create CI jobs running integration tests on incoming PRs > -------------------------------------------------------- > > Key: JBIDE-22680 > URL: https://issues.jboss.org/browse/JBIDE-22680 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build, qa > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Once we have integration tests running against a given source (JBIDE-22679), let's create the CI jobs to run those automatically and vote on incoming pull requests. > *STEPS TO SETUP PR CHECK JOB: * > 1.Update your tests pom.xml to install locally build plugins. See https://github.com/jbosstools/jbosstools-integration-tests/blob/master/te... > 2. Create your job here https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... you can use cdi11.prcheck job as your template > - specify who is the job maintainer > - dont forget to change GitHub project to monitor the correct one > - change Trigger Setup -> Commit status context to {name-of-the-component}-Integration-tests -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23869) ClassCastException with Jolokia connection

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23869?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-23869: ----------------------------------------- I want that the user has the information about the provided error from OpenShift. In our specific case, i want the user to know that it is an authentication problem. > ClassCastException with Jolokia connection > ------------------------------------------ > > Key: JBIDE-23869 > URL: https://issues.jboss.org/browse/JBIDE-23869 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jmx, openshift > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: jmx, jolokia, openshift > Fix For: 4.5.0.AM1 > > Attachments: failure.png, image-2017-02-06-13-54-27-708.png > > > !image-2017-02-06-13-54-27-708.png|thumbnail! > {noformat} > !ENTRY org.eclipse.core.jobs 4 2 2017-02-06 13:52:39.767 > !MESSAGE An internal error occurred during: "Connect Job". > !STACK 0 > java.lang.ClassCastException: java.lang.String cannot be cast to java.lang.Long > at org.jolokia.client.request.ValidatingResponseExtractor.extract(ValidatingResponseExtractor.java:58) > at org.jolokia.client.J4pClient.execute(J4pClient.java:195) > 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) > 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) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24383) Connection wizard: offer openshift.com as default server

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24383?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-24383. ------------------------------ Verified in Devstudio 10.4.0.GA.GA-v20170511-1748-B62. Closing. > Connection wizard: offer openshift.com as default server > -------------------------------------------------------- > > Key: JBIDE-24383 > URL: https://issues.jboss.org/browse/JBIDE-24383 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.4.Final, 4.5.0.AM1 > > Attachments: connection-wizard-signup-link.png > > > now that https://openshift.com is launched we should provide it as default server in the connection wizard. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24437) We should remove (Tech Preview) label from CDK server adapter server's type name

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24437?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-24437. --------------------------------- Resolution: Done > We should remove (Tech Preview) label from CDK server adapter server's type name > -------------------------------------------------------------------------------- > > Key: JBIDE-24437 > URL: https://issues.jboss.org/browse/JBIDE-24437 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Fix For: 4.4.4.Final > > Attachments: Spectacle.J12271.png > > > I believe that we should remove "(Tech Preview)" from server's type while adding new server adapter. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24437) We should remove (Tech Preview) label from CDK server adapter server's type name

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24437?page=com.atlassian.jira.plugi... ] Ondrej Dockal edited comment on JBIDE-24437 at 5/15/17 8:45 AM: ---------------------------------------------------------------- Thanks [~rob.stryker] for implementing the issue in advance! :) Verified on: Version: 10.4.0.GA Build id: GA-v20170511-1748-B62 and I also checked it in devstudio 11 build from master: devstudio-11.0.0.AM1-v20170515-0455-B123. was (Author: odockal): Thanks [~rob.stryker] for implementing the issue in advance! :) Verified on: Version: 10.4.0.GA Build id: GA-v20170511-1748-B62 and I also checked it in devstudio 11 from build from master: devstudio-11.0.0.AM1-v20170515-0455-B123. > We should remove (Tech Preview) label from CDK server adapter server's type name > -------------------------------------------------------------------------------- > > Key: JBIDE-24437 > URL: https://issues.jboss.org/browse/JBIDE-24437 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.4.Final > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Fix For: 4.4.4.Final > > Attachments: Spectacle.J12271.png > > > I believe that we should remove "(Tech Preview)" from server's type while adding new server adapter. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 May 2017