To effectively use GitLab CI, you need a valid .gitlab-ci.yml
file present at the root directory of your project and a runner properly set up. You can read our quick start guide to get you started.
If you are using an external CI server like Jenkins or Drone CI, it is advised to disable GitLab CI in order to not have any conflicts with the commits status API.
As of GitSwarm 2016.1, GitLab CI is mainly exposed via the /builds
page of a project. Disabling GitLab CI in a project does not delete any previous builds. In fact, the /builds
page can still be accessed, although it's hidden from the left sidebar menu.
GitLab CI is enabled by default on new installations and can be disabled either individually under each project's settings, or site-wide by modifying the settings in gitlab.yml
and /etc/gitswarm/gitswarm.rb
for source and package installations respectively.
The setting to enable or disable GitLab CI can be found with the name Builds under the Features area of a project's settings along with Issues, Merge Requests, Wiki and Snippets. Select or deselect the checkbox and hit Save for the settings to take effect.
You can disable GitLab CI site-wide, by modifying the settings in gitlab.yml
and /etc/gitswarm/gitswarm.rb
for source and package installations respectively.
Two things to note:
For source installations, open gitlab.yml
with your editor and set builds
to false
:
## Default project features settings
default_projects_features:
issues: true
merge_requests: true
wiki: true
snippets: false
builds: false
Save the file and restart GitSwarm: sudo service gitlab restart
.
For package installations, edit /etc/gitswarm/gitswarm.rb
and add the line:
gitlab_rails['gitlab_default_projects_features_builds'] = false
Save the file and reconfigure GitSwarm: sudo gitswarm-ctl reconfigure
.