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/06/29 06:53] – chudler | vcs:gitlab_roster_usage [2020/09/16 15:59] – [Internal Repo-based Configuration] chudler | ||
---|---|---|---|
Line 1: | Line 1: | ||
=====Git Auto-creation===== | =====Git Auto-creation===== | ||
- | This is intended to be a simple process that does heavy lifting and stays out of the way. | + | This is a simple process that does some heavy lifting |
+ | |||
+ | |||
+ | =====How it Works===== | ||
+ | To get started, read [[vcs: | ||
For each course that is enabled for automation, by default: | For each course that is enabled for automation, by default: | ||
- | * A dedicated Namespace is created in Gitlab | + | * A dedicated Namespace is created in Gitlab, using course numbers by default. |
- | * All students | + | * Repo and Project resources |
- | * Nominated Graders, and others, | + | * Each student is given an individual |
- | * Customization | + | * Nominated Graders get appropriate access roles to Projects and the enclosing namespace. |
- | * Registrar data (rosters) are processed nightly, and data is refreshed every 1 hour | + | * Subsequent customization |
+ | * An administrative project is established for Instructors and TAs to optionally continue to modify the provisioner | ||
+ | * The tool is flexible and can be modified to suit different situations. | ||
+ | |||
+ | =====Accessing Repositories===== | ||
+ | The Gitlab server emails each individual at the time they are granted access to a resource. If you have not received an email with repository details and think that you should have, please write [[ techstaff@cs.uchicago.edu | Techstaff ]] and let us know. | ||
+ | |||
+ | Hints for finding a repository: | ||
+ | * The current server | ||
+ | * The entire namespace path is identical to the Course identifier, e.g., '' | ||
+ | * Use Gitlab built-in search if necessary | ||
======Controlling The Rosters====== | ======Controlling The Rosters====== | ||
- | The overall automation tool is controlled by Techstaff. However, | + | 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 |
- | 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/ Registrar data. | + | Because of the aforementioned |
- | It is also possible to specify partial information, | + | It is also possible to specify partial information, |
< | < | ||
Line 34: | Line 48: | ||
- ctopper | - ctopper | ||
</ | </ | ||
- | |||
An example to create course without any associated Registrar data is the same, but includes | An example to create course without any associated Registrar data is the same, but includes | ||
Line 60: | Line 73: | ||
[[More Roster Configuration Examples]] | [[More Roster Configuration Examples]] | ||
+ |
/var/lib/dokuwiki/data/pages/vcs/gitlab_roster_usage.txt · Last modified: 2020/09/16 16:17 by chudler