[jbosstools-issues] [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
Nick Boldt (JIRA)
issues at jboss.org
Wed Feb 8 13:09:00 EST 2017
[ https://issues.jboss.org/browse/JBIDE-23285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13360675#comment-13360675 ]
Nick Boldt edited comment on JBIDE-23285 at 2/8/17 1:08 PM:
------------------------------------------------------------
Many jbosstools jobs in BosMW Jenkins set this maven property, including reddeer_master and jbosstools-server_master:
{code}download.cache.directory=/home/hudson/static_build_env/jbds/download-cache{code}
But I can't find any pom.xml files in jbosstools-* projects, or the parent pom, or the jbosstools-maven-plugins, where this property is used.
So maybe we no longer use this folder?
I've moved the contents of the folder out and have kicked a couple jobs to see if the artifacts are recreated:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/jbosstools-server_master/1437/
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/reddeer_master/899/
was (Author: nickboldt):
Many jbosstools jobs in BosMW Jenkins set this maven property, including reddeer_master and jbosstools-server_master:
{code}download.cache.directory=/home/hudson/static_build_env/jbds/download-cache{code}
But I can't find any pom.xml files in jbosstools-* projects, or the parent pom, or the jbosstools-maven-plugins, where this property is used.
So maybe we no longer use this folder?
> 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
> Fix For: 4.4.3.Final
>
>
> 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
(v7.2.3#72005)
More information about the jbosstools-issues
mailing list