May 2017 - jbosstools-issues - Jboss List Archives

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

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22799?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22799: --------------------------------------- Yes, we need to run the itests. I will look into this. > 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.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22789) Create integration tests PR check job for jmx

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22789?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22789. --------------------------------- Resolution: Rejected Rejecting since there are no jmx tests to be used. > Create integration tests PR check job for jmx > --------------------------------------------- > > Key: JBIDE-22789 > URL: https://issues.jboss.org/browse/JBIDE-22789 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Martin Malina > Fix For: 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22789) Create integration tests PR check job for jmx

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22789?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22789: --------------------------------------- I don't think we have any automated tests for jmx yet. So I'm afraid we'll have to reject this. > Create integration tests PR check job for jmx > --------------------------------------------- > > Key: JBIDE-22789 > URL: https://issues.jboss.org/browse/JBIDE-22789 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, qa > Reporter: Rastislav Wagner > Assignee: Martin Malina > Fix For: 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24301) Error while building jbosstools-openshift-4.4.3

by jyoti tumsare (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ] jyoti tumsare commented on JBIDE-24301: --------------------------------------- After installed jbosstools-4.4.4.Final I am having this View: !SignInPage.png|thumbnail! No wizard for OpenShift 3 connections present. What does it mean.Why am not able to use openshift .I don't want to go for openshift online. > Error while building jbosstools-openshift-4.4.3 > ----------------------------------------------- > > Key: JBIDE-24301 > URL: https://issues.jboss.org/browse/JBIDE-24301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.3.Final > Reporter: jyoti tumsare > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.Final > > Attachments: Error.PNG, SignInPage.png, issues.PNG, issues.txt, jboss-build.png, jbosstools-build.png, org.jboss.ide.eclipse.as.management.as7.png, target-platform.png > > > To build jbosstools-openshift-4.4.3 I followed following steps > 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3. > 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found". > 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24301) Error while building jbosstools-openshift-4.4.3

