Skip to content

GitLab

Switch branch/tag
History Find file
Clone
Merge branch 'fix-jira-mention-spec' into 'master'
Robert Speicher authored 
Fix JIRA mention spec

Fixes spec that was skipped in 10de4261.

The expected behavior with commits mentioning issues, is that when the commit _closes_ the issue, the issue only gets the "closed by commit X" comment, and not also the "mentioned in commit X" comment.

With JIRA, it used to get both, and now does no longer.

The spec was updated to test the new ("correct") behavior.

See merge request !36
5bd8b016
Name Last commit Last update
app Merge branch 'fix-jira-mention-spec' into 'master'
bin Merge branch 'master' into ci-and-ce-sitting-in-a-tree-k-i-s-s-i-n-g
builds Add missing builds/ folder to fix backup tests
config Merge remote-tracking branch 'origin/master' into ce_upstream_15_10
db Merge branch 'master' into ce_upstream_15_10
doc Merge remote-tracking branch 'ce/master'
docker Fix typo
features Fix JIRA service feature
lib Merge remote-tracking branch 'ce/master'
log init commit
public Merge remote-tracking branch 'origin/master' into ce_upstream_15_10
scripts Groundwork for merging CI into CE
spec Merge branch 'fix-jira-mention-spec' into 'master'
tmp Remove tmp/.gitkeep
vendor/assets Add nice scroll for sidebar
.foreman complete hooks for post receive
.gitattributes Update git attributes for changelog-ee
.gitignore Make Reply by email easier to configure
.gitlab-ci.yml Allow benchmark failures for the time being
.hound.yml Make houndci prefer single quotes.
.license_encryption_key.pub Allow license to be uploaded and enforce its validity.
.pkgr.yml Use new way of defining services on packager.io
.rspec Make Fuubar the default rspec formatter
.rubocop.yml Enable "UselessAssignment" rubocop lint
.ruby-version ruby 2.1.6
.simplecov
.teatro.yml
CHANGELOG
CHANGELOG-EE
CONTRIBUTING.md
GITLAB_SHELL_VERSION
Gemfile
Gemfile.lock
LICENSE
MAINTENANCE.md
PROCESS.md
Procfile
README.md
Rakefile
VERSION
config.ru
doc_styleguide.md
docker-compose.yml
README.md

GitLab

build status Build Status Code Climate Coverage Status

Canonical source

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

The source of GitLab Enterprise Edition is hosted on GitLab.com.

logo GitLab

Subscriber onboarding information

Thank you for purchasing a GitLab subscription!

For standard subscribers, please see emergency contact info and other useful information in the Standard subscribers README.

GitLab Enterprise Edition repository: https://gitlab.com/gitlab-com/gitlab-ee

Download GitLab Enterprise Edition: https://about.gitlab.com/downloads-ee

Documentation: http://doc.gitlab.com/ee/

To upgrade from CE, just perform a normal upgrade, but use an EE package: https://about.gitlab.com/update/#ee

If you need help with your GitLab installation and for any technical questions please contact us at subscribers@gitlab.com

For all other questions, contact us at sales@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
  • 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

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.

Included with the GitLab Omnibus Packages is GitLab CI that can easily build, test and deploy code.

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.1
  • Git 1.7.10+
  • Redis 2.4+
  • 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

Since 2011 a minor or major version of GitLab is released on the 22nd of every month. Patch and security releases are published when needed. New features are detailed on the blog and in the changelog. For more information about the release process see the release documentation. Features that will likely be in the next releases can be found on the feature request forum with the status started and completed.

Upgrading

For upgrading information please see our update page.

Documentation

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

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.

GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7