Closed PeterBowman closed 7 years ago
Sounds like a great idea!
For teo-main I activated a daily job on master via web. I understand this can be done via .travis
? Could you insert the magic lines on any .travis
so it's just copy+paste for me on the rest of the repos?
@jgvictores done at roboticslab-uc3m/kinematics-dynamics@4362843 and scheduled to run weekly on local develop branch. Please take a look at roboticslab-uc3m/kinematics-dynamics@677eeab, too.
YARP's devel already requires CMake +3.0, thus builds for yarp-devices are currently erroring. Pulling packages from ppa:kalakris/cmake is not an option since it stalled at 2.8.11. Looks like we need either to:
I'd like to remark that we no longer need to add a sudo apt-get install cmake
and, in spite of what official packages indicate, the default CMake version installed is 3.2.2 at the time of writing. Proof at https://travis-ci.org/roboticslab-uc3m/kinematics-dynamics/jobs/234523759 (L277), (L307).
I deem this done, all repos listed in the issue's description have been enabled but:
Following the lines of this comment at roboticslab-uc3m/teo-main#8, and also with #7 (latest-YARP policy) and #16 (YARP deprecations striking out of nowhere) in mind, it might be worth running periodic builds for each repo - say, once a week? - that would fetch YARP's devel branch to keep up with any breaking changes being prepared for the next release. The reasoning behind this is simple: use Travis' mechanisms to warn us against upcoming trouble even if nobody is keeping an eye on YARP's development progress. Such issues will surely arise at stale projects (like asibot-main was until quite recently).
One may use the
TRAVIS_EVENT_TYPE
default environment variable to differentiate between the usual push jobs and the cron ones.List of repos on which cron builds have been enabled (roboticslab-uc3m at travis-ci.org):