vcs:gitlab_roster_usage
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
vcs:gitlab_roster_usage [2020/09/16 15:36] – [Accessing Repositories] chudler | vcs:gitlab_roster_usage [2020/09/16 15:59] – [Internal Repo-based Configuration] chudler | ||
---|---|---|---|
Line 26: | Line 26: | ||
======Controlling The Rosters====== | ======Controlling The Rosters====== | ||
- | The overall automation tool is controlled by Techstaff. However, online customization of repository and project details are available to instructors and other course staff. | + | The overall automation tool is controlled by Techstaff. It must be enabled **before** you can modify the provisioner' |
- | ====Internal | + | =====Repo-based |
- | Before | + | Before the automations creates the first repository, it can be configured to read data that is published in **your own** secure Gitlab repository. |
- | Every hour, the automations bot will checkout the head of your '' | + | Every hour, the automations bot will checkout the head of your '' |
- | Because of Roster Config Merging, you typically only need to //augment// the Registrar' | + | Because of the aforementioned |
- | It is also possible to specify partial information, | + | It is also possible to specify partial information, |
< | < |
/var/lib/dokuwiki/data/pages/vcs/gitlab_roster_usage.txt · Last modified: 2020/09/16 16:17 by chudler