My jenkins install is working properly just that the phpunit+coverage on my code takes 5 minutes finish – because of too many files.
For me, it’s too much wait for just knowing if my last commit broke the build or not.
Is there a way I can run a special build (or scheduled) when jenkins is idle and while only in that build it will create phpunit code coverage reports?
I could run phpunit -c with-coverage.xml in cron but that is isolated from jenkins, it does not refresh jenkin’s job home page.
This is a common general problem: you want a first-tier build to quickly tell you if you’ve broken the application and a second-tier build to perform deeper analysis. Things that take more time in this latter build include
You can achieve this using two separate Jenkins projects–each executing an appropriate Ant task–where the second build is dependent on the first build’s success. I believe you can even have the first-tier build pass artifacts (e.g. junit.xml) to the second-tier build, but I haven’t had the time to experiment with this yet.
Unfortunately, this is a half-answer. I know you can do it, but I haven’t done it myself, nor can I tell you step-by-step how to do it. Hopefully this gives you enough pointers to get you started.