[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-6463) JBT tests should (re)use shared requirements dir OUTSIDE hudson workspace

[Nick Boldt (JIRA)]

    [ https://jira.jboss.org/browse/JBIDE-6463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12537081#action_12537081 ] 

Nick Boldt commented on JBIDE-6463:
-----------------------------------

Yes, but we already have this in place for the uberbuilds (continuous, nightly jbt, nightly jbds) and it generally works fine (esp. since the reqs are cached and only dl'd once).

Would a bootstrap job be better, which dls all the reqs then kicks off downstream jobs?


> JBT tests should (re)use shared requirements dir OUTSIDE hudson workspace
> -------------------------------------------------------------------------
>
>                 Key: JBIDE-6463
>                 URL: https://jira.jboss.org/browse/JBIDE-6463
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng
>    Affects Versions: 3.2.0.M1
>            Reporter: Nick Boldt
>            Assignee: Denis Golovin
>
> Per request of JBQA-3313, we did the following to start using /home/hudson/static_build_env/jbds/requirements as the dir into which requirements are downloaded:
> 		<!-- https://jira.jboss.org/jira/browse/JBQA-3313 Use static, shared space outside workspace, instead of working directly in the workspace -->
> 		<if>
> 			<available file="/home/hudson/static_build_env/jbds" type="dir" />
> 			<then>
> 				<var name="requirement.build.root" unset="true" />
> 				<property name="requirement.build.root" value="/home/hudson/static_build_env/jbds/requirements" />
> 				<mkdir dir="${requirement.build.root}" />
> 			</then>
> 		</if>
> 		<echo level="debug">requirement.build.root = ${requirement.build.root}</echo>
> https://svn.jboss.org/repos/devstudio/trunk/releng/org.jboss.ide.eclipse.releng/builders/common/buildRequirements.xml
> Can the new harness in http://anonsvn.jboss.org/repos/jbosstools/trunk/requirements/ use the same shared dir? Currently it writes into the part of the workspace which contains SVN sources, which means it will most likely be overwritten every time SVN is refreshed (and have to be downloaded for every slave on which we build).

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