Gitlab
 |
Please help improve this article or section by editing it for formatting, grammar, punctuation, accuracy and citation. Further information might be found on the talk page. |
 |
Please help improve this article or section by expanding it. Further information might be found on the talk page. |
| |
Maintainers of this service should update the page Visit the talk page to discuss the proposal. |
| Gitlab | |
| IP Address(es): | 128.153.145.46 |
| Contact Person: | Jared Dunbar |
| Last Update: | Fall 2016 |
| Services: | Gitlab - Git and Build Testing Services |
| LDAP Support: | yes |
| Hostname: | gitlab.cslabs.clarkson.edu |
| Operating system: | Debian 8 |
| NIC 1: | Clarkson Network MAC: ? IP: 128.153.145.46 |
| CPU: | 2x AMD Opteron 6220 (16 cores total) |
| RAM: | 64GB |
 |
This service has been retired. This page refers to a service that has been retired and is no longer operational. Content here is kept for archival and informational purposes only, and may not reflect the current status of operation. Became Starkist, after backing up the stored repositories to cold backups. A GoGS server called simply Git fulfilled its role. Any maintainer may restore this service; remove this notice upon doing so. |
GitLab was a git repository host, with additional features including an integrated CI system, issue trackers, and more. It can build your C, C++, LaTeX, Java (8?), python and python3 via a .gitlab-ci.yml
The LDAP login is for COSI members, and is the same login as everything else. Students should use a standard account after it has been set up for them by their TA or a GitLab admin.
CI/builds
See https://docs.gitlab.com/ce/ci/README.html for more information about GitLab CI. If you use a makefile, a simple .gitlab.yml might be:
job make:
script: "make"
Once you add that to your commits, it will build them. Don't expect it to build your older commits that don't have that file though, or the makefile.
Install
Installation of GitLab should be done with Omnibus: https://docs.gitlab.com/omnibus/README.html. We use Let's Encrypt for the certificates. Use certbot with the webroot config, and edit the nginx configs to forward /.well-known to the configured webroot use the new cert.
