August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22767) Deploy Docker Wizard: Create image stream contains wrong tags in some cases

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22767?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22767: ------------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Deploy Docker Wizard: Create image stream contains wrong tags in some cases > --------------------------------------------------------------------------- > > Key: JBIDE-22767 > URL: https://issues.jboss.org/browse/JBIDE-22767 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Marián Labuda > Labels: docker, openshift_v3 > Fix For: 4.4.2.AM1 > > > In Deploy Image to OpenShift wizard when I am trying to deploy image docker.io/openshift/hello-openshift:v1.2.1, the image stream created contains some weird tags. If I deploy this image via oc binary then a created image stream contains correct tag v1.2.1, but from tooling it contains more tags and none of them is the desired one (there are 0.4, 0.5, latest...). > Some behaviour is also common for normal usage. When deploying a image with tag latest, there are also defined other tags. OC binary creates IS only with the one tag, the one which was passed as "partial" argument when deploying an image. > Consequences of this issue are no pods created once the deploy image to OpenShift is finished. User has to manually trigger Deploy Latest from context menu of a deployment configuration to spin up an application pod. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard, Connection: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19506: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.1.Final) > Connection wizard, Connection: should have unit tests > ------------------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: openshift_v3, tests > Fix For: 4.4.x > > Original Estimate: 2 days > Time Spent: 3 days > Remaining Estimate: 3 days > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23057) Integration tests: test import project in server adapter wizard

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23057: ---------------------------------------- Summary: Integration tests: test import project in server adapter wizard Key: JBIDE-23057 URL: https://issues.jboss.org/browse/JBIDE-23057 Project: Tools (JBoss Tools) Issue Type: Task Components: openshift Affects Versions: 4.4.0.Final Reporter: Andre Dietisheim JBIDE-22621 allows the user to import a project in the server adapter wizard. We should add an integration test for this scenarion in CreateServerAdapterTest -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23057) Integration tests: test import project in server adapter wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23057?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23057: ------------------------------------- Fix Version/s: 4.4.2.AM1 > Integration tests: test import project in server adapter wizard > --------------------------------------------------------------- > > Key: JBIDE-23057 > URL: https://issues.jboss.org/browse/JBIDE-23057 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Fix For: 4.4.2.AM1 > > > JBIDE-22621 allows the user to import a project in the server adapter wizard. We should add an integration test for this scenarion in CreateServerAdapterTest -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22613) Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22613?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22613: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.1.Final) > Connection wizard: When a connection is configured with a stored token, switching back with basic will fail if token is invalid > ------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22613 > URL: https://issues.jboss.org/browse/JBIDE-22613 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Jeff MAURY > Labels: connection, connection_wizard, openshift_v3 > Fix For: 4.4.x > > > If an Openshift is configured with a OAuth and a stored token, if you want to switch back to basic, the connection will fail because the connection is still made using Oauth -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22376) Enable JMX when entering Debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22376?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22376: ------------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.1.Final) > Enable JMX when entering Debug mode > ----------------------------------- > > Key: JBIDE-22376 > URL: https://issues.jboss.org/browse/JBIDE-22376 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.1.Beta1 > Reporter: Thomas Mäder > Assignee: Fred Bricon > Fix For: 4.4.2.AM1 > > > We need to update the deployment configuration when entering debug mode. It is not entirely clear how to determine that an Openshift Pod has indeed a wildfly/EAP in it and can be reached with remoting-jmx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22727) Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22727?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22727: ------------------------------------- Fix Version/s: 4.4.x (was: 4.4.1.Final) > Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22727 > URL: https://issues.jboss.org/browse/JBIDE-22727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.x > > > The kind of Openshift resources are declated in 2 different places: WatchManager and ConnectionWrapper. This increases the technical debt and may lead to resources displayed by the explorer but not refreshed by the watcher. > The task requires investigation about ResourceKind.IMAGE_STREAM_TAG, which is present in ConnectionWrapper, but there is no such element in WatchManager's array. See discussion [here|https://github.com/jbosstools/jbosstools-openshift/pull/1272#discuss...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23001) Application Wizard: NPE when opening OS 2 wizard from central or shell menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23001?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23001: ------------------------------------------ the integration tests for the new application wizard cover this case in ID301OpenNewApplicationWizardTest#testOpenWizardViaCentral and #testOpenWizardViaMenu. Resolving > Application Wizard: NPE when opening OS 2 wizard from central or shell menu > --------------------------------------------------------------------------- > > Key: JBIDE-23001 > URL: https://issues.jboss.org/browse/JBIDE-23001 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: application_wizard, openshift_v2, regression > Fix For: 4.4.1.Final > > > When I am opening a New OpenShift Application wizard for OpenShift 2 connections, I get an NPE. This is caused only when opening wizard from shell menu File - New - OpenShift Application or from Central. > stack trace of NPE: > {code} > Problems occurred when invoking code from plug-in: "org.eclipse.jface". > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.common.ui.connection.ConnectionWizardPage.onPageWillGetDeactivated(ConnectionWizardPage.java:408) > at org.jboss.tools.openshift.internal.common.ui.wizard.AbstractOpenShiftWizardPage$3.handlePageChanging(AbstractOpenShiftWizardPage.java:121) > at org.eclipse.jface.wizard.WizardDialog$7.run(WizardDialog.java:1540) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173) > at org.eclipse.jface.wizard.WizardDialog.firePageChanging(WizardDialog.java:1537) > at org.eclipse.jface.wizard.WizardDialog.doPageChanging(WizardDialog.java:890) > at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1177) > at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:876) > at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:419) > at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:618) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5219) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4553) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4143) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.jboss.tools.central.internal.WizardSupport.openWizard(WizardSupport.java:71) > at org.jboss.tools.central.editors.GettingStartedHtmlPage$9.run(GettingStartedHtmlPage.java:431) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4146) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22439) Tests: include different checkers in our build or jenkins

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22439?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22439 at 8/30/16 6:53 AM: ------------------------------------------------------------------- I mailed sonarqube.com to get an account. Awaiting reply. Postponing since effort is ongoing. was (Author: adietish): I mailed sonarqube.com to get an account. Awaiting reply. > Tests: include different checkers in our build or jenkins > --------------------------------------------------------- > > Key: JBIDE-22439 > URL: https://issues.jboss.org/browse/JBIDE-22439 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.x > > Attachments: sornarcube-github-signup-error.png > > Original Estimate: 2 days > Time Spent: 2 hours, 30 minutes > Remaining Estimate: 1 day, 5 hours, 30 minutes > > We should have different checkers in our build so that problems are forced on us. Just having them in sonar isnt good enough since it tends to get forgotten. > - Findbugs > - PMC > - Code-format-Checkers > - Code-duplication (like [cpd|http://pmd.sourceforge.net/pmd-4.3.0/cpd.html] or [simian|http://www.harukizaemon.com/simian/]) > - ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22439) Tests: include different checkers in our build or jenkins

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22439?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22439: ------------------------------------- Sprint: devex #120 September 2016 (was: devex #119 August 2016) > Tests: include different checkers in our build or jenkins > --------------------------------------------------------- > > Key: JBIDE-22439 > URL: https://issues.jboss.org/browse/JBIDE-22439 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.x > > Attachments: sornarcube-github-signup-error.png > > Original Estimate: 2 days > Time Spent: 2 hours, 30 minutes > Remaining Estimate: 1 day, 5 hours, 30 minutes > > We should have different checkers in our build so that problems are forced on us. Just having them in sonar isnt good enough since it tends to get forgotten. > - Findbugs > - PMC > - Code-format-Checkers > - Code-duplication (like [cpd|http://pmd.sourceforge.net/pmd-4.3.0/cpd.html] or [simian|http://www.harukizaemon.com/simian/]) > - ... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues August 2016