[jbosstools-issues] [JBoss JIRA] Commented: (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:comment-tabpanel&focusedCommentId=12466654#action_12466654 ] 

Nick Boldt commented on JBDS-662:
---------------------------------

By having one be the upstream build of the other. JBT runs, then kicks a JBDS build thereafter. It's not a guarantee for ad hoc builds kicked by you, me, Denis, or others, but it's a fairly effective tool otherwise. 

If this caching policy becomes too big a nightmare I can easily disable it in future.

Frankly, I'd rather see us create a p2 repo (mirrored from Eclipse.org sources) for our dependencies and build against that, rather than needing to download and cache all these 3rd party zips. 

Obviously that's only a partial solution since other deps aren't available as p2 artifacts...

> 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