[
https://issues.jboss.org/browse/JBIDE-11155?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-11155:
------------------------------------
Problem w/ caching .m2 repo is that sometimes that gets corrupted. Reusing a corrupt repo
would cause subsequent builds to fail. Currently, if a build fails due to corrupt m2 repo,
chances are good the repin will be fine. If we start caching .m2 folders for each job, we
will also need to manually purge these folders if/when they get corrupted. Just something
to consider for downstream maintenance. :)
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