Files
gitlabhq/doc/integration
Valery Sizov 3fcd75a911 Merge CE master into EE master
Conflicts:
	Gemfile
	VERSION
	app/assets/javascripts/project.js.coffee
	app/assets/javascripts/users_select.js.coffee
	app/controllers/projects/services_controller.rb
	app/models/project.rb
	app/views/groups/edit.html.haml
	features/project/service.feature
	features/steps/project/services.rb
	spec/models/concerns/mentionable_spec.rb
2014-11-13 17:05:12 +02:00
..
2014-04-07 14:17:40 +02:00
2014-08-19 14:37:51 +02:00
2014-05-28 17:05:23 +02:00
2014-09-26 15:32:40 +02:00
2014-11-13 17:05:12 +02:00

GitLab Integration

GitLab integrates with multiple third-party services to allow external issue trackers and external authentication.

See the documentation below for details on how to configure these services.

  • Jira Integrate with the JIRA issue tracker
  • External issue tracker Redmine, bugzilla, etc.
  • LDAP Set up sign in via LDAP
  • OmniAuth Sign in via Twitter, GitHub, and Google via OAuth.
  • Jenkins Integrate with the Jenkins CI
  • Slack Integrate with the Slack chat service

Project services

Integration with services such as Campfire, Flowdock, Gemnasium, HipChat, PivotalTracker and Slack are available in the from of a Project Service. You can find these within GitLab in the Services page under Project Settings if you are at least a master on the project. Project Services are a bit like plugins in that they allow a lot of freedom in adding functionality to GitLab, for example there is also a service that can send an email every time someone pushes new commits. Because GitLab is open source we can ship with the code and tests for all plugins. This allows the community to keep the plugins up to date so that they always work in newer GitLab versions. For an overview of what projects services are available without logging in please see the project_services directory.