[JBoss JIRA] (JBIDE-24135) Clean up old vscode builds and establish file retention / cleanup policy
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24135?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-24135:
-------------------------------------
[~nickboldt] all jdt-language-server-version.tar.gz can be deleted.
I'd keep the last version of each vsix, purged every week probably
> Clean up old vscode builds and establish file retention / cleanup policy
> ------------------------------------------------------------------------
>
> Key: JBIDE-24135
> URL: https://issues.jboss.org/browse/JBIDE-24135
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.4.AM2
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Fix For: 4.5.0.AM1
>
>
> Discovered today that there are many jdt-language-server builds in http://download.jboss.org/jbosstools/static/vscode/ and since many of these predate the migration to eclipse, rename, and reversioning of the project, it would probably make sense to delete these obsolete artifacts.
> * java-server 1.0.x
> * java-server 0.1.x
> * jdt-language-server 0.1 older than 4 weeks ago
> Since the /static/ folder is reserved for permanent artifacts that will be Akamai mirrored for performance, and since these biweekly updates are NOT permanent stable releases, we might want to consider using a different folder, such as:
> /neon/snapshots/vscode
> /neon/integration/vscode
> etc.
> Going forward, we need to establish how often to delete old artifacts/builds. If builds are not conforming to the schema used by jbosstools-* projects, then a new tool for cleanup will need to be created.
> Today, build folders are automatically deleted when they're too old, eg., from http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer... if they conform to a datestamp like http://download.jboss.org/jbosstools/neon/snapshots/builds/jbosstools-aer...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[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:
---------------------------------------
Now I am building jbosstools-openshift-jbosstools-4.4.3.x
Facing Errors:
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.express.client:eclipse-plugin:3.3.2-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.eclipse.tycho:target-platform-configuration @ org.jboss.tools:openshift:3.3.2-SNAPSHOT, C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\pom.xml, line 57, column 12
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-clean-plugin is missing. @ org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.express.client:[unknown-version], C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\plugins\org.jboss.tools.openshift.express.client\pom.xml, line 77, column 12
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.express.core:eclipse-plugin:3.3.2-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.eclipse.tycho:target-platform-configuration @ org.jboss.tools:openshift:3.3.2-SNAPSHOT, C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\pom.xml, line 57, column 12
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.express.ui:eclipse-plugin:3.3.2-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.eclipse.tycho:target-platform-configuration @ org.jboss.tools:openshift:3.3.2-SNAPSHOT, C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\pom.xml, line 57, column 12
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.client:eclipse-plugin:3.3.2-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.eclipse.tycho:target-platform-configuration @ org.jboss.tools:openshift:3.3.2-SNAPSHOT, C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\pom.xml, line 57, column 12
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-clean-plugin is missing. @ org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.client:[unknown-version], C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\plugins\org.jboss.tools.openshift.client\pom.xml, line 128, column 12
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.common.core:eclipse-plugin:3.3.2-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.eclipse.tycho:target-platform-configuration @ org.jboss.tools:openshift:3.3.2-SNAPSHOT, C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\pom.xml, line 57, column 12
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.common.ui:eclipse-plugin:3.3.2-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.eclipse.tycho:target-platform-configuration @ org.jboss.tools:openshift:3.3.2-SNAPSHOT, C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\pom.xml, line 57, column 12
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.core:eclipse-plugin:3.3.2-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.eclipse.tycho:target-platform-configuration @ org.jboss.tools:openshift:3.3.2-SNAPSHOT, C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\pom.xml, line 57, column 12
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.ui:eclipse-plugin:3.3.2-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.eclipse.tycho:target-platform-configuration @ org.jboss.tools:openshift:3.3.2-SNAPSHOT, C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\pom.xml, line 57, column 12
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-clean-plugin is missing. @ org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.ui:[unknown-version], C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\plugins\org.jboss.tools.openshift.ui\pom.xml, line 47, column 21
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:eclipse-plugin:3.3.2-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.eclipse.tycho:target-platform-configuration @ org.jboss.tools:openshift:3.3.2-SNAPSHOT, C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\pom.xml, line 57, column 12
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.js:eclipse-plugin:3.3.2-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.eclipse.tycho:target-platform-configuration @ org.jboss.tools:openshift:3.3.2-SNAPSHOT, C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\pom.xml, line 57, column 12
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jboss.tools.openshift:plugins:pom:3.3.2-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.eclipse.tycho:target-platform-configuration @ org.jboss.tools:openshift:3.3.2-SNAPSHOT, C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\pom.xml, line 57, column 12
[WARNING]
[WARNING] Some problems were encountered while building the effective model for org.jboss.tools:openshift:pom:3.3.2-SNAPSHOT
[WARNING] 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin org.eclipse.tycho:target-platform-configuration @ line 57, column 12
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[WARNING]
[INFO] Computing target platform for MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.egit.core:3.3.2-SNAPSHOT @ C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\plugins\org.jboss.tools.openshift.egit.core\pom.xml
[INFO] Resolving dependencies of MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.egit.core:3.3.2-SNAPSHOT @ C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\plugins\org.jboss.tools.openshift.egit.core\pom.xml
[INFO] {osgi.os=win32, osgi.ws=win32, org.eclipse.update.install.features=true, osgi.arch=x86}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: org.jboss.tools.openshift.egit.core 3.3.2.qualifier
[ERROR] Missing requirement: org.jboss.tools.openshift.egit.core 3.3.2.qualifier requires 'bundle org.eclipse.jgit 4.6.1' but it could not be found
[ERROR]
[ERROR] See http://wiki.eclipse.org/Tycho/Dependency_Resolution_Troubleshooting for help.
[ERROR] Cannot resolve dependencies of MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.egit.core:3.3.2-SNAPSHOT @ C:\Users\jyoti.tumsare\Desktop\Jbosstools-Plugins\jbosstools-openshift-jbosstools-4.4.3.x\jbosstools-openshift-jbosstools-4.4.3.x\plugins\org.jboss.tools.openshift.egit.core\pom.xml: See log for details -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
I have added target platform also where org.eclipse.jgit-4.4.1 is available
still facing Error Missing requirement
> 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, 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
[JBoss JIRA] (JBDS-4368) Improve error reporting when an old Hyper-V Virtual Machine called "minishift is registered
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4368?page=com.atlassian.jira.plugin.... ]
Jan Richter closed JBDS-4368.
-----------------------------
> Improve error reporting when an old Hyper-V Virtual Machine called "minishift is registered
> -------------------------------------------------------------------------------------------
>
> Key: JBDS-4368
> URL: https://issues.jboss.org/browse/JBDS-4368
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: platform-installer
> Affects Versions: 10.4.0.AM2
> Reporter: Aurélien Pupier
> Assignee: Denis Golovin
> Fix For: 10.4.0.GA
>
>
> currently it is failing with this kind of error in log:
> {noformat}
> Mon, 24 Apr 2017 10:23:59 GMT-INFO: cdk - Copy C:\Users\AURELI~1\AppData\Local\Temp\7zS467E.tmp\minishift-3.0.0.Beta3.exe to c:\install\DevelopmentSuite-1.4.0-170424\cdk\bin\minishift.exe SUCCESS
> Mon, 24 Apr 2017 10:23:59 GMT-INFO: cdk - Set PATH environment variable to 'c:\install\DevelopmentSuite\cygwin\bin;C:\Program Files\Docker\Docker\Resources\bin;C:\ProgramData\Oracle\Java\javapath;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\PuTTY\;C:\HashiCorp\Vagrant\bin;C:\Program Files\nodejs\;C:\Program Files\Git\cmd;C:\DevelopmentSuite-1.2.0-161205-1202\jdk8\bin;C:\Program Files\OpenVPN\bin;C:\Program Files (x86)\Windows Kits\10\Windows Performance Toolkit\;C:\Program Files (x86)\Skype\Phone\;c:\DevelopmentSuite-1.3.0-172802\cdk\bin;c:\DevelopmentSuite-161220-1700\cdk\bin;c:\DevelopmentSuite-1.2.0-161205-1202\cdk\bin;C:\Ruby23-x64\bin;c:\install\DevelopmentSuite-1.1.0\cdk\bin;c:\install\DevelopmentSuite\cdk\bin;c:\install\DevelopmentSuite\cygwin\bin;C:\Program Files\Docker Toolbox;C:\install\apache-maven-3.3.9-bin\apache-maven-3.3.9\bin;C:\Program Files\Git\bin;C:\Users\Aurelien Pupier\AppData\Local\Microsoft\WindowsApps;C:\install\che;C:\minishift\minishift-windows-amd64.exe'
> Mon, 24 Apr 2017 10:23:59 GMT-INFO: cdk - Execute command c:\install\DevelopmentSuite-1.4.0-170424\cdk\bin\minishift.exe setup-cdk --force --default-vm-driver=hyperv
> Mon, 24 Apr 2017 10:24:03 GMT-ERROR: cdk - Error: Command failed: c:\install\DevelopmentSuite-1.4.0-170424\cdk\bin\minishift.exe setup-cdk --force --default-vm-driver=hyperv
> Mon, 24 Apr 2017 10:24:03 GMT-ERROR: cdk -
> Mon, 24 Apr 2017 10:24:03 GMT-ERROR: cdk failed to install: Error: Command failed: c:\install\DevelopmentSuite-1.4.0-170424\cdk\bin\minishift.exe setup-cdk --force --default-vm-driver=hyperv
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24307) Filter out Build config which have no git url configured in "Import OpenShift Application" dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24307?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24307:
-------------------------------------
Sprint: (was: devex #131 April 2017)
> Filter out Build config which have no git url configured in "Import OpenShift Application" dialog
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24307
> URL: https://issues.jboss.org/browse/JBIDE-24307
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: import_wizard, openshift_v3
> Fix For: 4.5.0.AM1
>
> Attachments: image-2017-04-25-15-22-03-598.png, image-2017-04-25-15-22-12-510.png
>
>
> it will avoid to have an error dialog just after
> !image-2017-04-25-15-22-12-510.png|thumbnail!
> Even more that thsi information is already retrieved to be displayed in "Build config details"
> !image-2017-04-25-15-22-03-598.png|thumbnail!
> Anothe rpossibility is to greyet out them with a tooltip explaining why we can't select them
> and/or disabled Next:Finish buttons
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-23710) Properites: Disable scaling on completed deployments
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23710?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23710:
-------------------------------------
Sprint: (was: devex #131 April 2017)
> Properites: Disable scaling on completed deployments
> ----------------------------------------------------
>
> Key: JBIDE-23710
> URL: https://issues.jboss.org/browse/JBIDE-23710
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Radim Hopp
> Assignee: Andre Dietisheim
> Labels: openshift_v3, properties
> Fix For: 4.5.0.AM1
>
>
> In web console, scaling completed deployments is disabled.
> In devstudio this option is enabled (in Deployments in Properties View) and after scaling up the completed deployment up (from 0 pods), the pods get scaled, but they are immediately scaled down automatically by openshift.
> Sometimes I also got this exception (but not allways):
> {noformat}
> !ENTRY org.jboss.tools.openshift.ui 4 0 2017-01-10 16:32:41.562
> !MESSAGE Unable to scale wildfly-1
> !STACK 0
> com.openshift.restclient.OpenShiftException: Exception trying to PUT https://10.40.4.205:8443/api/v1/namespaces/testproject/replicationcontrol... response code: 409 Operation cannot be fulfilled on replicationcontrollers "wildfly-1": the object has been modified; please apply your changes to the latest version and try again
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.createOpenShiftException(ResponseCodeInterceptor.java:114)
> at com.openshift.internal.restclient.okhttp.ResponseCodeInterceptor.intercept(ResponseCodeInterceptor.java:65)
> at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:190)
> at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:163)
> at okhttp3.RealCall.execute(RealCall.java:57)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:217)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:194)
> at com.openshift.internal.restclient.DefaultClient.execute(DefaultClient.java:183)
> at com.openshift.internal.restclient.DefaultClient.update(DefaultClient.java:275)
> at org.jboss.tools.openshift.core.connection.Connection.updateResource(Connection.java:451)
> at org.jboss.tools.openshift.internal.ui.handler.ScaleDeploymentHandler$2.run(ScaleDeploymentHandler.java:183)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
> I think we should do the same as web console -> disable scaling options on completed deployments.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-23473) Application wizard: weirdness and usability issues when using local template via URL
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23473?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23473:
------------------------------------------
[~rhopp] what you're refering to is the decorator issue aka issue #2. I should have mentioned that but I didnt fix that minor issue. If you agree that the main point in this issue, the near impossibility to type in a file url is fixed (which I assume it is watching your screencast), then I suggest that we file this 2nd issue to its own jira and keep this one here resolved.
> Application wizard: weirdness and usability issues when using local template via URL
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-23473
> URL: https://issues.jboss.org/browse/JBIDE-23473
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.2.AM2
> Reporter: Aurélien Pupier
> Assignee: Andre Dietisheim
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.4.Final, 4.5.0.AM1
>
> Attachments: image-2016-11-08-16-18-00-572.png, image-2016-11-08-16-18-00-572.png, local-template-validation-weirdness.ogv
>
>
> !image-2016-11-08-16-18-00-572.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (ERT-507) Have Docker connection working out of the box on Windows with latest Docker version [EBZ#516703]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-507:
---------------------------------------
Summary: Have Docker connection working out of the box on Windows with latest Docker version [EBZ#516703]
Key: ERT-507
URL: https://issues.jboss.org/browse/ERT-507
Project: Eclipse Release Train
Issue Type: Task
Components: Linux Tools
Reporter: Friendly Jira Robot
Created attachment 268365
Expose daemon option
with Version 17.03.1-ce-win12 (12058)
Channel: stable
d1db126
we need to "Expose daemon on tcp://localhost:2375 without TLS" to be able to connect to it using the Docker Explorer.
The comment on this option, which is not checked by default, is "Exposing daemon on TCP without TLS helps legacy clients connect to the daemon. it also makes yourself vulnerable to remote code execution attacks; Use with caution."
If not checked:
- in docker explorer there is an endless "pending connection"
- in wizard, when clicking "Test connection", there is a popup HttpHostConnectException (see attachment)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-23862) Server adapter: if "oc" in preferences is set to path with a " " syncing fails
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23862?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23862:
------------------------------------------
[~dbocharov] quite incredible, even with the PR, which seems fine to me, stuff still wont work on MacOS:
{code}
com.openshift.restclient.OpenShiftException: Does your OpenShift binary location exist? Error starting process: Cannot run program "oc" (in directory "/Users/adietish/Downloads/oc binaries/ocp-3.4.1.1.2"): error=2, No such file or directory
at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.startProcess(AbstractOpenShiftBinaryCapability.java:169)
at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:153)
at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPodLogRetrieval$PodLogs.getLogs(OpenShiftBinaryPodLogRetrieval.java:111)
at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPodLogRetrieval.getLogs(OpenShiftBinaryPodLogRetrieval.java:67)
at org.jboss.tools.openshift.internal.ui.job.PodLogsJob$ConsoleStreamPipe.runOCBinary(PodLogsJob.java:162)
at org.jboss.tools.openshift.internal.core.OCBinaryOperation.run(OCBinaryOperation.java:34)
at org.jboss.tools.openshift.internal.ui.job.PodLogsJob$ConsoleStreamPipe.run(PodLogsJob.java:152)
at java.lang.Thread.run(Thread.java:745)
Caused by: java.io.IOException: Cannot run program "oc" (in directory "/Users/adietish/Downloads/oc binaries/ocp-3.4.1.1.2"): error=2, No such file or directory
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1048)
at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.startProcess(AbstractOpenShiftBinaryCapability.java:165)
... 7 more
Caused by: java.io.IOException: error=2, No such file or directory
at java.lang.UNIXProcess.forkAndExec(Native Method)
at java.lang.UNIXProcess.<init>(UNIXProcess.java:247)
at java.lang.ProcessImpl.start(ProcessImpl.java:134)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1029)
... 8 more
{code}
In other words, your patch fixes things for Linux (since Windows always worked)?
Just for the info, I'm running a sun jvm
{code}
ava version "1.8.0_111"
Java(TM) SE Runtime Environment (build 1.8.0_111-b14)
Java HotSpot(TM) 64-Bit Server VM (build 25.111-b14, mixed mode)
{code}
> Server adapter: if "oc" in preferences is set to path with a " " syncing fails
> ------------------------------------------------------------------------------
>
> Key: JBIDE-23862
> URL: https://issues.jboss.org/browse/JBIDE-23862
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.Final
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Fix For: 4.5.0.AM1
>
> Attachments: ProcessMain.java
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months