b2c73fde79
In certain cases, GitLab can miss a PostReceive invocation the first time a branch is pushed. When this happens, the "branch created" hooks are not run, which means various features don't work until the branch is deleted and pushed again. This MR changes the `Git::BranchPushService` so it checks the cache of existing branches in addition to the `oldrev` reported for the branch. If the branch name isn't in the cache, chances are we haven't run the service yet (it's what refreshes the cache), so we can go ahead and run it, even through `oldrev` is set. If the cache has been cleared by some other means in the meantime, then we'll still fail to run the hooks when we should. Fixing that in the general case is a larger problem, and we'd need to devote significant engineering effort to it. There's a chance that we'll run the relevant hooks *multiple times* with this change, if there's a race between the branch being created, and the `PostReceive` worker being run multiple times, but this can already happen, since Sidekiq is "at-least-once" execution of jobs. So, this should be safe. |
||
|---|---|---|
| .github | ||
| .gitlab | ||
| app | ||
| bin | ||
| builds | ||
| changelogs | ||
| config | ||
| danger | ||
| db | ||
| doc | ||
| docker | ||
| fixtures/emojis | ||
| generator_templates | ||
| haml_lint | ||
| lib | ||
| locale | ||
| log | ||
| plugins/examples | ||
| public | ||
| qa | ||
| rubocop | ||
| scripts | ||
| shared | ||
| spec | ||
| symbol | ||
| tmp | ||
| vendor | ||
| .codeclimate.yml | ||
| .csscomb.json | ||
| .eslintignore | ||
| .eslintrc.yml | ||
| .foreman | ||
| .gitattributes | ||
| .gitignore | ||
| .gitlab-ci.yml | ||
| .haml-lint.yml | ||
| .haml-lint_todo.yml | ||
| .mailmap | ||
| .nvmrc | ||
| .pkgr.yml | ||
| .prettierignore | ||
| .prettierrc | ||
| .rubocop.yml | ||
| .rubocop_todo.yml | ||
| .ruby-version | ||
| .scss-lint.yml | ||
| .stylelintrc | ||
| .yamllint | ||
| babel.config.js | ||
| CHANGELOG.md | ||
| config.ru | ||
| CONTRIBUTING.md | ||
| Dangerfile | ||
| docker-compose.yml | ||
| Dockerfile.assets | ||
| Gemfile | ||
| Gemfile.lock | ||
| GITALY_SERVER_VERSION | ||
| GITLAB_ELASTICSEARCH_INDEXER_VERSION | ||
| GITLAB_PAGES_VERSION | ||
| GITLAB_SHELL_VERSION | ||
| GITLAB_WORKHORSE_VERSION | ||
| INSTALLATION_TYPE | ||
| jest.config.js | ||
| LICENSE | ||
| MAINTENANCE.md | ||
| package.json | ||
| PHILOSOPHY.md | ||
| Pipfile | ||
| Pipfile.lock | ||
| PROCESS.md | ||
| Procfile | ||
| Rakefile | ||
| README.md | ||
| security.txt | ||
| VERSION | ||
| yarn.lock | ||
GitLab
Test coverage
Ruby
JavaScript
Canonical source
The canonical source of GitLab Community Edition is hosted on GitLab.com.
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
- Complete continuous integration (CI) and CD pipelines to builds, test, and deploy your applications
- Each project can also have an issue tracker, issue board, 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)
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:
- Subscriptions
- Consultancy
- Community
- Hosted GitLab.com use GitLab as a free service
- GitLab Enterprise Edition with additional features aimed at larger organizations.
- GitLab CI a continuous integration (CI) server that is easy to integrate with GitLab.
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.
Contributing
GitLab is an open source project and we are very happy to accept community contributions. Please refer to Contributing to GitLab page for more details.
Licensing
GitLab Community Edition (CE) is available freely under the MIT Expat license.
All third party components incorporated into the GitLab Software are licensed under the original license provided by the owner of the applicable component.
All Documentation content that resides under the doc/ directory of this repository is licensed under Creative Commons: CC BY-SA 4.0.
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 getting started 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/OpenSUSE
- Ruby (MRI) 2.4
- Git 2.8.4+
- Redis 2.8+
- PostgreSQL (preferred) or MySQL
For more information please see the architecture documentation.
UX design
Please adhere to the UX Guide when creating designs and implementing code.
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 docs.gitlab.com/ce/.
Getting help
Please see Getting help for GitLab on our website for the many options to get help.
Why?
Is it any good?
Is it awesome?
These people seem to like it.