- Edited
Hello,
I fail to grasp the idea behind the git integration.
In the management tutorial, we setup the following files:
~/artiq-master
/device_db.py
/repository
(bare git repo)/hooks
/post-receive
~/artiq-work
(regular git repo)/mgmt_tutorial.py
We register ~/artiq-master/repository
as origin of ~/artiq-work
, allowing us to push commits from ~/artiq-work
to ~/artiq-master/repository
. When ~/artiq-master/repository
receives a commit, the post-receive
hook is triggered, which performs a rescan through the committed files.
We run artiq_master
with the git flag -g
inside the ~/artiq-master
directory to interface with the artiq hardware and schedule the experiments.
Initially, I thought why not just have one git repository and use a post-push hook, but apparently there is no git support for such hook.
Second, maybe the idea of using two git repositories should promote the master-client architecture, but then, why not go "full-server" and have some gitlab runner executing the experiments?
So what is the reasoning behind using two git repositories to integrate ARTIQ into git? What is the suggested workflow?