Re:Advantages of monolithic version control
by skovorodkin on Tuesday February 13, 2018 @06:09AM
(#16366255)
> Travis ci expects a single file at the root of the project and so does gitlab ci
GitLab has a related issue to support "Several .gitlab-ci.yml for monorepos" (https://gitlab.com/gitlab-org/gitlab-ce/issues/18157).
Re:Advantages of monolithic version control
by connorshea on Tuesday February 13, 2018 @01:21PM
(#16369391)
We also have an issue for running jobs only when modifications are made to a given file or files in a directory, it's tentatively scheduled for 10.7 (April's release).
Re:Advantages of monolithic version control
by connorshea on Tuesday February 13, 2018 @01:20PM
(#16369380)
Not Sid, but thanks for being a fan ;)
Let's say I want a small application with flask and angular.
I create a single repo for both flask and angular. I put everything flask in one sub folder called backbend and I put everything angular in another folder called frontend
WIP here: https://github.com/kusl/flaskexperiment or https://git.sr.ht/%7Ekus/flaskexperiment/
Now the problems are just starting: how do I set up ci for all my projects? Travis ci expects a single file at the root of the project and so does gitlab ci (hi sid, big fan)
I am sad I can't talk to the experts at Google about how they navigated these problems. I understand Google has many enemies that are constantly trying to exploit whatever but I still wish we could have a more open conversation here.