Too long CI execution time
Static source code analysis tool for C and C++ code
Brought to you by:
danielmarjamaki
Menu
▾
▴
We have too long CI execution time. I think it can be acceptable if it finish in 4-5 minutes. More than 30 minutes is unacceptable!
I believe we need to split up the testing. A quick test can be executed by AppVeyor/Travis on each commit. It should contain the MUST HAVE tests.
I do not want to remove the other tests. I suggest that we run those tests on the daca@home workers. The question I see is how we best publish this. If we just publish the results on cppcheck.osuosl.org there is a risk that failures will go unnoticed for days. Maybe we can send email to everybody that made commits since the failures started?
Do you have some ideas/feedback?
Perhaps Travis cron jobs could be used? https://docs.travis-ci.com/user/cron-jobs/
I only know what I've googled about them, but it looks like you can check in travis.yml if it is a cron job and then choose to run extra checks. Then we wouldn't have to worry about how to publish the results.