[jbosstools-issues] [JBoss JIRA] Resolved: (JBDS-662) centralize requirements folder on in /home/hudson/hudson_workspace/workspace/jbosstools-jbdevstudio-REQUIREMENTS

[Nick Boldt (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBDS-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt resolved JBDS-662.
-----------------------------

    Fix Version/s:     (was: 2.0.1)
       Resolution: Done


For the moment, this is enabled for trunk builds, but not for maintenance. Seems to be working as long as we don't run both JBDS 2.1 and JBT 3.1 at the same time.

I don't plan to roll this out to the maintenance branch to avoid problems w/ versions, though the cache does currently have both sets of requirements. 

Caching system also works on my local box to save bandwidth; I run local builds with devstudio-trunk/releng/o.**.releng/hudson/loc.sh

> centralize requirements folder on in /home/hudson/hudson_workspace/workspace/jbosstools-jbdevstudio-REQUIREMENTS
> ----------------------------------------------------------------------------------------------------------------
>
>                 Key: JBDS-662
>                 URL: https://jira.jboss.org/jira/browse/JBDS-662
>             Project: Developer Studio
>          Issue Type: Task
>    Affects Versions: LATER
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> To avoid meltdowns like we had in JBQA-2144, to reduce disk usage, and to speed up the rollout of new hudson jobs, I propose we create two folders:
>  /home/hudson/hudson_workspace/workspace/jbosstools-3.0-jbdevstudio-2.0-REQUIREMENTS
>  /home/hudson/hudson_workspace/workspace/jbosstools-3.1-jbdevstudio-2.1-REQUIREMENTS
> In there, we will place a copy of all the requirements used by the paired builds, and instead of burning time and bandwidth fetching the 3G of zips every time we start a new job, we'll simply symlink to that folder so new reqs will be added. 
> cd /home/hudson/hudson_workspace/workspace/jbosstools-nightly-3.0.x/jbds-build
> ln -s  /home/hudson/hudson_workspace/workspace/jbosstools-3.0-jbdevstudio-2.0-REQUIREMENTS requirements
> Thus, for the 4 parallel jobs for JBDS2.0.0/2.0.1 & JBT3.0.0/3.0.1, we'll use about 3G of disk instead of 12. For the 2 parallel jobs for JBDS2.1.0 & JBT3.1.0, we'd save 3G.
> For the case where this is run on a local box (eg., my own Hudson) we just need a catch that says "if  /home/hudson/hudson_workspace/workspace/jbosstools-3.1-jbdevstudio-2.1-REQUIREMENTS doesn't exist, create it, symlink to it, and begin downloading" .. of course the path there would be ~/.hudson/jobs/jbosstools-3.1-jbdevstudio-2.1-REQUIREMENTS, but it's the same relative path.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira