[
https://issues.jboss.org/browse/JBIDE-24340?page=com.atlassian.jira.plugi...
]
Ondrej Dockal commented on JBIDE-24340:
---------------------------------------
In case of testing proxy on rhel, even if I did not follow exact steps to replicate the
environment, I consider this case to be done.
Proxy was thoroughly tested in central-ci environment that is full-fledged substitute to
enterprise environment (rhel vm-guest machine is registered, openshift connection created
and docker connection is at place).
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, integration-tests, openshift
Affects Versions: 4.4.4.Final
Environment: Linux (Fedora), Mac OS, Windows
Reporter: Ondrej Dockal
Assignee: Ondrej Dockal
Priority: Critical
Fix For: 4.5.x
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)