[JBoss JIRA] (JBDS-4106) Pre-configure the OpenShift server adapter
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-4106?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier updated JBDS-4106:
----------------------------------
Summary: Pre-configure the OpenShift server adapter (was: Pre-configure the OpenShift adapters)
> Pre-configure the OpenShift server adapter
> ------------------------------------------
>
> Key: JBDS-4106
> URL: https://issues.jboss.org/browse/JBDS-4106
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.1.0.GA
> Reporter: Aurélien Pupier
>
> When using the Developmen tsuite installer, it preconfigures the CDK adapter.
> The CDK instance is providing an OpenShift instance instance, it will be nice to provide the OpenShift adapter for this instance by default
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4106) Pre-configure the OpenShift adapters
by Aurélien Pupier (JIRA)
Aurélien Pupier created JBDS-4106:
-------------------------------------
Summary: Pre-configure the OpenShift adapters
Key: JBDS-4106
URL: https://issues.jboss.org/browse/JBDS-4106
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Feature Request
Components: platform-installer
Reporter: Aurélien Pupier
When using the Developmen tsuite installer, it preconfigures the CDK adapter.
The CDK instance is providing an OpenShift instance instance, it will be nice to provide the OpenShift adapter for this instance by default
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBDS-4102) Headless installation doesn't generate InstallConfigRecord.xml
by Lukáš Valach (JIRA)
[ https://issues.jboss.org/browse/JBDS-4102?page=com.atlassian.jira.plugin.... ]
Lukáš Valach closed JBDS-4102.
------------------------------
Verified in 10.2.0.AM2 (v20161011-0458-B6186). Headless installation works fine, thanks.
> Headless installation doesn't generate InstallConfigRecord.xml
> --------------------------------------------------------------
>
> Key: JBDS-4102
> URL: https://issues.jboss.org/browse/JBDS-4102
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer, upstream
> Affects Versions: 10.1.0.AM2
> Environment: Fedora 24, openjdk 1.8.0_102
> Reporter: Lukáš Valach
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM2
>
> Attachments: InstallConfigRecord_missing-terminal.png
>
>
> The installer should create InstallConfigRecord.xml in target folder, it works fine when I install devstudio in standard way (using GUI), but when I use headless installation the installer doesn't create InstallConfigRecord.xml in target folder.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23314) Implement "Add/remove" on OpenShift servers
by Aurélien Pupier (JIRA)
Aurélien Pupier created JBIDE-23314:
---------------------------------------
Summary: Implement "Add/remove" on OpenShift servers
Key: JBIDE-23314
URL: https://issues.jboss.org/browse/JBIDE-23314
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Reporter: Aurélien Pupier
it might implemented by leveraging the s2i binaries mode.
it will provide a fast way of deploying a new version to the OpenShift instance
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months
[JBoss JIRA] (JBIDE-23285) integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-23285:
---------------------------------------
OK, so on today's local devstudio qe call we agreed that we need to unify this - we will put the runtime versions/urls in our root pom, so that they're shared - this should avoid the situation where one test uses wf 10.0.0.CR1 and another one uses 10.0.0.Final.
Also, we will remove downloads and tests of very old runtimes that are not supported anymore.
> integration tests should share runtime downloads so that each test doesn't have to re-download the same runtime zips, and no longer use EOL'd runtimes
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23285
> URL: https://issues.jboss.org/browse/JBIDE-23285
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: integration-tests
> Affects Versions: 4.4.2.AM1
> Reporter: Nick Boldt
> Assignee: Martin Malina
>
> While running the integration tests today to investigate JBDS-4077, I discovered that:
> * org.jboss.ide.eclipse.as.ui.bot.test requires 11 runtimes, some of which are well past their EOL date [1]:
> {code}jboss-3.2.8.SP1 jboss-4.2.3.GA jboss-5.1.0.GA jboss-as-7.0.2.Final wildfly-10.0.0.CR2 wildfly-9.0.1.Final
> jboss-4.0.5.GA jboss-5.0.1.GA jboss-6.1.0.Final jboss-as-7.1.1.Final wildfly-8.2.0.Final{code}
> * org.jboss.tools.deltaspike.ui.bot.test requires 1 runtime, wildfly-10.0.0.Final
> [1] https://access.redhat.com/support/policy/updates/jboss_notes/eol vs. https://access.redhat.com/support/policy/updates/jboss_notes/
> So, three problems here:
> a) different tests use different versions of the same runtime (WFLY 10.0.0.CR2 vs. Final)
> b) different tests re-download their runtimes every time you do a clean, instead of fetching runtimes from a cache. So the same 160M of WFLY 10 gets downloaded twice.
> c) we still test on runtimes that have been EOL'd years ago, such as AS 4.0 and earlier.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 5 months