[JBoss JIRA] (JBIDE-24121) Update versionwatch for devstudio 11 - document/update known multiples & report upstream problems to Eclipse CVS, Help, WST
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24121?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-24121 at 5/9/17 12:13 PM:
-------------------------------------------------------------
New problem: performance when installing the latest CI to perform a version check.
So, need to experiment with performance of ssh mounts vs. http pulls
# devstudio@filem - use INSTALLER_NIGHTLY_FOLDER with correct ssh mount
# devstudio@wonka - use INSTALLER_NIGHTLY_FOLDER with correct ssh mount
# http://wonka - use INSTALLERS pointing at a specific folder (not latest) and specific installer (not latest)
# https://ds.rh - use INSTALLERS pointing at a specific folder (not latest) and specific installer (not latest)
was (Author: nickboldt):
New problem: performance.
So, need to experiment with performance of ssh mounts vs. http pulls
# devstudio@filem - use INSTALLER_NIGHTLY_FOLDER with correct ssh mount
# devstudio@wonka - use INSTALLER_NIGHTLY_FOLDER with correct ssh mount
# http://wonka - use INSTALLERS pointing at a specific folder (not latest) and specific installer (not latest)
# https://ds.rh - use INSTALLERS pointing at a specific folder (not latest) and specific installer (not latest)
> Update versionwatch for devstudio 11 - document/update known multiples & report upstream problems to Eclipse CVS, Help, WST
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24121
> URL: https://issues.jboss.org/browse/JBIDE-24121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, qa, versionwatch
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.AM1
>
> Attachments: Screenshot_2017-03-21_12-37-07.png, version-decreased.png
>
>
> {code}
> Version Watch - Summary Report: devstudio-11.0.0.AM1
> Multiple version issues
> Feature Problem Reference Version(s)
> Plugin Problem Reference Version(s)
> org.slf4j.api Multiple versions of same bundle found! 1.7.2.v20121108-1250 1.7.10.v20160921-1923
> org.apache.httpcomponents.httpcore Multiple versions of same bundle found! 4.3.3.v201411290715 4.4.4.v20161115-1643
> org.apache.httpcomponents.httpclient Multiple versions of same bundle found! 4.3.6.v201511171540 4.5.2.v20161115-1643
> Ignored (known issue)
> org.apache.lucene.core Multiple versions of bundle are expected and ignored - {3.5.0,5.4.1} 3.5.0.v20120725-1805 6.1.0.v20161115-1612
> javax.wsdl Multiple versions of bundle are expected and ignored - {1.5.1,1.6.2} 1.5.1.v201012040544 1.6.2.v201012040545
> com.jcraft.jsch Multiple versions of bundle are expected and ignored - {0.1.50,0.1.51} 0.1.53.v201508180515 0.1.54.v20170116-1932
> org.eclipse.jdt.annotation Multiple versions of bundle are expected and ignored - {1.1.0,2.1.0} 1.1.100.v20160418-1457 2.1.0.v20170119-1701
> org.objectweb.asm Multiple versions of bundle are expected and ignored - {4.0.0,5.0.1} 4.0.0.v201302062210 5.0.1.v201404251740
> org.apache.commons.logging Multiple versions of bundle are expected and ignored - {1.0.4,1.1.1} 1.0.4.v201101211617 1.1.1.v201101211721
> com.google.guava Multiple versions of bundle are expected and ignored - 13.0.0,15.0.0 15.0.0.v201403281430 18.0.0.v20161115-1643
> Version decreased issues
> Feature Problem Reference Version(s)
> org.eclipse.cvs Version 1.4.300.v20170126-1030 must be higher than 1.4.301.v20161124-1400 1.4.301.v20161124-1400
> org.eclipse.help Version 2.2.0.v20170126-1030 must be higher than 2.2.1.v20161124-1400 2.2.1.v20161124-1400
> Plugin Problem Reference Version(s)
> org.eclipse.cvs Version 1.4.300.v20170126-1030 must be higher than 1.4.301.v20161124-1400 1.4.301.v20161124-1400
> org.eclipse.wst.server.ui Version 1.5.306.v201610202117 must be higher than 1.5.307.v201611072017 1.5.307.v201611072017
>
> 7 issues found.{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24121) Update versionwatch for devstudio 11 - document/update known multiples & report upstream problems to Eclipse CVS, Help, WST
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24121?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-24121:
------------------------------------
New problem: performance.
So, need to experiment with performance of ssh mounts vs. http pulls
# devstudio@filem - use INSTALLER_NIGHTLY_FOLDER with correct ssh mount
# devstudio@wonka - use INSTALLER_NIGHTLY_FOLDER with correct ssh mount
# http://wonka - use INSTALLERS pointing at a specific folder (not latest) and specific installer (not latest)
# https://ds.rh - use INSTALLERS pointing at a specific folder (not latest) and specific installer (not latest)
> Update versionwatch for devstudio 11 - document/update known multiples & report upstream problems to Eclipse CVS, Help, WST
> ---------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24121
> URL: https://issues.jboss.org/browse/JBIDE-24121
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, qa, versionwatch
> Affects Versions: 4.5.0.AM1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.5.0.AM1
>
> Attachments: Screenshot_2017-03-21_12-37-07.png, version-decreased.png
>
>
> {code}
> Version Watch - Summary Report: devstudio-11.0.0.AM1
> Multiple version issues
> Feature Problem Reference Version(s)
> Plugin Problem Reference Version(s)
> org.slf4j.api Multiple versions of same bundle found! 1.7.2.v20121108-1250 1.7.10.v20160921-1923
> org.apache.httpcomponents.httpcore Multiple versions of same bundle found! 4.3.3.v201411290715 4.4.4.v20161115-1643
> org.apache.httpcomponents.httpclient Multiple versions of same bundle found! 4.3.6.v201511171540 4.5.2.v20161115-1643
> Ignored (known issue)
> org.apache.lucene.core Multiple versions of bundle are expected and ignored - {3.5.0,5.4.1} 3.5.0.v20120725-1805 6.1.0.v20161115-1612
> javax.wsdl Multiple versions of bundle are expected and ignored - {1.5.1,1.6.2} 1.5.1.v201012040544 1.6.2.v201012040545
> com.jcraft.jsch Multiple versions of bundle are expected and ignored - {0.1.50,0.1.51} 0.1.53.v201508180515 0.1.54.v20170116-1932
> org.eclipse.jdt.annotation Multiple versions of bundle are expected and ignored - {1.1.0,2.1.0} 1.1.100.v20160418-1457 2.1.0.v20170119-1701
> org.objectweb.asm Multiple versions of bundle are expected and ignored - {4.0.0,5.0.1} 4.0.0.v201302062210 5.0.1.v201404251740
> org.apache.commons.logging Multiple versions of bundle are expected and ignored - {1.0.4,1.1.1} 1.0.4.v201101211617 1.1.1.v201101211721
> com.google.guava Multiple versions of bundle are expected and ignored - 13.0.0,15.0.0 15.0.0.v201403281430 18.0.0.v20161115-1643
> Version decreased issues
> Feature Problem Reference Version(s)
> org.eclipse.cvs Version 1.4.300.v20170126-1030 must be higher than 1.4.301.v20161124-1400 1.4.301.v20161124-1400
> org.eclipse.help Version 2.2.0.v20170126-1030 must be higher than 2.2.1.v20161124-1400 2.2.1.v20161124-1400
> Plugin Problem Reference Version(s)
> org.eclipse.cvs Version 1.4.300.v20170126-1030 must be higher than 1.4.301.v20161124-1400 1.4.301.v20161124-1400
> org.eclipse.wst.server.ui Version 1.5.306.v201610202117 must be higher than 1.5.307.v201611072017 1.5.307.v201611072017
>
> 7 issues found.{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24322) Openshift publisher keeps getting more nested
by Dmitrii Bocharov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24322?page=com.atlassian.jira.plugi... ]
Dmitrii Bocharov commented on JBIDE-24322:
------------------------------------------
[~nickboldt] as i've said in the chat, this pr is not the cause of the test failures.
> Openshift publisher keeps getting more nested
> ---------------------------------------------
>
> Key: JBIDE-24322
> URL: https://issues.jboss.org/browse/JBIDE-24322
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Final
> Environment: - OS: Windows 7
> - JbossDev: 10.3.0.0
> - Openshift Client: 3.4
> - Openshift Enterprise: 3.4
> - Workspace location: it's inside a network drive
> Reporter: Rob Stryker
> Assignee: Dmitrii Bocharov
> Priority: Critical
> Labels: openshift_v3, server_adapter
> Fix For: 4.4.4.Final, 4.5.0.AM1
>
>
> During a POC, one of the requirements is that developers want to deploy/test their local changes inside a pod before to commit.
> We noticed that during the publishing or local change.
>
> The Publish function, always creates a nested deploy directory inside an existing one.
> For instance inside /opt/eap/standalone/deployments/
> 1st Publish:
> deploy/server.war/
> 2nd Publish:
> deploy/deploy/server.war/
> 3nd Publish:
> deploy/deploy/deploy/server.war/
>
> So with 3 publish, you end up with 3 deployed same application.
> This happen also inside the local workspaces for the synchronisation:
> .metadata/.plugins/org.jboss.ide.eclipse.as.core/poc-dev@jboss-eap70-openshift
> The EAP7 images is the jboss-eap70-openshift:latest.
>
> Do you have any idea why this happen?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24340) CDK3 tools works behind proxy - Test case
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24340?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24340:
----------------------------------
Description:
It is still impossible to test CDK 3 on central-ci and so, it is willing to test CDK 3 tools operated from devstudio via usage of proxy system settings on local machines.
Steps to follow:
1. Setup local firewall/network rules to simulate that machine resides in restricted network and requires proxy to utilize CDK3 features. ( [^create_proxy-test_env.sh] )
2. Download/install devstudio
3. Download CDK3 minishift binary and prepare the environemnt (run minishift setup-cdk)
4. ASSERT: Cannot subscribe minishift-rhel image during minishift start, can be done via cli
4. Set env. variable MINISHIFT_HTTP(S)_PROXY
5. Start devstudio, add new Container Development Environement server
6. Start server adapter
7. ASSERT: CDK tools are working properly - CDK started successfully
* rhel-image was subscribed
* docker image pulled
* log into openshift
was:
It is still impossible to test CDK 3 on central-ci and so, it is willing to test CDK 3 tools operated from devstudio via usage of proxy system settings on local machines.
Steps to follow:
1. Setup local firewall/network rules to simulate that machine resides in restricted network and requires proxy to utilize CDK3 features. ( [^create_proxy-test_env.sh] )
2. Download/install devstudio
3. Download CDK3 minishift binary and prepare the environemnt (run minishift setup-cdk)
4. ASSERT: Cannot subscribe minishift-rhel image during minishift start, can be done via cli
4. Set env. variable MINISHIFT_HTTP(S)_PROXY
5. Start devstudio, add new Container Development Environement server
6. Start server adapter
7. ASSERT: CDK tools are working properly - CDK started successfully
* rhel-image was subscribed
* docker image pulled
* openshift can be operated
> CDK3 tools works behind proxy - Test case
> -----------------------------------------
>
> Key: JBIDE-24340
> URL: https://issues.jboss.org/browse/JBIDE-24340
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdk, docker, openshift
> Affects Versions: 4.4.4.Final
> Environment: Linux (Fedora), Mac OS, Windows
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Fix For: 4.4.4.Final
>
> Attachments: create_proxy-test_env.sh
>
>
> It is still impossible to test CDK 3 on central-ci and so, it is willing to test CDK 3 tools operated from devstudio via usage of proxy system settings on local machines.
> Steps to follow:
> 1. Setup local firewall/network rules to simulate that machine resides in restricted network and requires proxy to utilize CDK3 features. ( [^create_proxy-test_env.sh] )
> 2. Download/install devstudio
> 3. Download CDK3 minishift binary and prepare the environemnt (run minishift setup-cdk)
> 4. ASSERT: Cannot subscribe minishift-rhel image during minishift start, can be done via cli
> 4. Set env. variable MINISHIFT_HTTP(S)_PROXY
> 5. Start devstudio, add new Container Development Environement server
> 6. Start server adapter
> 7. ASSERT: CDK tools are working properly - CDK started successfully
> * rhel-image was subscribed
> * docker image pulled
> * log into openshift
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24340) CDK3 tools works behind proxy - Test case
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24340?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24340:
----------------------------------
Description:
It is still impossible to test CDK 3 on central-ci and so, it is willing to test CDK 3 tools operated from devstudio via usage of proxy system settings on local machines.
Steps to follow:
1. Setup local firewall/network rules to simulate that machine resides in restricted network and requires proxy to utilize CDK3 features. ( [^create_proxy-test_env.sh] )
2. Download/install devstudio
3. Download CDK3 minishift binary and prepare the environemnt (run minishift setup-cdk)
4. ASSERT: Cannot subscribe minishift-rhel image during minishift start, can be done via cli
4. Set env. variable MINISHIFT_HTTP(S)_PROXY
5. Start devstudio, add new Container Development Environement server
6. Start server adapter
7. ASSERT: CDK tools are working properly - CDK started successfully
* rhel-image was subscribed
* docker image pulled
* openshift can be operated
was:
It is still impossible to test CDK 3 on central-ci and so, it is willing to test CDK 3 tools operated from devstudio via usage of proxy system settings on local machines.
Steps to follow:
1. Setup local firewall/network rules to simulate that machine resides in restricted network and requires proxy to utilize CDK3 features. ( [^create_proxy-test_env.sh] )
2. Download/install devstudio
3. Download CDK3 minishift binary and prepare the environemnt (run minishift setup-cdk)
4. Set env. variable MINISHIFT_HTTP(S)_PROXY
5. Start devstudio, add new Container Development Environement server
6. Start server adapter
7. Assert that cdk tools are working properly (cdk started, openshift can be operated, docker can pull image, etc...)
> CDK3 tools works behind proxy - Test case
> -----------------------------------------
>
> Key: JBIDE-24340
> URL: https://issues.jboss.org/browse/JBIDE-24340
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: cdk, docker, openshift
> Affects Versions: 4.4.4.Final
> Environment: Linux (Fedora), Mac OS, Windows
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Priority: Critical
> Fix For: 4.4.4.Final
>
> Attachments: create_proxy-test_env.sh
>
>
> It is still impossible to test CDK 3 on central-ci and so, it is willing to test CDK 3 tools operated from devstudio via usage of proxy system settings on local machines.
> Steps to follow:
> 1. Setup local firewall/network rules to simulate that machine resides in restricted network and requires proxy to utilize CDK3 features. ( [^create_proxy-test_env.sh] )
> 2. Download/install devstudio
> 3. Download CDK3 minishift binary and prepare the environemnt (run minishift setup-cdk)
> 4. ASSERT: Cannot subscribe minishift-rhel image during minishift start, can be done via cli
> 4. Set env. variable MINISHIFT_HTTP(S)_PROXY
> 5. Start devstudio, add new Container Development Environement server
> 6. Start server adapter
> 7. ASSERT: CDK tools are working properly - CDK started successfully
> * rhel-image was subscribed
> * docker image pulled
> * openshift can be operated
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months