On 7/29/12 09:03 , Sami Tikka wrote:
Rich Pixley <rich.pix...@palm.com> kirjoitti 28.7.2012 kello 0.28:
You just have to understand that jenkins doesn't really do much in the way of
work space management so hosed builds mean you'll have to clear the workspace
and start all over from scratch.
Jenkins does have the option of clearing the workspace at the beginning of the
build. It is usually there in the SCM (= version control) settings and is
usually off.
I haven't found that yet. Core jenkins apparently doesn't have that
ability, although it would seem to be core functionality.
And from my perspective, manual clearing is extremely minimal support.
It would appear that jenkins is primarily based around a bunch of much, much,
much smaller builds than something like oe so there are likely to be some
scaling issues. Eg, I'm finding that stuff like clearing the workspace take
long enough that jenkins thinks they've failed.
Interesting. Could you elaborate? I wasn't aware of any time limits in Jenkins
builds. I have a Jenkins which runs 24 hour performance tests and Jenkins has
never failed it because it runs too long.
I'm not sure what else to say. I click "clear workspace', it runs for a
while, I can see the disk space being cleared, and then it fails with a
time out.
A typical oe build directory can run 30gig per device and you may well
build for 5 devices. That's a lot of disk space which takes time to
deallocate.
--rich
