Izaak AlpertandIzaak Alpert
3d7194f011
The good: - You can do a merge request for a forked commit and it will merge properly (i.e. it does work). - Push events take into account merge requests on forked projects - Tests around merge_actions now present, spinach, and other rspec tests - Satellites now clean themselves up rather then recreate The questionable: - Events only know about target projects - Project's merge requests only hold on to MR's where they are the target - All operations performed in the satellite The bad: - Duplication between project's repositories and satellites (e.g. commits_between) (for reference: http://feedback.gitlab.com/forums/176466-general/suggestions/3456722-merge-requests-between-projects-repos) Fixes: Make test repos/satellites only create when needed -Spinach/Rspec now only initialize test directory, and setup stubs (things that are relatively cheap) -project_with_code, source_project_with_code, and target_project_with_code now create/destroy their repos individually -fixed remote removal -How to merge renders properly -Update emails to show project/branches -Edit MR doesn't set target branch -Fix some failures on editing/creating merge requests, added a test -Added back a test around merge request observer -Clean up project_transfer_spec, Remove duplicate enable/disable observers -Ensure satellite lock files are cleaned up, Attempted to add some testing around these as well -Signifant speed ups for tests -Update formatting ordering in notes_on_merge_requests -Remove wiki schema update Fixes for search/search results -Search results was using by_project for a list of projects, updated this to use in_projects -updated search results to reference the correct (target) project -udpated search results to print both sides of the merge request Change-Id: I19407990a0950945cc95d62089cbcc6262dab1a8
GitLab: self hosted Git management software
GitLab allows you to
- keep your code secure on your own server
- manage repositories, users and access permissions
- communicate through issues, line-comments and wiki pages
- perform code review with merge requests
GitLab is
- powered by Ruby on Rails
- completely free and open source (MIT license)
- used by more than 10.000 organizations to keep their code secure
Code status
-
on ci.gitlab.org (master branch) -
on travis-ci.org (master branch) -
-
this button can be yellow (small updates are available) but must not be red (a security fix or an important update is available), gems are updated in major releases of GitLab. -
Resources
-
GitLab.org community site: Homepage | Screenshots | Blog | Demo
-
GitLab.com commercial services: Homepage | Subscription | Consultancy | GitLab Cloud | Blog
-
GitLab CI: Readme of the GitLab open-source continuous integration server
Requirements
- Ubuntu/Debian**
- ruby 1.9.3
- MySQL or PostgreSQL
- git
- gitlab-shell
- redis
** More details are in the requirements doc
Installation
Official production installation
Official development installation
If you want to contribute, please first read our Contributing Guidelines and then we suggest you to use the Vagrant virtual machine project to get an environment working with all dependencies.
Unsupported production installation
-
GitLab recipes for setup on different platforms
New versions and upgrading
Each month on the 22nd a new version is released together with an upgrade guide.
-
Features that will be in the next release are listed on the feedback and suggestions forum with the status "started".
Run in production mode
The Installation guide contains instructions on how to download an init script and run it automatically on boot. You can also start the init script manually:
sudo service gitlab start
or by directly calling the script
sudo /etc/init.d/gitlab start
Run in development mode
Start it with Foreman
bundle exec foreman start -p 3000
or start each component separately
bundle exec rails s
bundle exec rake sidekiq:start
Run the tests
-
Seed the database
bundle exec rake db:setup RAILS_ENV=test bundle exec rake db:seed_fu RAILS_ENV=test -
Run all tests
bundle exec rake gitlab:test -
RSpec unit and functional tests
All RSpec tests: bundle exec rake spec Single RSpec file: bundle exec rspec spec/controllers/commit_controller_spec.rb -
Spinach integration tests
All Spinach tests: bundle exec rake spinach Single Spinach test: bundle exec spinach features/project/issues/milestones.feature
GitLab interfaces
Getting help
-
Maintenance policy specifies what versions are supported.
-
Troubleshooting guide contains solutions to common problems.
-
Mailing list and Stack Overflow are the best places to ask questions. For example you can use it if you have questions about: permission denied errors, invisible repos, can't clone/pull/push or with web hooks that don't fire. Please search for similar issues before posting your own, there's a good chance somebody else had the same issue you have now and has resolved it. There are a lot of helpful GitLab users there who may be able to help you quickly. If your particular issue turns out to be a bug, it will find its way from there to a fix.
-
Feedback and suggestions forum is the place to propose and discuss new features for GitLab.
-
Contributing guide describes how to submit pull requests and issues. Pull requests and issues not in line with the guidelines in this document will be closed.
-
Support subscription connects you to the knowledge of GitLab experts that will resolve your issues and answer your questions.
-
Consultancy allows you hire GitLab experts for installations, upgrades and customizations.