by jyoti tumsare (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ] jyoti tumsare updated JBIDE-24301: ---------------------------------- Attachment: SignInPage.png > Error while building jbosstools-openshift-4.4.3 > ----------------------------------------------- > > Key: JBIDE-24301 > URL: https://issues.jboss.org/browse/JBIDE-24301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.4.3.Final > Reporter: jyoti tumsare > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.Final > > Attachments: Error.PNG, SignInPage.png, issues.PNG, issues.txt, jboss-build.png, jbosstools-build.png, org.jboss.ide.eclipse.as.management.as7.png, target-platform.png > > > To build jbosstools-openshift-4.4.3 I followed following steps > 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3. > 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found". > 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24302) Circular fragment workflow for optional runtime use case

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24302?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24302: --------------------------------------- [~rob.stryker], yeah, I think you told me about it :) > Circular fragment workflow for optional runtime use case > -------------------------------------------------------- > > Key: JBIDE-24302 > URL: https://issues.jboss.org/browse/JBIDE-24302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.5.0.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > This is a tracking issue for this upstream bug: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=514888 > > Rob's description: > While playing with the changes dropped for Bug 513486, I found a small bug. > When a runtime is optional, the wtp framework does not add the runtime fragment directly. It will only add the server fragment, and assume that the server fragment will introduce the runtime fragment in the workflow as it chooses. > A workflow was discovered where the NewServerWizardFragment is still adding the runtime fragment before the server fragment. Since the server may also be adding that fragment later, it leads to circular behavior because the runtime fragment is in the list of fragments twice. The user will then press next continually but never advance. > Sorry for this bug. It only happens under specific situations. > Workflow: > 1) new server wizard, choose server type with optional runtime > 2) Go forward, change settings in server fragment, causing server fragment to designate runtime fragment as a child > 3) go back to main page of server wizard to change host > 4) Change host to 127.0.0.1 > 5) Press forward, forward, forward, etc. never ends. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24501) Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24501?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24501: ------------------------------------- Steps to Reproduce: # ASSERT: have the CDK with the registry that's not publicly reachable # ASSERT: have a project with a docker file in your workspace (ex. clone git@github.com:redhat-helloworld-msa/hola.git) # ASSERT: have a connection to the docker daemon in the CDK3 # EXEC: in package explorer: select your Dockerfile and pick Run As > Docker Image Build. Provide some image name and version, pick *Docker Connection* to the docker daemon in the CDK # EXEC: once the image is built, go to "Docker Explorer", select the Docker image that you built and select "Deploy to OpenShift..." # EXEC: In deploy docker image wizard: check "Push Image to Registry" and finish the wizard # ASSERT: once the push is finished, the freshly pushed image should show up in the Docker explorer !image-2017-05-23-12-00-51-733.png! # EXEC: in "Docker Explorer": select this image and pick "Deploy to OpenShift..." # ASSERT: "Deploy Docker Image" wizard shows up, having "Image Name" set to your Docker image with the docker registry prefix !image-2017-05-23-12-07-14-028.png! # EXEC: hit "Next" Result: The image name lookup fails, and 2 error dialogs show up: One that tells you that the lookup failed and one that tells you about an NPE that happened: !image-2017-05-23-12-10-06-694.png! In the Eclipse log you'll find the following: {code} java.lang.NullPointerException at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DockerConfigMetaData.env(DockerConfigMetaData.java:69) at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImageWizardModel.initializeContainerInfo(DeployImageWizardModel.java:356) at org.jboss.tools.openshift.internal.ui.wizard.deployimage.DeployImagePage$1ImageValidatorJob.run(DeployImagePage.java:154) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) {code} was: # ASSERT: have the CDK with the registry that's not publicly reachable # ASSERT: have a project with a docker file in your workspace (ex. clone git@github.com:redhat-helloworld-msa/hola.git) # ASSERT: have a connection to the docker daemon in the CDK3 # EXEC: in package explorer: select your Dockerfile and pick Run As > Docker Image Build. Provide some image name and version, pick *Docker Connection* to the docker daemon in the CDK # EXEC: once the image is built, go to "Docker Explorer", select the Docker image that you built and select "Deploy to OpenShift..." # EXEC: In deploy docker image wizard: check "Push Image to Registry" and finish the wizard # ASSERT: once the push is finished, the freshly pushed image should show up in the Docker explorer !image-2017-05-23-12-00-51-733.png! # EXEC: in "Docker Explorer": select this image and pick "Deploy to OpenShift..." # ASSERT: "Deploy Docker Image" wizard shows up, having "Image Name" set to your Docker image with the docker registry prefix !image-2017-05-23-12-07-14-028.png! # EXEC: hit "Next" Result: The image name lookup fails, and 2 error dialogs show up: One that tells you that the lookup failed and one that tells you about an NPE that happened: !image-2017-05-23-12-10-06-694.png! > Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-24501 > URL: https://issues.jboss.org/browse/JBIDE-24501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Attachments: image-2017-05-23-12-00-51-733.png, image-2017-05-23-12-07-14-028.png, image-2017-05-23-12-10-06-694.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24501) Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-24501: ---------------------------------------- Summary: Deploy Docker Image wizard: NPE when trying to deploy image previously pushed to docker registry Key: JBIDE-24501 URL: https://issues.jboss.org/browse/JBIDE-24501 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.4.Final Reporter: Andre Dietisheim Attachments: image-2017-05-23-12-00-51-733.png, image-2017-05-23-12-07-14-028.png, image-2017-05-23-12-10-06-694.png -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24500) Create smaller slaves for some integration tests

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-24500: ------------------------------------- Summary: Create smaller slaves for some integration tests Key: JBIDE-24500 URL: https://issues.jboss.org/browse/JBIDE-24500 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: integration-tests Affects Versions: 4.5.0.AM1 Reporter: Josef Kopriva Create smaller slaves for some integration tests to save resources on OpenStack. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24500) Create smaller slaves for some integration tests

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24500?page=com.atlassian.jira.plugi... ] Josef Kopriva reassigned JBIDE-24500: ------------------------------------- Assignee: Josef Kopriva > Create smaller slaves for some integration tests > ------------------------------------------------ > > Key: JBIDE-24500 > URL: https://issues.jboss.org/browse/JBIDE-24500 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: integration-tests > Affects Versions: 4.5.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > > Create smaller slaves for some integration tests to save resources on OpenStack. -- 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