vcs:gitlab_roster_usage
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
vcs:gitlab_roster_usage [2020/06/29 06:57] – chudler | vcs:gitlab_roster_usage [2020/09/16 16:17] (current) – 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, | + | * Subsequent customization |
+ | * An administrative project is established for Instructors | ||
+ | * The tool is flexible and can be modified to suit different situations. | ||
=====Accessing Repositories===== | =====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, please | + | 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 |
- | Hints: | + | Hints for finding a repository: |
- | * The current server is named [[ https:// | + | * The current server is named [[ https:// |
- | * The entire namespace path is identical to the Course identifier, e.g., '' | + | * 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, 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 |
- | 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, |
+ | |||
+ | =====File Format===== | ||
+ | |||
+ | Files must end in a '' | ||
+ | |||
+ | All structures must begin with a key that uniquely and globally identifies the course and offering that is currently being taught. The format of the key is opaque to the provisioner and is not parsed, and you are also not restricted to choosing from known keys. Therefore, you are able to create repositories that have no upstream datasource, for testing, future use, and other devices. The example below uses a familiar key structure intended for real courses. | ||
< | < | ||
Line 42: | Line 55: | ||
</ | </ | ||
+ | When your configuration is split across multiple files, merging takes place on the basis of the key. So, be sure to use the same key in different '' | ||
- | An example to create course without any associated Registrar data is the same, but includes | + | An example to create |
- | more memberships | + | |
< | < | ||
Line 63: | Line 76: | ||
</ | </ | ||
- | ==Configuration Merging== | + | As the example shows, the automations will consume this structure and map the groups of people (" |
+ | |||
+ | ===Configuration Merging=== | ||
Techstaff will augment any configuration you provide with roster data from the University Registrar. The union of memberships is considered, and scalar values are overridden by your values. | Techstaff will augment any configuration you provide with roster data from the University Registrar. The union of memberships is considered, and scalar values are overridden by your values. | ||
[[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