Find a file
Olaf Tomalka c0a92cb801 Limited amount of pruned Event rows per run
Old deployments of Gitlab might have a big number of old events to be
deleted. Such numbers cause the worker to timeout.
I've limited the amount of rows that should be destroyed at once to
10000, and increased how often pruning shall take place to 4 times a
day.
2016-09-07 19:41:25 +02:00
.github
.gitlab Rename behaviour to behavior in bug issue template for consistency 2016-09-01 22:01:02 -05:00
app Limited amount of pruned Event rows per run 2016-09-07 19:41:25 +02:00
bin
builds
config Limited amount of pruned Event rows per run 2016-09-07 19:41:25 +02:00
db Support empty PG database too 2016-09-06 12:13:45 +02:00
doc Merge branch 'patch-5' into 'master' 2016-09-07 14:13:36 +00:00
docker
features Merge branch '21508-inconsistency-personal-dashboard-todos-page-uses-old-interface-wrong-dropdown-filter-buttons' into 'master' 2016-09-01 20:17:46 +00:00
fixtures/emojis Upgrade Gemojione from 2.6.1 to 3.0.1. 2016-07-18 10:40:16 -06:00
generator_templates/active_record/migration Added checks for migration downtime 2016-07-20 12:41:56 +02:00
lib Merge branch 'refactor/ci-config-add-logical-validation' into 'master' 2016-09-07 16:14:37 +00:00
log
public Update specs - add mocks to simulate old versions 2016-09-01 14:00:46 +02:00
rubocop
scripts Used phantomjs variable 2016-08-15 11:43:23 +01:00
shared
spec Added cron to prune events older than 12 months. 2016-09-07 19:41:25 +02:00
tmp
vendor drop execute bit 2016-08-19 08:11:07 +03:00
.csscomb.json
.flayignore
.foreman
.gitattributes Added '*.js.es6 gitlab-language=javascript' to .gitattributes 2016-07-26 00:55:00 +01:00
.gitignore Add test coverage analysis for CoffeeScript (!5052) 2016-08-07 21:52:37 +02:00
.gitlab-ci.yml Have CI test migration paths 2016-09-06 12:54:22 +02:00
.mailmap Add an initial .mailmap 2016-08-06 23:21:11 +02:00
.pkgr.yml
.rspec
.rubocop.yml Rubocop syntax 2.3 2016-09-01 19:50:45 +02:00
.rubocop_todo.yml Enable Style/SpaceAroundEqualsInParameterDefault cop 2016-08-06 04:03:01 +02:00
.ruby-version Default build tests ruby 2.3.1 2016-08-11 19:00:00 +02:00
.scss-lint.yml
.vagrant_enabled
CHANGELOG Limited amount of pruned Event rows per run 2016-09-07 19:41:25 +02:00
config.ru
CONTRIBUTING.md Merge branch 'mr-performance-guides' into 'master' 2016-08-31 12:51:36 +00:00
doc_styleguide.md
docker-compose.yml
Gemfile Updated gitlab_git to 10.6.3 2016-09-06 15:42:24 +02:00
Gemfile.lock Updated gitlab_git to 10.6.3 2016-09-06 15:42:24 +02:00
GITLAB_SHELL_VERSION Update gitlab-shell to v3.4.0 2016-08-20 10:57:10 +02:00
GITLAB_WORKHORSE_VERSION Use gitlab-workhorse 0.7.11 2016-08-24 15:50:24 +02:00
LICENSE
MAINTENANCE.md Update MAINTENANCE.md with our latest policy 2016-07-19 09:05:56 +03:00
PROCESS.md Fix grammar (those issue -> those issues) 2016-08-31 15:23:31 +00:00
Procfile
Rakefile
README.md Merge branch 'docs/add-tests-coverage-badge-to-readme' into 'master' 2016-08-24 14:47:43 +00:00
VERSION 8.11 is released, long live 8.12 2016-08-23 10:00:38 +02:00

GitLab

build status coverage report Code Climate

Canonical source

The source of GitLab Community Edition is hosted on GitLab.com and there are mirrors to make contributing as easy as possible.

Open source software to collaborate on code

To see how GitLab looks please see the features page on our website.

  • Manage Git repositories with fine grained access controls that keep your code secure
  • Perform code reviews and enhance collaboration with merge requests
  • Each project can also have an issue tracker and a wiki
  • Used by more than 100,000 organizations, GitLab is the most popular solution to manage Git repositories on-premises
  • Completely free and open source (MIT Expat license)
  • Powered by Ruby on Rails

Hiring

We're hiring developers, support people, and production engineers all the time, please see our jobs page.

Editions

There are two editions of GitLab:

  • GitLab Community Edition (CE) is available freely under the MIT Expat license.
  • GitLab Enterprise Edition (EE) includes extra features that are more useful for organizations with more than 100 users. To use EE and get official support please become a subscriber.

Website

On about.gitlab.com you can find more information about:

Requirements

Please see the requirements documentation for system requirements and more information about the supported operating systems.

Installation

The recommended way to install GitLab is with the Omnibus packages on our package server. Compared to an installation from source, this is faster and less error prone. Just select your operating system, download the respective package (Debian or RPM) and install it using the system's package manager.

There are various other options to install GitLab, please refer to the installation page on the GitLab website for more information.

You can access a new installation with the login root and password 5iveL!fe, after login you are required to set a unique password.

Install a development environment

To work on GitLab itself, we recommend setting up your development environment with the GitLab Development Kit. If you do not use the GitLab Development Kit you need to install and setup all the dependencies yourself, this is a lot of work and error prone. One small thing you also have to do when installing it yourself is to copy the example development unicorn configuration file:

cp config/unicorn.rb.example.development config/unicorn.rb

Instructions on how to start GitLab and how to run the tests can be found in the development section of the GitLab Development Kit.

Software stack

GitLab is a Ruby on Rails application that runs on the following software:

  • Ubuntu/Debian/CentOS/RHEL
  • Ruby (MRI) 2.3
  • Git 2.7.4+
  • Redis 2.8+
  • MySQL or PostgreSQL

For more information please see the architecture documentation.

Third-party applications

There are a lot of third-party applications integrating with GitLab. These include GUI Git clients, mobile applications and API wrappers for various languages.

GitLab release cycle

For more information about the release process see the release documentation.

Upgrading

For upgrading information please see our update page.

Documentation

All documentation can be found on doc.gitlab.com/ce/.

Getting help

Please see Getting help for GitLab on our website for the many options to get help.

Is it any good?

Yes

Is it awesome?

Thanks for asking this question Joshua. These people seem to like it.