[JBoss JIRA] (JBIDE-24236) cdk3 oc command
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24236?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24236 at 4/11/17 5:46 PM:
-------------------------------------------------------------------
Great idea, really.
In the preferences, where one does set the location of the oc binary we look up the PATH if the location is not set. See here: https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or...
As you pointed out we might have to store oc binaries per connection, but only if it turns out that oc is not backward compatible (would oc 3.4 work with CDK 2.3?). As far as I remember there were problems. Verifying this is for sure the first step to take. If that's not true, or the vast exception, I'd tend to think that we can simply also look up the cache for minishift beside the PATH.
A simple warning for known compat issues in specific oc binaries could also help keeping this simple using single, global oc location (see here where we warn that oc < 1.1.1 is not working for rsync: https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or...)
was (Author: adietish):
Great idea, really.
In the preferences, where one does set the location of the oc binary we look up the PATH if the location is not set. See here: https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or...
As you pointed out we might have to store oc binaries per connection, but only if it turns out that oc is not backward compatible (would oc 3.4 work with CDK 2.3?). As far as I remember there were problems. Verifying this is for sure the first step to take. If that's not true, or the vast exception, I'd tend to think that we can simply also look up the cache for minishift beside the PATH.
A simple warning for known compat issues in specific oc binaries could also help keeping this simple using single, global oc location (see here where we warn that oc < 1.1.1 is not working for rsync: https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or...)
> cdk3 oc command
> ---------------
>
> Key: JBIDE-24236
> URL: https://issues.jboss.org/browse/JBIDE-24236
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Reporter: Rob Stryker
> Assignee: Rob Stryker
>
> After minishift setup-cdk, the oc command is at %USERPROFILE%\.minishift\cache\oc\v3.4.1.2
> Should our tools help streamline this process for users? I would suggest yes, but needs investigation **how** to do it.
> Another question is, do we need different 'oc' command versions for each openshift connection? Should it really be a workplace setting? Or should it be per-connection?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (JBIDE-24236) cdk3 oc command
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24236?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-24236 at 4/11/17 5:44 PM:
-------------------------------------------------------------------
Great idea, really.
In the preferences, where one does set the location of the oc binary we look up the PATH if the location is not set. See here: https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or...
As you pointed out we might have to store oc binaries per connection, but only if it turns out that oc is not backward compatible (would oc 3.4 work with CDK 2.3?). As far as I remember there were problems. Verifying this is for sure 1 of the first steps to take. If that's not true, or the vast exception, I'd tend to think that we can simply also look up the cache for minishift beside the PATH.
A simple warning for known compat issues in specific oc binaries could also help keeping this simple with a single oc location stored in preferences (see here where we warn that oc < 1.1.1 is not working for rsync: https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or...)
was (Author: adietish):
Great idea, really.
In the preferences, where one does set the location of the oc binary we look up into different default locations and the PATH.
See here: https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or...
One of the problems is that the copy of the oc binary only exists for CDK3, not for CDK2
Another one might be that the different CDKs require different oc binaries. As far as I remember there were problems in backwards compatibility (would oc 3.4 work with CDK 2.3?). Verifying this is for sure 1 of the first steps to take. If this is true we'd even have to change the preferences to use different oc binaries for different CDKs. If that's not true, or the vast exception, I'd tend to think that we can simply also look up the cache for minishift beside the path.
> cdk3 oc command
> ---------------
>
> Key: JBIDE-24236
> URL: https://issues.jboss.org/browse/JBIDE-24236
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Reporter: Rob Stryker
> Assignee: Rob Stryker
>
> After minishift setup-cdk, the oc command is at %USERPROFILE%\.minishift\cache\oc\v3.4.1.2
> Should our tools help streamline this process for users? I would suggest yes, but needs investigation **how** to do it.
> Another question is, do we need different 'oc' command versions for each openshift connection? Should it really be a workplace setting? Or should it be per-connection?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (JBIDE-24236) cdk3 oc command
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24236?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-24236:
------------------------------------------
Great idea, really.
In the preferences, where one does set the location of the oc binary we look up into different default locations and the PATH.
See here: https://github.com/jbosstools/jbosstools-openshift/blob/master/plugins/or...
One of the problems is that the copy of the oc binary only exists for CDK3, not for CDK2
Another one might be that the different CDKs require different oc binaries. As far as I remember there were problems in backwards compatibility (would oc 3.4 work with CDK 2.3?). Verifying this is for sure 1 of the first steps to take. If this is true we'd even have to change the preferences to use different oc binaries for different CDKs. If that's not true, or the vast exception, I'd tend to think that we can simply also look up the cache for minishift beside the path.
> cdk3 oc command
> ---------------
>
> Key: JBIDE-24236
> URL: https://issues.jboss.org/browse/JBIDE-24236
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Reporter: Rob Stryker
> Assignee: Rob Stryker
>
> After minishift setup-cdk, the oc command is at %USERPROFILE%\.minishift\cache\oc\v3.4.1.2
> Should our tools help streamline this process for users? I would suggest yes, but needs investigation **how** to do it.
> Another question is, do we need different 'oc' command versions for each openshift connection? Should it really be a workplace setting? Or should it be per-connection?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (JBIDE-23769) New Application: Do not throw exception in error log when provided template is of wrong kind.
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23769?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23769:
------------------------------------------
[~jeffmaury] thx for the fix!
merged into jbosstools-4.4.x and cherry-picked into master
> New Application: Do not throw exception in error log when provided template is of wrong kind.
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-23769
> URL: https://issues.jboss.org/browse/JBIDE-23769
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Radim Hopp
> Assignee: Jeff MAURY
> Priority: Minor
> Fix For: 4.4.4.AM3
>
>
> When creating new application from local template one selects wrong file (not of kind "Template", but kind "Pod" for example) multiple (same) exceptions are thrown into error log:
> {noformat}
> !ENTRY org.eclipse.core.databinding 4 0 2017-01-19 13:56:20.472
> !MESSAGE Unhandled exception: Wrong resource kind: Pod
> !STACK 0
> org.jboss.tools.openshift.internal.ui.wizard.newapp.NotATemplateException: Wrong resource kind: Pod
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.getLocalAppSource(NewApplicationWizardModel.java:139)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.loadAppSource(NewApplicationWizardModel.java:293)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.ApplicationSourceListPage$17.run(ApplicationSourceListPage.java:824)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> I think it's enough to inform the user in the wizard (this is already happening).
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (JBIDE-24250) OpenShift Explorer sometimes don't show the objects in Properties view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24250?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24250:
-------------------------------------
Project: Tools (JBoss Tools) (was: Red Hat JBoss Developer Studio (devstudio))
Key: JBIDE-24250 (was: JBDS-4231)
Docs QE Status: (was: NEW)
Component/s: openshift
(was: openshift)
Affects Version/s: 4.2.0.Final
(was: 10.2.0.GA)
Fix Version/s: 4.4.4.AM3
(was: 10.4.0.AM3)
> OpenShift Explorer sometimes don't show the objects in Properties view
> ----------------------------------------------------------------------
>
> Key: JBIDE-24250
> URL: https://issues.jboss.org/browse/JBIDE-24250
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Final
> Environment: * JBoss Developer Studio 10.2.0.GA
> * CDK
> Reporter: Ricardo Martinelli Oliveira
> Assignee: Jeff MAURY
> Fix For: 4.4.4.AM3
>
> Attachments: empty-builds.png
>
>
> After right-click in a project in OpenShift Explorer view and select Properties, not always the list of Kubernetes/OpenShift objects are listed in the Properties view. The workaround I found is close all editors, the Properties view and after changing the focus on other views, go back to OpenShift Explorer and Refresh it I can finally list the objects.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (JBDS-4231) OpenShift Explorer sometimes don't show the objects in Properties view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-4231?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim commented on JBDS-4231:
----------------------------------------
[~jeffmaury] this issue should be move to JBoss Tools since there's nothing Devstudio specific in this issue.
> OpenShift Explorer sometimes don't show the objects in Properties view
> ----------------------------------------------------------------------
>
> Key: JBDS-4231
> URL: https://issues.jboss.org/browse/JBDS-4231
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 10.2.0.GA
> Environment: * JBoss Developer Studio 10.2.0.GA
> * CDK
> Reporter: Ricardo Martinelli Oliveira
> Assignee: Jeff MAURY
> Fix For: 10.4.0.AM3
>
> Attachments: empty-builds.png
>
>
> After right-click in a project in OpenShift Explorer view and select Properties, not always the list of Kubernetes/OpenShift objects are listed in the Properties view. The workaround I found is close all editors, the Properties view and after changing the focus on other views, go back to OpenShift Explorer and Refresh it I can finally list the objects.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (ERT-501) Add new Docker Reddeer feature [EBZ#515136]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-501:
---------------------------------------
Summary: Add new Docker Reddeer feature [EBZ#515136]
Key: ERT-501
URL: https://issues.jboss.org/browse/ERT-501
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Priority: Trivial
Fix For: Oxygen (4.7)
Hi,
please create feature group for org.eclipse.linuxtools.docker.reddeer plugin, so we can use this plugin in our tests.
Thanks
Josef
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months
[JBoss JIRA] (JBDS-4231) OpenShift Explorer sometimes don't show the objects in Properties view
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-4231?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-4231:
-----------------------------------
Workaround Description: Unfold the project in the OpenShift Explorer
Workaround: Workaround Exists
> OpenShift Explorer sometimes don't show the objects in Properties view
> ----------------------------------------------------------------------
>
> Key: JBDS-4231
> URL: https://issues.jboss.org/browse/JBDS-4231
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 10.2.0.GA
> Environment: * JBoss Developer Studio 10.2.0.GA
> * CDK
> Reporter: Ricardo Martinelli Oliveira
> Assignee: Jeff MAURY
> Fix For: 10.4.0.AM3
>
> Attachments: empty-builds.png
>
>
> After right-click in a project in OpenShift Explorer view and select Properties, not always the list of Kubernetes/OpenShift objects are listed in the Properties view. The workaround I found is close all editors, the Properties view and after changing the focus on other views, go back to OpenShift Explorer and Refresh it I can finally list the objects.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 12 months