[JBoss JIRA] (JBIDE-23881) Properties: Builds are missing the cathegories and properties that exist in all other tab items
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-23881:
----------------------------------------
Summary: Properties: Builds are missing the cathegories and properties that exist in all other tab items
Key: JBIDE-23881
URL: https://issues.jboss.org/browse/JBIDE-23881
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: openshift
Affects Versions: 4.4.2.Final
Reporter: Andre Dietisheim
The "Builds" tab contains a list of builds that exist on the server. Selecting them unveil the properties of the selected build.
The same is valid for all other tabs like "Build Configs" , "Deployments", etc. But these other items all have cathegories like "Annotations", "Basic", "Labels", etc.
"Builds" dont have these:
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23625) JMX: jmx tree is not very usable
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23625?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23625:
-------------------------------------
Description:
steps to reproduce:
# EXEC: create a new app via eap64-basic-s2i template and import the source to a workspace project
# EXEC: create a server adapter for it
# ASSERT: your server adapter now has a JMX child node
# EXEC: double click it and wait until all MBeans are loaded
# EXEC: now try to see if you can find your deployment
Result:
You get a listing of tons of beans.
!mbeans.png!
Your deployment is a child bean of jboss.as, named by the war that was created:
!image-2016-12-02-16-47-59-519.png|thumbnail!
Rather painfull to find a listing of your deployments in this way.
was:
steps to reproduce:
# EXEC: create a new app via eap64-basic-s2i template and import the source to a workspace project
# EXEC: create a server adapter for it
# ASSERT: your server adapter now has a JMX child node
# EXEC: double click it and wait until all MBeans are loaded
# EXEC: now try to see if you can find your deployment
Result:
You get a listing of tons of beans.
!mbeans.png!
Your deployment is a child bean of jboss.as, named by the war that was created:
!image-2016-12-02-16-47-59-519.png!
Rather painfull to find a listing of your deployments in this way.
> JMX: jmx tree is not very usable
> --------------------------------
>
> Key: JBIDE-23625
> URL: https://issues.jboss.org/browse/JBIDE-23625
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Andre Dietisheim
> Fix For: 4.5.0.AM1
>
> Attachments: image-2016-12-02-16-47-59-519.png
>
>
> steps to reproduce:
> # EXEC: create a new app via eap64-basic-s2i template and import the source to a workspace project
> # EXEC: create a server adapter for it
> # ASSERT: your server adapter now has a JMX child node
> # EXEC: double click it and wait until all MBeans are loaded
> # EXEC: now try to see if you can find your deployment
> Result:
> You get a listing of tons of beans.
> !mbeans.png!
> Your deployment is a child bean of jboss.as, named by the war that was created:
> !image-2016-12-02-16-47-59-519.png|thumbnail!
> Rather painfull to find a listing of your deployments in this way.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23625) JMX: jmx tree is not very usable
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23625?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23625:
-------------------------------------
Description:
steps to reproduce:
# EXEC: create a new app via eap64-basic-s2i template and import the source to a workspace project
# EXEC: create a server adapter for it
# ASSERT: your server adapter now has a JMX child node
# EXEC: double click it and wait until all MBeans are loaded
# EXEC: now try to see if you can find your deployment
Result:
You get a listing of tons of beans.
!mbeans.png!
Your deployment is a child bean of jboss.as, named by the war that was created:
!image-2016-12-02-16-47-59-519.png!
Rather painfull to find a listing of your deployments in this way.
was:
steps to reproduce:
# EXEC: create a new app via eap64-basic-s2i template and import the source to a workspace project
# EXEC: create a server adapter for it
# ASSERT: your server adapter now has a JMX child node
# EXEC: double click it and wait until all MBeans are loaded
# EXEC: now try to see if you can find your deployment
Result:
You get a listing of tons of beans.
!mbeans.png!
Your deployment is a child bean of jboss.as, named by the war that was created:
!mbean-deployment.png!
Rather painfull to find a listing of your deployments in this way.
> JMX: jmx tree is not very usable
> --------------------------------
>
> Key: JBIDE-23625
> URL: https://issues.jboss.org/browse/JBIDE-23625
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.2.Final
> Reporter: Andre Dietisheim
> Fix For: 4.5.0.AM1
>
> Attachments: image-2016-12-02-16-47-59-519.png
>
>
> steps to reproduce:
> # EXEC: create a new app via eap64-basic-s2i template and import the source to a workspace project
> # EXEC: create a server adapter for it
> # ASSERT: your server adapter now has a JMX child node
> # EXEC: double click it and wait until all MBeans are loaded
> # EXEC: now try to see if you can find your deployment
> Result:
> You get a listing of tons of beans.
> !mbeans.png!
> Your deployment is a child bean of jboss.as, named by the war that was created:
> !image-2016-12-02-16-47-59-519.png!
> Rather painfull to find a listing of your deployments in this way.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23860) Unit tests: CDKOpenshiftUtilityTest.testOpenshiftConnectionCredentials is failing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23860?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-23860.
------------------------------------
nothing for QE to verify. Closing
> Unit tests: CDKOpenshiftUtilityTest.testOpenshiftConnectionCredentials is failing
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23860
> URL: https://issues.jboss.org/browse/JBIDE-23860
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.3.Final
>
>
> starting with [#1815|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Master/job/jbosstools-openshift_master/1815/] the jenkins build for openshift started to fail with an error in the unit-tests:
> {code}
> Failed tests:
> CDKOpenshiftUtilityTest.testOpenshiftConnectionCredentials:57 expected:<[openshift-dev]> but was:<[test]>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23860) Unit tests: CDKOpenshiftUtilityTest.testOpenshiftConnectionCredentials is failing
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23860?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23860:
------------------------------------------
starting with [#1831|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Master/job/jbosstools-openshift_master/1831] jenkins is back to blue.
> Unit tests: CDKOpenshiftUtilityTest.testOpenshiftConnectionCredentials is failing
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23860
> URL: https://issues.jboss.org/browse/JBIDE-23860
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.Final
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.4.3.Final
>
>
> starting with [#1815|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Master/job/jbosstools-openshift_master/1815/] the jenkins build for openshift started to fail with an error in the unit-tests:
> {code}
> Failed tests:
> CDKOpenshiftUtilityTest.testOpenshiftConnectionCredentials:57 expected:<[openshift-dev]> but was:<[test]>
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (JBIDE-23867) OCBinary: is mixing platform independent with dependent code
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23867?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-23867:
-------------------------------------
{code|
commit a340f929df783e55d199755c034768184b24fad4
Author: Rob Stryker <rob(a)oxbeef.net>
Date: Mon Feb 6 16:32:55 2017 -0500
{code}
It's mostly a bunch of cleanup to make things more clear for andre.
> OCBinary: is mixing platform independent with dependent code
> ------------------------------------------------------------
>
> Key: JBIDE-23867
> URL: https://issues.jboss.org/browse/JBIDE-23867
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
> Fix For: 4.4.3.Final
>
>
> OCBinary is suing enums for the different platform. The platform instance is chosen right when you get the instance that you want to work with:
> {code}
> OCBinary#getInstance
> {code}
> {code}
> public static OCBinary getInstance() {
> if (SystemUtils.IS_OS_WINDOWS) {
> return WINDOWS;
> } else {
> return OTHER;
> }
> }
> {code}
> But then, latter code (that was introduced later in #getSystemPathLocation ignoring it and start being platform independent again, even setting the default to be linux:
> {code}
> public String getSystemPathLocation() {
> if (locationBinary == null) {
> this.locationBinary = new CommandLocationBinary("oc");
> locationBinary.addPlatformLocation(Platform.OS_LINUX, OC_DEFAULTLOCATION_LINUX);
> locationBinary.setDefaultPlatform(Platform.OS_LINUX);
> }
> return locationBinary.findLocation();
> }
> {code}
> Even worse is that the above code hard-codes the oc binary to be "oc" while the enum for windows is defining it as "oc.exe"
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month