Difference between revisions of "Gitlab"

From CSLabsWiki
Jump to: navigation, search
(Git Stuff)
Line 65: Line 65:
  
 
I would start with a web server, gitlab-ci, gitlab-ci-runner, and git installed on the system. Install certs, and then woo. I am not sure how exactly it was created unfortunately.
 
I would start with a web server, gitlab-ci, gitlab-ci-runner, and git installed on the system. Install certs, and then woo. I am not sure how exactly it was created unfortunately.
 +
 +
[[Category:Web Service]]

Revision as of 11:56, 9 June 2016

Gitlab
IP Address(es): 128.153.145.46
Contact Person: Jared Dunbar
Last Update: April 2016
VM Host (Physical): felix
Host VM: Gitlab
Services: Gitlab - Git and Build Testing Services
LDAP Support: yes


Hostname: [1]
Operating system: Debian
LDAP Support: no
Development Status: Stable
Status: running


GitLab is a git server and test build server. It can build your C, C++, LaTeX, Java (8?), python and python3 via a makefile and a .gitlab-ci.yml

To log in, make sure that you either accept Talos as a CA or that you have manually added GitLab as an exception to your browser. You will need to accept Talos as your CA to access gitlab via git unless you toggle the httpVerify flag in Git to false.

LDAP is the same as using your ldap username and password on the COSI network on the lab machines, and Local accounts are reserved for special purposes and the (non-netwokred) admins.

Build

To have a buildable commit, make sure that you already have a makefile that Make detects, then use the following to execute it internally:

.gitlab-ci.yml

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. If you are not using a makefile, go online to find out how to use the file to make custom build scripts.

Monitoring

If you think you've hung GitLab while building a large package, check http://management.cosi.clarkson.edu/gitlab to see that it is still up. Contact a maintainer if it fails to come back in 5 minutes or more. It may have caused some problems on the VM host.

Git Stuff

Git doesn't like it when you try to do stuff without verified SSL

To disable SSL checking on your system:

git config --global httpVerify false

To disable SSL checking for just a repo:

git config --local httpVerify false

If you want it to be secure (I would not recommend using the method above to solve the problem for an extended period of time) I would add Talos to your list of CA's in your system. That is beyond the scope of this page though, check out the OpenSSL CA page to do that.

Install

Installation was done in many steps by many people. In retrospect it should have been documented properly.

I would start with a web server, gitlab-ci, gitlab-ci-runner, and git installed on the system. Install certs, and then woo. I am not sure how exactly it was created unfortunately.