[
https://issues.jboss.org/browse/JBIDE-11155?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11155:
------------------------------------
Now doing this to cache a copy of the ~/.m2 repo folder too. I figure a quick NFS copy
will trump fetching everything from maven central every time we build, right?
{code}
# store a copy of this project's sources so it can be usd to bootstrap other projects
mkdir -p /home/hudson/static_build_env/jbds/tools/sources/build/trunk/
rsync -aqrz ${WORKSPACE}/sources/*
/home/hudson/static_build_env/jbds/tools/sources/build/trunk/
# store a copy of this project's ~/.m2 folder so it can be used to bootstrap other
projects
mkdir -p /home/hudson/static_build_env/jbds/tools/sources/m2-repository/trunk/
rsync -aqrz ${WORKSPACE}/m2-repository/*
/home/hudson/static_build_env/jbds/tools/sources/m2-repository/trunk/
{code}
Awaiting respin:
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.target-platform/ >=362
consider caching svn sources outside Jenkins workspaces
-------------------------------------------------------
Key: JBIDE-11155
URL:
https://issues.jboss.org/browse/JBIDE-11155
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 3.3.0.Beta3
Reporter: Nick Boldt
Assignee: Nick Boldt
Fix For: 3.3.0.Beta3
From JBIDE-10974:
> 9. Every change in build component triggers full rebuild for all components
9. This could be fixed by instead of watching the /build folder in SVN for changes, we
simply fetch it using `svn co` or `svn up` as a prelim step in the job.
Perhaps taking this a step further, we could fetch the whole SVN tree and store it
outside the workspaces so that jobs would simply re-use local shared space instead of
clean-fetching everything every time they run on a new slave.
This would of course make jobs "more tied to infrastructure" and "harder
to build the same way offline" but that's the price you pay for optimizing for
speed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira