You can't look at just jenkins times and say there's a css compile problem. What else is going on in the box? Are there other builds? How is the system configured? Are you doing a lot of swapping? Is the CPU pegged during the compile? Is it using the same jdk you are, is it using the same ruby, ...
But ultimately my answer would be, "who cares?"
I'm not saying that to be crass or offensive, but it's just a CI build. If it takes 10 minutes to do something you do locally in 1 minute, it really doesn't matter. It doesn't hold up development, it really shouldn't be an impact to any of your processes at all. Ultimately if it takes Jenkins 10 minutes, it takes 10 minutes and you plan around it (if it is an impact).
Now if it was taking 1 minute on jenkins and 10 minutes on your local, well that deserves resolving as that impacts your development cycles.
But jenkins? I wouldn't really worry about trying to tune jenkins build times. Ultimately it will just cost money (more cpu, more memory, ...) but not give you much value in return.
Come meet me at the
LSNA!
