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

[ https://jira.jboss.org/jira/browse/JBDS-662?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBDS-662: --------------------------------- First pass added to /devstudio-trunk/releng/org.jboss.ide.eclipse.releng/builders/common/buildRequirements.xml#cleanRequirements, lines 61-98: <!-- JBDS-662: use a central requirements bucket to save bandwidth and disk, if running on linux/macosx/etc. --> <if> <and> <os family="unix" /> <not> <!-- If requirements cache dir does not exist, eg., ~/.hudson/jobs/devstudio-nightly-2.0.x/workspace/jbds-build/requirements or /home/hudson/hudson_workspace/workspace/jbosstools-release-3.0.x/jbds-build/requirements --> <available file="${requirement.build.root}" type="dir" /> </not> </and> <then> <!-- find the hudson jobs dir, eg. ~/.hudson/jobs/ or /home/hudson/hudson_workspace/ --> <property name="HUDSON_JOBS_DIR" location="${requirement.build.root}/../../../../" /> <!-- create a central cache folder; should we use one cache for 3.1.x and one for 3.0.x? --> <property name="SHARED_REQUIREMENTS_DIR" value="${HUDSON_JOBS_DIR}/jbosstools-jbdevstudio-REQUIREMENTS"/> <if> <and> <available file="${HUDSON_JOBS_DIR}" type="dir" /> <not> <available file="${SHARED_REQUIREMENTS_DIR}" type="dir" /> </not> </and> <then> <mkdir dir="${SHARED_REQUIREMENTS_DIR}" /> </then> </if> <!-- then create a symlink within the build's workspace to the cache --> <symlink link="${requirement.build.root}" resource="${SHARED_REQUIREMENTS_DIR}" /> </then> </if> <!-- TODO: verify if using a shared requirements cache will cause problems with overlapping builds doing this cleanup step --> -- 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