Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-11155

consider caching svn sources outside Jenkins workspaces


    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Major Major
    • 4.0.0.Alpha2
    • 3.3.0.Beta3
    • build
    • None

      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.

            nickboldt Nick Boldt
            nickboldt Nick Boldt
            0 Vote for this issue
            3 Start watching this issue