[
https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugi...
]
Nick Boldt edited comment on JBIDE-23285 at 10/5/16 12:34 PM:
--------------------------------------------------------------
I was not suggesting we remove old server adapters, only that we might want to performance
tune the suite of integration tests by NOT running the old ones in order to save time and
disk space.
To answer the question of how much disk is used, consider this 2.2G m2 repo cache being
copied over into a tests/org.jboss.tools.*/target/ folder a dozen times.
{code}
cd ~/.m2/repository/.cache/maven-download-plugin; du -sch *.zip | sort
105M jboss-5.0.1.GA-jdk6.zip
108M jboss-seam-2.2.2.Final.zip
127M wildfly-8.2.0.Final.zip
128M jboss-5.1.0.GA-jdk6.zip
128M jboss-as-7.1.1.Final.zip
128M wildfly-9.0.1.Final.zip
132M wildfly-10.0.0.Final.zip
138M wildfly-10.0.0.CR2.zip
175M jboss-as-distribution-6.1.0.Final.zip
187M GateIn-3.5.0.Final-jbossas7.zip
192M GateIn-3.4.0.Final-jbossas5.zip
54M jboss-3.2.8.SP1.zip
60M hibernate-distribution-3.6.10.Final-dist.zip
61M hibernate-release-4.3.11.Final.zip
64M hibernate-distribution-3.5.3-Final-dist.zip
76M jboss-as-7.0.2.Final.zip
78M jboss-4.0.5.GA.zip
8.2M 10.x.zip
88M jboss-seam-2.0.2.SP1.zip
89M jboss-seam-distribution-2.3.0.Final-dist.zip
96M jboss-4.2.3.GA-jdk6.zip
2.2G total{code}
was (Author: nickboldt):
I was not suggesting we remove old server adapters, only that we might want to performance
tune the suite of integration tests by NOT running the old ones in order to save time and
disk space.
To answer the question of how much disk is used, consider this cache 2.2G cache being
copied over into a tests/org.jboss.tools.*/target/ folder a dozen times.
{code}
cd ~/.m2/repository/.cache/maven-download-plugin; du -sch *.zip | sort
105M jboss-5.0.1.GA-jdk6.zip
108M jboss-seam-2.2.2.Final.zip
127M wildfly-8.2.0.Final.zip
128M jboss-5.1.0.GA-jdk6.zip
128M jboss-as-7.1.1.Final.zip
128M wildfly-9.0.1.Final.zip
132M wildfly-10.0.0.Final.zip
138M wildfly-10.0.0.CR2.zip
175M jboss-as-distribution-6.1.0.Final.zip
187M GateIn-3.5.0.Final-jbossas7.zip
192M GateIn-3.4.0.Final-jbossas5.zip
54M jboss-3.2.8.SP1.zip
60M hibernate-distribution-3.6.10.Final-dist.zip
61M hibernate-release-4.3.11.Final.zip
64M hibernate-distribution-3.5.3-Final-dist.zip
76M jboss-as-7.0.2.Final.zip
78M jboss-4.0.5.GA.zip
8.2M 10.x.zip
88M jboss-seam-2.0.2.SP1.zip
89M jboss-seam-distribution-2.3.0.Final-dist.zip
96M jboss-4.2.3.GA-jdk6.zip
2.2G total{code}
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)