Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Schedule periodic Travis cron jobs on YARP's devel branch #17

Closed
PeterBowman opened this issue Apr 22, 2017 · 4 comments
Closed

Schedule periodic Travis cron jobs on YARP's devel branch #17

PeterBowman opened this issue Apr 22, 2017 · 4 comments

Comments

@PeterBowman
Copy link
Member

PeterBowman commented Apr 22, 2017

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):

@jgvictores
Copy link
Member

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?

@PeterBowman
Copy link
Member Author

@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.

@PeterBowman
Copy link
Member Author

PeterBowman commented May 21, 2017

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).

@PeterBowman
Copy link
Member Author

I deem this done, all repos listed in the issue's description have been enabled but:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants