Branching and CI builds in superbuild repos

roboticslab-uc3m / questions-and-answers

A place for general debate and question&answer

https://robots.uc3m.es/developer-manual/appendix/repository-index.html

2 stars 0 forks source link

Branching and CI builds in superbuild repos #53

Closed PeterBowman closed 6 years ago

PeterBowman commented 6 years ago

As usual, our superbuild repos follow the GitFlow workflow:

We set develop as the default branch, and occasionally merge it into master. CI builds are set on a daily basis per https://github.com/roboticslab-uc3m/questions-and-answers/issues/17#issuecomment-314855633. In contrast to each orchestrated subrepo (e.g. kinematics-dynamics, yarp-devices, etc.), <robot>-main are tested against YARP's master and their own master branch. However, the CI badge at root README.md points at develop (ref, which is not covered by cron jobs).

Two issues:

Do we need a master/develop pair here? I'd say yes for now, perhaps until we start a discussion about GH project releases and packaging.
Switch daily CI jobs to develop? Change the default branch?

PeterBowman commented 6 years ago

Ideas, as spoken with @jgvictores:

put two badges in README.md: master + develop
set (daily?) Travis cron jobs on develop, too

PeterBowman commented 6 years ago

set (daily?) Travis cron jobs on develop, too

Done in Travis settings, with option Do not run if there has been a build in the last 24h. I'm not sure if this check refers to the branch being built, or to all branches. In the second case, we'll (almost) never run a job on develop because there is already one set on master. I'll take a look in one day or two.

put two badges in README.md: master + develop

Done. Prefer https://img.shields.io/ to Travis badges, the former allows custom labels.

PeterBowman commented 6 years ago

I'm not sure if this check refers to the branch being built, or to all branches.

The former, which is nice. Done!

PeterBowman commented 3 years ago

set (daily?) Travis cron jobs on develop, too

Some time ago cron jobs on master were disabled because of https://github.com/roboticslab-uc3m/questions-and-answers/issues/87. Now, I'm configuring crons on a monthly basis - we don't really need them to run any more often - and master is targeted (again) instead of develop because of https://github.com/roboticslab-uc3m/questions-and-answers/issues/88.