Skip to content
Snippets Groups Projects

Compare revisions

Changes are shown as if the source revision was being merged into the target revision. Learn more about comparing revisions.

Source

Select target project
No results found

Target

Select target project
  • gitlab-com/www-gitlab-com
  • jvanbaarsen/www-gitlab-com
  • dblessing/www-gitlab-com
  • axil/www-gitlab-com
  • mvb/www-gitlab-com
  • Mataway/www-gitlab-com
  • grexi/www-gitlab-com
  • mwermuth/www-gitlab-com
  • razer6/www-gitlab-com
  • crohr/www-gitlab-com
  • mr-vinn/www-gitlab-com
  • semancik/www-gitlab-com
  • bugagazavr/www-gitlab-com
  • tangnan/www-gitlab-com
  • igor-drozdov/www-gitlab-com
  • mlapierre/www-gitlab-com
  • bluefeet/www-gitlab-com
  • chance_t521usa/www-gitlab-com
  • Hipinspire/www-gitlab-com
  • thiagonego/www-gitlab-com
  • dachary/www-gitlab-com
  • jblaine/www-gitlab-com
  • DouweM/www-gitlab-com
  • ayufan/www-gitlab-com
  • haynes/www-gitlab-com
  • andrewsomething/www-gitlab-com
  • ellen/www-gitlab-com
  • leanlabs.io/www-gitlab-com
  • aureliojargas/www-gitlab-com
  • chriscool/www-gitlab-com
  • stevepeak/www-gitlab-com
  • Chaos/www-gitlab-com
  • mwessel/www-gitlab-com
  • amenophis/www-gitlab-com
  • karengc/www-gitlab-com
  • mikegerwitz/www-gitlab-com
  • Ilinde/www-gitlab-com
  • jwrede/www-gitlab-com
  • pwhittlesea/www-gitlab-com
  • bbodenmiller/www-gitlab-com
  • performance/www-gitlab-com
  • marin/www-gitlab-com
  • nansione/www-gitlab-com
  • harlantwood/www-gitlab-com
  • cangcanglang/www-gitlab-com
  • 2called-chaos/www-gitlab-com
  • Arno/www-gitlab-com
  • jeffkreeftmeijer/www-gitlab-com
  • jaredjennings/www-gitlab-com
  • glennon/www-gitlab-com
  • ggppjj/www-gitlab-com
  • beetee2/www-gitlab-com
  • mccroden/www-gitlab-com
  • Hamcha/www-gitlab-com
  • mzaideel/www-gitlab-com
  • jzelinskie/www-gitlab-com
  • newton/www-gitlab-com
  • paulthomson/www-gitlab-com
  • vidkun/www-gitlab-com
  • makwarth/www-gitlab-com
  • Ashley/www-gitlab-com
  • anseljh/www-gitlab-com
  • jnijhof/www-gitlab-com
  • NathanGiesbrecht/www-gitlab-com
  • scronide/www-gitlab-com
  • rymai/www-gitlab-com
  • kelvinmutuma/www-gitlab-com
  • brettcannon/www-gitlab-com
  • voidspacexyz/www-gitlab-com
  • chayan553/www-gitlab-com
  • grzesiek/www-gitlab-com
  • strugee/www-gitlab-com
  • palmin/www-gitlab-com
  • singingwolfboy/www-gitlab-com
  • it33/www-gitlab-com
  • luis-raymeb/www-gitlab-com
  • vinkla/www-gitlab-com
  • msokk/www-gitlab-com
  • akarun/www-gitlab-com
  • emmajane/www-gitlab-com
  • ranbose/www-gitlab-com
  • morsik/www-gitlab-com
  • deeeki/www-gitlab-com
  • mkrdip/www-gitlab-com
  • chrisjrn/www-gitlab-com
  • apetro/www-gitlab-com
  • valeriomazzeo/www-gitlab-com
  • guoxf/www-gitlab-com
  • nelson-r-oliveira/www-gitlab-com
  • dpenezic/www-gitlab-com
  • samurailink3/www-gitlab-com
  • yozo.suzuki/www-gitlab-com
  • openjck/www-gitlab-com
  • vgerris/www-gitlab-com
  • tlfvulmort/www-gitlab-com
  • securitykernel/www-gitlab-com
  • simon_w/www-gitlab-com
  • luciano-igtech/www-gitlab-com
  • sah2ed/www-gitlab-com
  • rutsky1/www-gitlab-com
  • Avadon/www-gitlab-com
  • xorgy/www-gitlab-com
  • ahmetkizilay/www-gitlab-com
  • asumaran/www-gitlab-com
  • DanSkaggs/www-gitlab-com
  • karen/www-gitlab-com
  • HRMsimon/www-gitlab-com
  • nerdishbynature/www-gitlab-com
  • pedrorijo91/www-gitlab-com
  • ghostlyrics/www-gitlab-com
  • Y.Skandrani/www-gitlab-com
  • markpundsack/www-gitlab-com
  • evigeant/www-gitlab-com
  • plainspace/www-gitlab-com
  • kmf/www-gitlab-com
  • alexwlchan/www-gitlab-com
  • hayesr/www-gitlab-com
  • daniel.wonisch/www-gitlab-com
  • MrChrisW/www-gitlab-com
  • AngeloStavrow/www-gitlab-com
  • nikhilgk/www-gitlab-com
  • dolfim/www-gitlab-com
  • njgraham/www-gitlab-com
  • guyzmo/www-gitlab-com
  • ashleysmithashleysmith/www-gitlab-com
  • mvdan/www-gitlab-com
  • mprittie/www-gitlab-com
  • thabz/www-gitlab-com
  • kush/www-gitlab-com
  • cyann/www-gitlab-com
  • teemo/www-gitlab-com
  • amara/www-gitlab-com
  • Mortiferr/www-gitlab-com
  • alexleventer/www-gitlab-com
  • svansteenis/www-gitlab-com
  • hax0rlif3/www-gitlab-com
  • iraytrace/www-gitlab-com
  • clns/www-gitlab-com
  • jasoares/www-gitlab-com
  • bkc/www-gitlab-com
  • dsross/www-gitlab-com
  • gshaheen/www-gitlab-com
  • artemad/www-gitlab-com
  • artfisica/www-gitlab-com
  • malganis93/www-gitlab-com
  • cha63506/www-gitlab-com
  • madhancock/www-gitlab-com
  • curry684/www-gitlab-com
  • scottbrown/www-gitlab-com
  • ismail-s/www-gitlab-com
  • tattwamasi/www-gitlab-com
  • Tuckie/www-gitlab-com
  • nzoschke/www-gitlab-com
  • eliran.mesika/www-gitlab-com
  • muendelezaji/www-gitlab-com
  • benwbooth/www-gitlab-com
  • apenney/www-gitlab-com
  • VikramTiwari/www-gitlab-com
  • eugene3/www-gitlab-com
  • railmeat/www-gitlab-com
  • Lintalist/www-gitlab-com
  • lbennett/www-gitlab-com
  • haketo/www-gitlab-com
  • dougmiller/www-gitlab-com
  • cperessini/www-gitlab-com
  • daikonsama/www-gitlab-com
  • pavelloz/www-gitlab-com
  • shelbymallon092/www-gitlab-com
  • markglenfletcher1/www-gitlab-com
  • jspizziri/www-gitlab-com
  • jneen/www-gitlab-com
  • jerbob92/www-gitlab-com
  • danielcarr/www-gitlab-com
  • graingert/www-gitlab-com
  • lyrixx/www-gitlab-com
  • benjbrandall/www-gitlab-com
  • iguyking/www-gitlab-com
  • julieamanalo/www-gitlab-com
  • dawg/www-gitlab-com
  • sdmouton/www-gitlab-com
  • alanhamlett/www-gitlab-com
  • frank-west-iii/www-gitlab-com
  • toricls/www-gitlab-com
  • znixian/www-gitlab-com
  • jparrow/www-gitlab-com
  • ahmadsherif/www-gitlab-com
  • julie_manalo/www-gitlab-com
  • winniehell/www-gitlab-com
  • Maesto/www-gitlab-com
  • eanplatter/www-gitlab-com
  • lupine/www-gitlab-com
  • tianshi/www-gitlab-com
  • POEditor/www-gitlab-com
  • rjauquet/www-gitlab-com
  • dimitrieh/www-gitlab-com
  • adambuckland/www-gitlab-com
  • thisishugo/www-gitlab-com
  • nick.thomas/www-gitlab-com
  • timsly/www-gitlab-com
  • ramosmd/www-gitlab-com
  • jayesh-sapkale/www-gitlab-com
  • tingshow163/www-gitlab-com
  • z9g9l9/www-gitlab-com
  • stefanoCaroli/www-gitlab-com
  • ngetchell/www-gitlab-com
  • clofresh/www-gitlab-com
  • WheresAlice/www-gitlab-com
  • benalbrecht/www-gitlab-com
  • woollyally/www-gitlab-com
  • omt-tech/about-omt-tech
  • brycepj/www-gitlab-com
  • nick.volynkin/www-gitlab-com
  • txworking/www-gitlab-com
  • virtuacreative/www-gitlab-com
  • rdumont/www-gitlab-com
  • hotoo/www-gitlab-com
  • caowf/www-gitlab-com
  • lanzafame/www-gitlab-com
  • rockybean/www-gitlab-com
  • sungwoncho/www-gitlab-com
  • bebbs/www-gitlab-com
  • eventualbuddha/www-gitlab-com
  • gitpitch/www-gitlab-com
  • airat/www-gitlab-com
  • CuCTeMeH/www-gitlab-com
  • melissa3/www-gitlab-com
  • ianmartin/www-gitlab-com
  • gramakri/www-gitlab-com
  • nateprewitt/www-gitlab-com
  • hcgtv/www-gitlab-com
  • ClemMakesApps/www-gitlab-com
  • demi/www-gitlab-com
  • HongPong/www-gitlab-com
  • dalanmiller/www-gitlab-com
  • reproduction-group/www-gitlab-com
  • Nowaker/www-gitlab-com
  • bugmuncher/www-gitlab-com
  • erica/www-gitlab-com
  • adamniedzielski/www-gitlab-com
  • artNasser/www-gitlab-com
  • JustinTRoss/www-gitlab-com
  • stowball/www-gitlab-com
  • imt-voidnologo/www-gitlab-com
  • jloh/www-gitlab-com
  • dts1/www-gitlab-com
  • zillion/www-gitlab-com
  • monty24/www-gitlab-com
  • Hazelaar/www-gitlab-com
  • lbot/www-gitlab-com
  • npwalker/www-gitlab-com
  • juliendubreuil/www-gitlab-com
  • Wiil/www-gitlab-com
  • pixdrift/www-gitlab-com
  • sbeleidy/www-gitlab-com
  • julien485/www-gitlab-com
  • jonathanjouty/www-gitlab-com
  • carnage/www-gitlab-com
  • greysonp/www-gitlab-com
  • LucaVazz/www-gitlab-com
  • josephfrazier/www-gitlab-com
  • cindy/www-gitlab-com
  • zeroroll/www-gitlab-com
  • andreaskaemmerle/www-gitlab-com
  • alexandrustaetusecondary/www-gitlab-com
  • vijoin/www-gitlab-com
  • catalinred/www-gitlab-com
  • uberblue87/www-gitlab-com
  • carmiri/www-gitlab-com
  • Celc27/www-gitlab-com
  • lchavez/www-gitlab-com
  • ja-me-sk/www-gitlab-com
  • gihadmurad/www-gitlab-com
  • ericcrosson/www-gitlab-com
  • ryancharris/www-gitlab-com
  • freethejazz/www-gitlab-com
  • balasankarc/www-gitlab-com
  • warren.postma/www-gitlab-com
  • eReGeBe/www-gitlab-com
  • terrchen/www-gitlab-com
  • aaronjheinen/www-gitlab-com
  • warren.postma2/www-gitlab-com
  • Pascalmh/www-gitlab-com
  • samrose3/www-gitlab-com
  • moritzplassnig/www-gitlab-com
  • notisj/www-gitlab-com
  • marcolenzo/www-gitlab-com
  • w.vankuipers/www-gitlab-com
  • Hostert/www-gitlab-com
  • EtherTyper/www-gitlab-com
  • Letme/www-gitlab-com
  • lcong/www-gitlab-com
  • kazhuyo/www-gitlab-com
  • rocketpastsix/www-gitlab-com
  • timwis/www-gitlab-com
  • poschi3/www-gitlab-com
  • JoshOakhurst/www-gitlab-com
  • garandam/www-gitlab-com
  • Kachi0/www-gitlab-com
  • doron/www-gitlab-com
  • andrepiske/www-gitlab-com
  • snorlaxyum/www-gitlab-com
  • ozmose/www-gitlab-com
  • superstrong/www-gitlab-com
  • yukio/www-gitlab-com
  • tc42/www-gitlab-com
  • abuango/www-gitlab-com
  • Petermuturi/www-gitlab-com
  • lexicoder/www-gitlab-com
  • psimyn/www-gitlab-com
  • funspectre/www-gitlab-com
  • michael.biebl/www-gitlab-com
  • daamien/www-gitlab-com
  • rachapornsemaksorn/www-gitlab-com
  • mehranrasulian/www-gitlab-com
  • ziegenberg/www-gitlab-com
  • kesh92/www-gitlab-com
  • jarka/www-gitlab-com
  • allamand/www-gitlab-com
  • viktorbenei/www-gitlab-com
  • travsten/www-gitlab-com
  • scott113341/www-gitlab-com
  • TAiS46/www-gitlab-com
  • itay.mendelawy/www-gitlab-com
  • michaelcweiss/www-gitlab-com
  • odoedkiy/www-gitlab-com
  • seanlane/www-gitlab-com
  • mydigitalself/www-gitlab-com
  • kevgathuku/www-gitlab-com
  • mbell/www-gitlab-com
  • reyhan/www-gitlab-com
  • fournova/www-gitlab-com
  • dssaini/www-gitlab-com
  • steffenpoulsen/www-gitlab-com
  • sandercox/www-gitlab-com
  • Holysynrr/www-gitlab-com
  • siemens/www-gitlab-com
  • mrogge/www-gitlab-com
  • guuslieben/www-gitlab-com
  • brittanyr/www-gitlab-com
  • gsaslis/www-gitlab-com
  • csmallman/www-gitlab-com
  • rothsa/www-gitlab-com
  • sc0ttyd/www-gitlab-com
  • TheNT87/www-gitlab-com
  • j5alive/www-gitlab-com
  • html5cat/www-gitlab-com
  • leo19920823/www-gitlab-com
  • cshubhamrao/www-gitlab-com
  • yesmeck/www-gitlab-com
  • dosuken123/www-gitlab-com
  • aws002/www-gitlab-com
  • gitlab/www-gitlab-com
  • jmay1/www-gitlab-com
  • pyrothos1/www-gitlab-com
  • jf---/www-gitlab-com
  • aviraldg/www-gitlab-com
  • simonabw/www-gitlab-com
  • niccokunzmann/www-gitlab-com
  • hook/www-gitlab-com
  • gmessner/www-gitlab-com
  • briancaine/www-gitlab-com
  • alysha/www-gitlab-com
  • maxklenk/www-gitlab-com
  • reprazent/www-gitlab-com
  • atsaloli/www-gitlab-com
  • pkq/www-gitlab-com
  • collinanderson/www-gitlab-com
  • bekroogle/www-gitlab-com
  • sarahod/www-gitlab-com
  • infogrind/www-gitlab-com
  • barspi/www-gitlab-com
  • smith-kyle/www-gitlab-com
  • gitlabproject_s/www-gitlab-com
  • paolofalomo/www-gitlab-com
  • mike37/www-gitlab-com
  • dakotahp/www-gitlab-com
  • pratikborsadiya/www-gitlab-com
  • pauldalmeida/www-gitlab-com
  • mikew/www-gitlab-com
  • loopDelicious/www-gitlab-com
  • tnir/www-gitlab-com
  • Theaxiom/www-gitlab-com
  • hcs0/www-gitlab-com
  • Lviv/www-gitlab-com
  • winh/www-gitlab-com
  • stovokor/www-gitlab-com
  • marceloschmidt/www-gitlab-com
  • innerwhisper/www-gitlab-com
  • mollybeth/www-gitlab-com
  • juan11/www-gitlab-com
  • MaxWason/www-gitlab-com
  • raxkin/www-gitlab-com
  • jayson.ocoracion/www-gitlab-com
  • bschacht/www-gitlab-com
  • tywe/www-gitlab-com
  • fatihgokce07/www-gitlab-com
  • belak/www-gitlab-com
  • contetto/www-gitlab-com
  • reviforks/www-gitlab-com
  • joshrotenberg/www-gitlab-com
  • maguowei/www-gitlab-com
  • levyleo/www-gitlab-com
  • dirkriehle/www-gitlab-com
  • simonwex/www-gitlab-com
  • elygre/www-gitlab-com
  • jirkalewandowski/www-gitlab-com
  • mkozono/www-gitlab-com
  • BgR8/www-gitlab-com
  • chen-j/www-gitlab-com
  • Sandyl/www-gitlab-com
  • flungo/www-gitlab-com
  • mitchhentges/www-gitlab-com
  • felix.maier/www-gitlab-com
  • Dannyzen/www-gitlab-com
  • jean3/www-gitlab-com
  • Sleept33/www-gitlab-com
  • MDXDave/www-gitlab-com
  • chrismo/www-gitlab-com
  • wilsonmar/www-gitlab-com
  • emenguy/www-gitlab-com
  • gebn/www-gitlab-com
  • ckatanda/www-gitlab-com
  • imran-khan/www-gitlab-com
  • vickyvignesh1091/www-gitlab-com
  • SandraE/www-gitlab-com
  • rareyang.why/www-gitlab-com
  • ethomson/www-gitlab-com
  • eeshangarg/www-gitlab-com
  • yongbo/www-gitlab-com
  • saine1a/www-gitlab-com
  • uforce/www-gitlab-com
  • TrevorL/www-gitlab-com
  • katrinleinweber/www-gitlab-com
  • bdero/www-gitlab-com
  • wangchen1/www-gitlab-com
  • bmackinney/www-gitlab-com
  • amorphid/www-gitlab-com
  • srinivasg1/www-gitlab-com
  • srikanth.satturi/www-gitlab-com
  • adeolonoh/www-gitlab-com
  • travismiller/www-gitlab-com
  • masone/www-gitlab-com
  • photomatt/www-gitlab-com
  • SuriyaaKudoIsc/www-gitlab-com
  • jamesjieye/www-gitlab-com
  • hoppus/www-gitlab-com
  • iscorer/www-gitlab-com
  • caseyscarborough/www-gitlab-com
  • gdubicki/www-gitlab-com
  • eyalev/www-gitlab-com
  • jarv/www-gitlab-com
  • FelicianoTech/www-gitlab-com
  • VitM/www-gitlab-com
  • ericforbes/www-gitlab-com
  • khrystyna_h/www-gitlab-com
  • thanadams/www-gitlab-com
  • barbiejane/www-gitlab-com
  • ZapierTeam/www-gitlab-com
  • almtoolbox/www-gitlab-com
  • ymousavinia/www-gitlab-com
  • hnk/www-gitlab-com
  • Rush1/www-gitlab-com
  • hanul17623/www-gitlab-com
  • xuantan/www-gitlab-com
  • NechPL/www-gitlab-com
  • markus_bruns/www-gitlab-com
  • denisvm/www-gitlab-com
  • fybwid/www-gitlab-com
  • simonwill/www-gitlab-com
  • jbmath/www-gitlab-com
  • mattatrenet/www-gitlab-com
  • shak-mar/www-gitlab-com
  • boleary/www-gitlab-com
  • natseg/www-gitlab-com
  • techguru/www-gitlab-com
  • Linuus/www-gitlab-com
  • hugoherter/www-gitlab-com
  • ajvengo/www-gitlab-com
  • levente_sz/www-gitlab-com
  • paulrbr/www-gitlab-com
  • 7022andre/www-gitlab-com
  • inem/www-gitlab-com
  • gitlab-contrib/www-gitlab-com
  • JeffreyCA/www-gitlab-com
  • williamchia/www-gitlab-com
  • huntfield35/www-gitlab-com
  • mitchellwright/www-gitlab-com
  • richardc/www-gitlab-com
  • stratosgear/www-gitlab-com
  • elin.yordanov/www-gitlab-com
490 results
Show changes
Commits on Source (1194)
Showing
with 1410 additions and 1066 deletions
Loading
Loading
@@ -7,9 +7,8 @@ before_script:
- bundle install --jobs 4 --path vendor
 
cache:
key: "website"
key: "web"
paths:
- public
- vendor
 
stages:
Loading
Loading
@@ -63,7 +62,7 @@ review:
variables:
GIT_STRATEGY: none
script:
- rsync -av --delete public ~/pages/$CI_COMMIT_REF_SLUG
- rsync -avz --delete public ~/pages/$CI_COMMIT_REF_SLUG
environment:
name: review/$CI_COMMIT_REF_SLUG
url: http://$CI_COMMIT_REF_SLUG.about.gitlab.com
Loading
Loading
@@ -71,7 +70,7 @@ review:
only:
- branches@gitlab-com/www-gitlab-com
except:
- master
- master@gitlab-com/www-gitlab-com
tags:
- deploy
- review-apps
Loading
Loading
@@ -93,7 +92,7 @@ review_stop:
only:
- branches@gitlab-com/www-gitlab-com
except:
- master
- master@gitlab-com/www-gitlab-com
tags:
- deploy
- review-apps
Loading
Loading
@@ -107,7 +106,7 @@ deploy:
- build_master
before_script: []
script:
- rsync --delete -vr public/ ~/public/
- rsync --delete -avz public/ ~/public/
environment:
name: production
url: https://about.gitlab.com
Loading
Loading
### Description
Compare GitLab with <Competitor>.
### Links / references
(Add links to the competitor home page, documentation, Wikipedia article, etc.)
-
-
/label ~"comparison page"
### Experiment Description
(Please describe your experiment in 3-5 sentences. For example: We should change
the navigation bar. It is important to drive people to the EE premium page and
it should be more prominent. Let's make the navigation bar only have a link to
EE premium!)
### Which metrics do you think this will affect?
(Example: It will increase the number of EE trials we have)
### What is your predicted outcome on this metric?
(Example: Increase EE trials by 25%)
### What resources will this experiment require?
- [ ] Marketing (x days)
- [ ] Engineering (x days)
- [ ] Design (x days)
### Any other information you'd like to add?
### Description
Create comparison page for: GitLab vs <Competitor>.
Closes <link to issue>
### Preview URL
/label ~"comparison page"
Copyright (c) GitLab B.V.
Copyright (c) GitLab B.V.
Loading
Loading
@@ -319,27 +319,110 @@ follow the steps below:
The feature page grabs its content automatically from the file
`/data/features.yml`.
 
### Update the comparison page (under `/comparison`)
### Create or update the comparison pages (under `/comparison`)
 
The comparison page grabs its content automatically from the file
`/data/comparisons.yml`.
The [comparison page][comp] grabs its content automatically from the files under
`data/comparisons/`.
 
When adding a new comparison, make sure that you follow the structure below:
There are 3 files in total which you need to create or edit:
 
- `data/comparisons/gitlab_vs_competitor.yml`: Create for new comparisons. Every
comparison page has its own yaml file. **Use underscores**
- `source/comparison/gitlab-vs-competitor.html.haml`: Create for new comparisons.
Every comparison page has its own html file. **Use dashes**
- `source/includes/comparison_table.html.haml`: Edit for new or existing
comparisons.
---
**Step 1**
Add a new yaml file named after the comparison using underscores:
`data/comparisons/gitlab_vs_competitor.yml`. You can start by copying an
existing one and then changing its content. Yaml files are sensitive to
indentation, so be extra careful. Make sure that you follow the structure below:
```yaml
title: "Competitor vs GitLab"
pdf: gitlab-vs-competitor.pdf
competitor_one:
name: 'GitLab'
logo: '/images/comparison/gitlab-logo.svg'
competitor_two:
name: 'Competitor'
logo: '/images/comparison/competitor-logo.svg'
last_updated: 'May 5, 2017'
features:
- title: "Briefly explain the feature"
description: |
Describe the differences in detail. This text can span in multiple
lines without interfering with its structure. It will always appear
as one paragraph.
link_description: "Learn more about Feature Name."
link: "link to GitLab's feature page documentation or blog post"
competitor_one: true
competitor_two: true
```
Notes:
- Although the file is named with GitLab being first, the title should have the
competitor name first.
- The `pdf` name should be similar to the yaml file name, but with dashes. In
short, it has to match the HTML page name in step 2. If you want to omit the
PDF link altogether, set its value to `null`, like: `pdf: 'null'`.
- Remember to update the date every time you make a change.
- The competitor's logo (`competitor_two`) can be `svg` or `png`. Save it in
`source/images/comparison/competitor-logo.svg`.
- In the features area, `competitor_one` is always GitLab, and `competitor_two`
is the competitor we are compared against. Values for these two fields are
`true|false|sortof`.
**Step 2**
Add a new haml file named after the comparison using dashes:
`source/comparison/gitlab-vs-competitor.html.haml`. You can start by copying an
existing one and then editing it. The only change you need to make is the
name of the yaml file you created above:
```yaml
---
layout: comparison_page
trial_bar: true
title: GitLab compared to other tools
suppress_header: true
image_title: '/images/comparison/title_image.png'
extra_css:
- compared.css
extra_js:
- comparison.js
---
- data.comparisons.gitlab_vs_competitor do |comparison_block|
= partial "includes/comparison_table", locals: { comparison_block: comparison_block }
```
- title: ""
description: ""
link_description: ""
link:
competitor_one: true
competitor_two: false
**Step 3**
As a last step, you need to add the new page in the dropdown menu. To do that,
open `source/includes/comparison_table.html.haml` and add an entry of your newly
added comparison page. Again, you can copy one of the entries you'll find inside
and just change its content. Haml files are sensitive to indentation, so be
extra careful:
```haml
%li
= highlight_active_nav_link("Competitor vs. GitLab", "/comparison/gitlab-vs-competitor.html#dropdown")
```
 
Title and description fields are mandatory.
**Step 4**
If you followed the above 3 steps, the new comparison page should be reachable
under `/comparison/gitlab-vs-competitor.html` and you should see it in the
dropdown menu. The last thing you need to do is create the PDF. Follow the
info in [creating comparison PDFs](#comparison-pdfs).
 
`competitor_one` is always GitLab,
`competitor_two` is the competitor we are compared against. Values for these two
fields are `true|false|sortof`.
[comp]: https://about.gitlab.com/comparison/
 
### Update the release list page (under `/release-list`)
 
Loading
Loading
@@ -370,6 +453,58 @@ the 22th is 8.12, the month should be 8 (i.e August for 8.11), not 9.
 
The release-list page will be updated after `bundle exec rake build`.
 
### Update the projects page (under `/handbook/engineering/projects`)
GitLab Engineering Projects page is generated using information stored in
`data/projects.yml` and `data/team.yml` files. Edit these files to add a
project and assign product owners / maintainers / reviewers.
* Typically, product owner is a Product Team member whose responsibilities
include having a vision of a project's development, scheduling a work and
allocating required resources.
* Maintainer is usually a team member who is responsible for the final review
and has ability to merge changes into the `master` branch / default branch.
* A reviewer is a team member who is responsible for reviewing changes and
providing a quick feedback during multiple review iterations.
To assign someone to a project it is necessary to add a `projects` section to
team member's entry in `data/team.yml`. See an example below.
```yaml
- name: Full Name
locality: Some City
# [...]
gitlab: gitlab-com-handle
projects:
some-project: owner
gitlab-ce: maintainer backend
gitlab-ee: maintainer backend
gitlab-shell: reviewer
story: Bio that appears on the team page.
```
Note that each project, that user is involved in, is referenced by a key.
The key needs to be defined in `data/projects.yml` as well.
```yaml
gitlab-ce:
name: GitLab Community Edition (CE)
path: gitlab-org/gitlab-ce
# [...]
```
If corresponding key does not exist in `data/projects.yml` then CI pipeline
will fail and an appropriate RSpec failure will inform you which key is
missing.
Supported roles are only `owner`, `maintainer` and `reviewer`. A text provided
after a role name is an arbitrary description, that will appear next to a
team member's gitlab.com handle on a generated page.
See [Engineering Projects Page](https://about.gitlab.com/handbook/engineering/projects) in the Handbook.
## Production build
 
Before building the static files, ensure you have a GitLab.com `PRIVATE_TOKEN`
Loading
Loading
@@ -395,15 +530,34 @@ derived from a corresponding 'printable' HTML file, such as
 
The PDF files are generated by [pandoc](http://pandoc.org/) using
[LaTeX/XeTeX](http://xetex.sourceforge.net/). Global PDF parameters such
as page margins are configured in pdf_template.tex.
as page margins are configured in `pdf_template.tex`.
 
### Install PDF dependencies
 
On OS X: run `brew install pandoc` and install [Basic
TeX](https://tug.org/mactex/morepackages.html).
There are two kinds of PDFs created: the comparison pages ones and all the others.
 
For the comparison PDFs you will need to run the following on OS X:
`brew cask install wkhtmltopdf`
---
For the comparison PDFs you will need to install [wkhtmltopdf].
On macOS:
```
brew cask install wkhtmltopdf
```
---
For all the others you need [pandoc](http://pandoc.org/installing.html). On
macOS run:
```
brew install pandoc
```
Then, install [Basic TeX](https://tug.org/mactex/morepackages.html).
[wkhtmltopdf]: https://wkhtmltopdf.org/downloads.html
 
### PDF development
 
Loading
Loading
@@ -448,18 +602,27 @@ website, you have to:
 
### Comparison PDFs
 
>**Notes:**
- Before creating the PDF for a new comparison page, you need to have
[created the page](#create-or-update-the-comparison-pages-under-comparison)
beforehand.
- Make sure you have all [PDF dependencies installed](#install-pdf-dependencies).
The comparison PDFs are generated in a slightly different way and require a
different command to be run. Before the PDFs can be generated the website
needs to be built locally by running the following:
 
`bundle exec middleman build`
```
bundle exec middleman build
```
 
After running that you can now run the following to generate the PDFs:
 
`bundle exec rake comparison_pdfs`
```
bundle exec rake comparison_pdfs
```
 
Once you have done that you are free to commit and push these to GitLab.com
to then be merged into master.
Once you have done that you are free to commit and push these to GitLab.com.
 
## Custom Generators
 
Loading
Loading
@@ -500,15 +663,6 @@ by pointing your browser to http://localhost:8000.
 
[gh-livereload]: https://github.com/middleman/middleman-livereload/issues/60
 
## Conclusion
In case someone forgot the most important commands and is catting this file from the command line we end by listing them:
```
bundle exec rake new_post
bundle exec middleman
```
## Review Apps
 
Thanks to the [Review Apps], the `www-gitlab-com` project supports live reviewing
Loading
Loading
@@ -530,3 +684,12 @@ Beware that:
Review Apps.
 
[review apps]: https://docs.gitlab.com/ce/ci/review_apps/
## Conclusion (please leave this at the bottom of the doc)
In case someone forgot the most important commands and is catting this file from the command line we end by listing them:
```
bundle exec rake new_post
bundle exec middleman
```
Loading
Loading
@@ -6,5 +6,5 @@ for filename in public/comparison/pdfs/*.html; do
 
wkhtmltopdf --margin-left 0 --margin-right 0 --margin-top 0 --zoom 3 $filename $pdffilename
 
echo "✅ PDF pdffilename generated!"
echo "✅ PDF $pdffilename generated!"
done
Loading
Loading
@@ -20,7 +20,7 @@ page '/*.txt', layout: false
 
set :haml, {
ugly: true,
format: :html5
format: :xhtml
}
 
activate :syntax, line_numbers: false
Loading
Loading
@@ -84,15 +84,19 @@ org_chart = OrgChart.new
proxy "/team/structure/index.html", "/team/structure/template.html", locals: { team_data_tree: org_chart.team_data_tree }, ignore: true
 
# Proxy comparison PDF pages
data.comparisons.each do |key, comparison|
data.comparisons.comparisons.each do |key, comparison|
file_name = key.dup.gsub(/_/, '-')
proxy "/comparison/pdfs/#{file_name}.html", "/comparison/pdfs/template.html", locals: { comparison_block: comparison }, ignore: true
proxy "/comparison/pdfs/#{file_name}.html", "/comparison/pdfs/template.html", locals: {
comparison_block: comparison,
key_one: comparison.product_one.to_sym,
key_two: comparison.product_two.to_sym
}, ignore: true
end
 
# GitLab Projects
proxy '/handbook/engineering/projects/index.html',
'/handbook/engineering/projects/template.html',
locals: { team: Gitlab::Homepage::Team.build! },
locals: { team: Gitlab::Homepage::Team.new },
ignore: true
 
# Proxy vacancy pages
Loading
Loading
Loading
Loading
@@ -39,7 +39,7 @@
- url: https://addons.opera.com/en/extensions/details/octotree/
title: Octotree on Opera Add-ons Store
- url: https://github.com/buunguyen/octotree#install-on-safari
title: Install Octotree on Safari
title: Install Octotree on Safari
- title: Git2Go
content: The Git client for iPhone and iPad you always wanted
links:
Loading
Loading
@@ -112,6 +112,11 @@
links:
- url: https://github.com/NARKOZ/gitlab
title: Repository on GitHub
- title: "gitlabr"
content: R client for GitLab REST API.
links:
- url: https://gitlab.com/jirkalewandowski/gitlabr
title: Development repository on GitLab.com
- title: Perl
content: Net::GitLab Perl Client talks to a GitLab installation via its API.
links:
Loading
Loading
@@ -239,6 +244,11 @@
links:
- url: https://github.com/Evolveum/connector-gitlab
title: Repository on GitHub
- title: GitLab external user creator
content: Web app which allows internal users to create new users for collaborators (as external users).
links:
- url: https://github.com/dolfim/gitlab_user_creator
title: Repository on GitHub
- title: create-gitlab-repo
content: Simple script creating a GitLab project from the local repository in the current directory.
links:
Loading
Loading
@@ -279,11 +289,21 @@
links:
- url: https://teamweek.com/
title: Teamweek
- title: SwaggerHub
content: SwaggerHub is an API development platform that allows users to quickly build, document and deploy their APIs using the Swagger framework. SwaggerHub’s GitLab integration lets users push-generate their API’s definition and code to the GitLab repository of their choice and keep them in sync, thus managing their API lifecycle in GitLab from a single source-of-truth.
links:
- url: https://app.swaggerhub.com/help/integrations/gitlab-sync
title: SwaggerHub
- title: Invantive Query Tool for SQL
content: With the Invantive Query Tool is all the data, stored in GitLab, available on demand. It empowers to execute queries, capture and analyze data and create business reports in real-time.
links:
- url: https://www.gitlab-apps.com/index.html?utm_source=gitlab-query-tool#query-tool
title: Invantive Query Tool for SQL
- title: WakaTime
content: Fully automatic time tracking generated from your programming activity in your editor.
links:
- url: https://wakatime.com/integrations
title: WakaTime
- title: Toggl
content: Time tracker that is built for speed and ease of use.
links:
Loading
Loading
@@ -367,7 +387,7 @@
- title: GitLab CI
content: GitLab Continuous Integration (CI) integrates with your GitLab installation to run tests for your projects. Login with GitLab account, add a project with one click and enjoy running your tests. GitLab CI is on-premises software that you can install and use on your server(s) and is supported by GitLab the company.
links:
- url: https://about.gitlab.com/gitlab-ci/
- url: /features/gitlab-ci-cd/
title: GitLab CI
- title: BuildKite
content: BuildKite runs builds on GitLab commits, either on self-hosted GitLab repositories or GitLab.com.
Loading
Loading
@@ -451,7 +471,7 @@
- url: https://visualstudiogallery.msdn.microsoft.com/abafc7d6-dcaa-40f4-8a5e-d6724bdb980c
title: visualstudiogallery
- title: GitKraken
content: GitKraken is a visual git client. Please note that it requires you to sign up with a working email.
content: The downright luxurious Git client for Windows, Mac & Linux.
links:
- url: https://www.gitkraken.com/
title: GitKraken.com
Loading
Loading
@@ -500,6 +520,11 @@
links:
- url: https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/integration/oauth_provider.md
title: GitLab as OAuth2 authentication service provider
- title: PHP OAuth2 client
content: Let users of your application authenticate through a public or private GitLab instance.
links:
- url: https://packagist.org/packages/omines/oauth2-gitlab
title: GitLab Provider for the PHP League OAuth 2.0 Client
- title: Scrum Boards
id: scrum-boards
applications:
Loading
Loading
@@ -535,7 +560,7 @@
- title: Perforce Helix GitSwarm
content: Perforce Helix GitSwarm is a git collaboration tool built on GitLab.
links:
- url: http://www.perforce.com/git"
- url: http://www.perforce.com/git
title: perforce.com/git
- title: O'Reilly Atlas
content: 'Technical publisher O''Reilly Media has build their own frontend on top of a GitLab backend. They published a <a href="https://www.youtube.com/watch?v=IHEbYsaKW9Y&feature=youtu.be">video of the app</a> <a href="https://github.com/oreillymedia/backbone-gitlab/">Backbone for GitLab API library</a> they developed for this.'
Loading
Loading
@@ -547,21 +572,3 @@
links:
- url: https://www.penflip.com/
title: penflip.com
- title: GitLab Runners
id: gitlab-runners
applications:
- title: Official GitLab Runner
content: Written in Go, supported on multiple operating systems and includes Docker support.
links:
- url: https://gitlab.com/gitlab-org/gitlab-ci-multi-runner#installation
title: Official GitLab Runner
- title: Unofficial GitLab Runner for Scala/Java
content: 'An unofficial GitLab Runner written in Java, it has less features than <a href="https://gitlab.com/gitlab-org/gitlab-ci-multi-runner">our official Runner</a>'
links:
- url: https://github.com/nafg/gitlab-ci-runner-scala
title: Unofficial GitLab Runner for Scala/Java
- title: Unofficial GitLab Runner for Node
content: 'An unofficial GitLab Runner written in Node, it has less features than <a href="https://gitlab.com/gitlab-org/gitlab-ci-multi-runner">our official Runner</a>'
links:
- url: https://www.npmjs.com/package/gcr
title: Unofficial GitLab Runner for Node
This diff is collapsed.
title: "Bitbucket Server vs. GitLab CE/EE"
pdf: gitlab-ce-ee-vs-bitbucket-server.pdf
competitor_one:
name: 'GitLab CE/EE'
logo: '/images/comparison/ce-ee-gitlab-logo.svg'
competitor_two:
name: 'Bitbucket Server'
logo: '/images/comparison/bitbucket-logo.svg'
last_updated: 'February 08, 2017'
features:
- title: "Built-in Continuous Integration tool"
description: "Easy-to-set up, performant, stable and elegant continuous integration with every GitLab installation."
link_description: "Learn about the benefits of our CI tool"
link: https://docs.gitlab.com/ce/ci/
competitor_one: true
competitor_two: false
- title: "Track app deployments with Deploy Boards"
description: "Deploy Boards offer a consolidated view of the current health and status of each CI environment running on Kubernetes, pod by pod. Not available with BitBucket Pipelines."
link_description: "Learn more about Deploy Boards"
link: https://docs.gitlab.com/ee/user/project/deploy_boards.html
competitor_one: true
competitor_two: false
- title: "Docker Registry support"
description: "GitLab Container Registry is a secure and private registry for Docker images. It allows for easy upload and download of images from GitLab CI. It is fully integrated with Git repository management."
link_description: "Documentation on Container Registry"
link: https://docs.gitlab.com/ce/user/project/container_registry.html
competitor_one: true
competitor_two: false
- title: "Lock Files"
description: "File locking in GitLab Enterprise Edition allows you to lock any file or directory. This ensures that no one will work on or overwrite work that can't be merged easily, for instance when working with art assets or other non-text files."
link_description: "Read the File Locking documentation"
link: http://docs.gitlab.com/ee/user/project/file_lock.html
competitor_one: true
competitor_two: false
- title: "More value with everything you need in one solution"
description: "To replace GitLab, you'd need a combination of Bitbucket server, JIRA, Confluence, and Bamboo, at a much higher cost."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Great user interface"
description: "GitLab has a really nice user interface that your team will love, and also enjoy working with. Bitbucket is not known for this."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Integrated issue tracking"
description: "GitLab includes an issue tracker which you can link to any merge request. Bitbucket doesn't have that."
link_description: "Issue tracker"
link: https://gitlab.com/gitlab-org/gitlab-ce/issues
competitor_one: true
competitor_two: false
- title: "Better activity feed and visualization"
description: "Collaborative activity feed to help everyone understand what is happening in a project and graphical view of the commit history."
link_description: "See Our Activity Feed"
link: https://gitlab.com/gitlab-org/gitlab-ce/activity
competitor_one: true
competitor_two: false
- title: "Search files with fuzzy file finder"
description: "GitLab provides a way to search a file in your repository in one keystroke. Bitbucket makes you browse a file tree."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "Full, powerful search"
description: "Search through all your code, issues, wikis, commits and commits messages, groups and projects. Built into GitLab."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "No need to manage multiple licenses"
description: "GitLab EE needs a license, but doesn't require any validation or separate licenses for separate servers. With Bitbucket Server (Data Center), licenses are linked to servers, requiring management of licenses over servers. You can deploy 100 instances of GitLab EE for the same price as a single instance. You only pay for the total amount of users, not for how you choose to manage and scale the software."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Easy configuration"
description: "GitLab can be easily configured through ENV variables and YAML files. This makes maintaining, upgrading and deploying GitLab easy to automate. Bitbucket Server requires extensive manual configuration."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "One integrated tool"
description: "Bitbucket requires the integration of multiple 3rd party tools to complete the software development lifecycle. GitLab has a completely integrated solution that covers the entire development lifecycle."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "Runs on metal"
description: "GitLab can run on metal, if you choose to. So does Bitbucket."
link_description: ""
link:
competitor_one: true
competitor_two: true
- title: "HA setups"
description: "For mission critical releases, you cannot afford downtime. GitLab offers support for HA, as well as Bitbucket."
link_description: "More information about active servers"
link: https://about.gitlab.com/high-availability/
competitor_one: true
competitor_two: true
- title: "Multiple approvals in code review"
description: "In GitLab, to ensure strict code review, you can require a specific number of approvals on a merge request by different users before being able to merge it. You can undo an approval by removing it after the fact."
link_description: "Approvals Documentation"
link: https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_approvals.html
competitor_one: true
competitor_two: false
- title: "Ease of Migration"
description: "GitLab lets you easily migrate all repos and merge request data from your previous provider."
link_description: ""
link:
competitor_one: true
competitor_two: sortof
- title: "Issue Weights"
description: "GitLab lest you manage issues using Agile practices by setting the weight of an issue. Bitbucket does not have issues."
link_description: "Issue Weights Documentation"
link: https://docs.gitlab.com/ee/workflow/issue_weight.html
competitor_one: true
competitor_two: false
- title: "Prevent committing secrets in the repositories"
description: "GitLab provides a way to avoid committing sensitive files to your repositories automatically."
link_description: "Documentation"
link: https://docs.gitlab.com/ee/push_rules/push_rules.html#prevent-pushing-secrets-to-the-repository
competitor_one: true
competitor_two: false
- title: "Ability to set a project size"
description: "GitLab allows to set a project size limit at a global, group and project level."
link_description: "Documentation on account and limit settings"
link: https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html
competitor_one: true
competitor_two: false
- title: "Multiple issues and merge request templates"
description: "With GitLab, you can create multiple templates for issues and merge requests in your project to ensure all information is entered correctly and to make it easy to standardize. Bitbucket does not have issues."
link_description: "Templates for Issues and Merge Requests Documentation"
link: https://docs.gitlab.com/ee/customization/issue_and_merge_request_template.html
competitor_one: true
competitor_two: sortof
- title: "Geographic Replication with GitLab Geo"
description: "To improve collaboration, remote teams need the ability to be able to seamlessly work across geographical boundaries. GitLab Geo creates read only mirrors of your GitLab instance so your remote employees can clone and fetch large repos quickly, while Bitbucket has no similar feature."
link_description: "Read the Geo docs for more information"
link: http://docs.gitlab.com/ee/gitlab-geo/
competitor_one: true
competitor_two: false
- title: "Application performance monitoring"
description: "GitLab collects and displays performance metrics for deployed apps, leveraging Prometheus. Developers can quickly and easily determine the impact of any changes, without leaving GitLab. Bitbucket requires a 3rd party product, adding additional cost and separate workflows."
link_description: "Learn more about monitoring deployed apps"
link: http://docs.gitlab.com/ce/user/project/integrations/prometheus.html
competitor_one: true
competitor_two: false
- title: "Monitoring built-in"
description: "GitLab ships with an open source monitoring solution, Prometheus, which offers world-class monitoring of the GitLab service. BitBucket exposes a limited set of metrics via Java Management Extensions."
link_description: "How to monitor GitLab"
link: http://docs.gitlab.com/ce/administration/monitoring/prometheus/index.html
competitor_one: true
competitor_two: sortof
- title: "Chat integration"
description: "GitLab ships with Mattermost, an open-source Slack alternative. Bitbucket sort of integrates with 3rd party chat software, but it's not bundled with anything."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "Commit graph and reporting tools"
description: "GitLab provides commit graphs and reporting tools about collaborators' work. Bitbucket requires a paid plugin to provide this functionality."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "Access to and possibility to modify your source code"
description: "GitLab Enterprise Edition is publically readable, meaning you can scan or modify the code to meet your security and development needs. Code in Bitbucket is proprietary, meaning you cannot edit or view the source code."
link_description: "Read the GitLab Enterprise Edition license."
link: https://gitlab.com/gitlab-org/gitlab-ee/blob/master/LICENSE
competitor_one: true
competitor_two: false
- title: "Ability to block certain filetypes to be pushed"
description: "GitLab allows you to define rules to prevent certain filetypes to be pushed. Bitbucket requires a paid plugin to achieve this functionality."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "Message banner on all pages"
description: "GitLab allows administrators to write message banners that appear on all pages. Bitbucket doesn't allow this."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "Email notifications and todos"
description: "GitLab provides advanced notification mechanisms to let developers know what happens in the project. Bitbucket requires a plugin to achieve this."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "Reduce costs with simple licence management"
description: "Bitbucket requires integration with multiple products, each with different billing cycles. Bitbucket also has complex licensing rules, whereas GitLab has the simplest licence management, and is simply the most comprehensive and affordable software development solution on the market."
link description:
link:
competitor_one: true
competitor_two: false
- title: "Reduce 3rd party maintenance with an integrated solution"
description: "Bitbucket 3rd party integrations mean that if something breaks, you will need to contact both vendors to address the problem, resulting in longer wait times. With an integrated solution, GitLab’s rapid response time to issues, means that you can be back up and running in no time."
link description:
link:
competitor_one: true
competitor_two: false
- title: "Omnibus Installation to get up and running quicker"
description: "An installation of Bitbucket requires the implementation of multiple products, each with their own complexities. GitLab has an omnibus package which spans the entire software supply chain, and has all dependencies built in for a simple and straightforward installation and configuration."
link description:
link:
competitor_one: true
competitor_two: false
- title: "Review your teams performance with Cycle Analytics"
description: "Team want to improve their each stage of their workflow, but are faced with no way to measure this with GitHub with it’s 3rd party integrations. With built in Cycle Analytics, GitLab records the median time it takes the team to complete each stage in their workflow from idea to production, and provides insights into areas for improvement."
link description:
link:
competitor_one: true
competitor_two: false
- title: "New features every month"
description: "GitLab is updated with new features and improvements every month on the 22nd."
link_description: ""
link:
competitor_one: true
competitor_two: false
title: "SaaS vs. GitLab CE/EE"
pdf: gitlab-ce-ee-vs-sass.pdf
competitor_one:
name: 'GitLab CE/EE'
logo: '/images/comparison/ce-ee-gitlab-logo.svg'
competitor_two:
name: 'SaaS'
logo: 'null'
last_updated: 'January 31, 2017'
features:
- title: "Containment"
description: "Containing your company's IP behind the company's firewall gives you protection from unauthorized access. Learn from the lessons of Code Space"
link_description: "Lessons from Code Space"
link: http://www.infoworld.com/article/2608076/data-center/murder-in-the-amazon-cloud.html
competitor_one: true
competitor_two: false
- title: "Integrations"
description: "Integrating with Authentication and Authorization (LDAP / AD), issue tracking, CI, deployment and other tools such as ALM, PLM, Agile and Automation tools."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Control"
description: "Take control of maintenance downtime, don't be at the mercy of your hosting provider. Control how and where your code is backed up and stored."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Choice and Flexibility"
description: "GitLab CE/EE can be installed on physical servers, virtualized servers (dedicated or shared), purpose-built appliances and virtualized appliances. These aren’t available with hosted solutions. Likewise, most on-premises servers can be deployed on a variety of operating systems and there’s more choice of on-premises solutions in general."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Retrieval"
description: "Getting your IP back from cloud vendors that store data in proprietary formats can be a costly and lengthy process. No such trouble with GitLab CE/EE."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "In good company"
description: "GitLab is the most adopted on-premises solution for developer collaboration, deployed at over 100,000 organizations worldwide."
link_description: ""
link:
competitor_one: true
competitor_two: false
title: "GitLab EE vs. GitLab CE"
pdf: gitlab-ce-vs-gitlab-ee.pdf
description: "GitLab Community Edition is great for personal projects or small teams with minimal user management and workflow control needs. GitLab Enterprise Edition offers ALL the benefits of Community Edition, with added support for large companies which often have distributed teams who need advanced workflow controls and security for their professional projects, High Availability, and Premium Support."
competitor_one:
name: 'GitLab CE'
logo: '/images/comparison/ce-gitlab-logo.svg'
competitor_two:
name: 'GitLab EE'
logo: '/images/comparison/ee-gitlab-logo.svg'
last_updated: 'February 14, 2017'
feature_page: "All the features listed on"
feature_page_link_description: "the Products page"
feature_page_link_description_2: ", plus the following:"
feature_page_link: http://about.gitlab.com/products/#compare-options
features:
- title: "File Locking"
description: "Working with multiple people on the same file can be a risk. Conflicts when merging a non-text file are hard to overcome and will require a lot of manual work to resolve. With GitLab Enterprise Edition Premium, File Locking helps you avoid merge conflicts and better manage your binary files by preventing everyone, except you, from modifying a specific file or entire directory."
link_description: ""
link:
competitor_one: false
competitor_two: true
- title: "Avoid Downtime"
description: "For mission critical releases, you cannot afford downtime. With GitLab Enterprise Edition, a Support Engineer will guide you and help you identify your specific HA needs, and map out an appropriate architecture."
link_description: ""
link:
competitor_one: false
competitor_two: true
- title: "Advanced Support"
description: "While the best tools are intuitive, there will be a time when you'll need to troubleshoot. GitLab Enterprise Edition gives your team a single point of contact for all of your onboarding, training, upgrading, and troubleshooting needs. Purchasing Enterprise Edition means that support is there 24/7, with live upgrade assistance so you can release code faster."
link_description: ""
link:
competitor_one: false
competitor_two: true
- title: "Advanced audit logs"
description: "To maintain the integrity of your code, GitLab Enterprise Edition gives admins the ability to view any modifications made within the GitLab server in an advanced audit log system, so you can control, analyze and track every change."
link_description: ""
link:
competitor_one: false
competitor_two: true
- title: "Admin Control"
description: "GitLab Enterprise Edition gives your Admin’s the ability to automatically sync groups and manage SSH-keys, permissions, and authentication, so you can focus on building your product, not configuring your tools."
link_description: ""
link:
competitor_one: false
competitor_two: true
- title: "Merge Request Approval"
description: "When a project requires multiple sign-offs, GitLab Enterprise Edition enables you to make sure every merge request is approved by one or more people. Merge request approvals allow you to set the number of necessary approvals and predefine a list of approvers that will need to approve every merge request in a project, and in-turn improve your code’s quality."
link_description: ""
link:
competitor_one: false
competitor_two: true
- title: "LDAP group sync"
description: "GitLab Enterprise Edition gives your Admin’s the ability to automatically sync groups and manage SSH-keys, permissions, and authentication, so you can focus on building your product, not configuring your tools."
link_description: ""
link:
competitor_one: false
competitor_two: true
- title: "Multiple Issue Boards"
description: "Large companies often have hundreds of different projects, all with different moving parts at the same time. GitLab Enterprise Edition allows for multiple issue boards for a single project so you can to plan, organize, and visualize a workflow for a feature or product release. Multiple issue boards are particularly useful for large projects with more than one team or in situations where a repository is used to host the code of multiple products."
link_description: "Multiple Issue Boards"
link: https://docs.gitlab.com/ee/user/project/issue_board.html
competitor_one: false
competitor_two: true
- title: "Track app deployments with Deploy Boards"
description: "Deploy Boards offer a consolidated view of the current health and status of each CI environment running on Kubernetes, pod by pod."
link_description: "Learn more about Deploy Boards"
link: https://docs.gitlab.com/ee/user/project/deploy_boards.html
competitor_one: false
competitor_two: true
- title: "Auditor users"
description: "Auditor users are users who are given read-only access to all projects, groups, and other resources on the GitLab instance."
link_description: "Auditor users"
link: https://docs.gitlab.com/ee/administration/auditor_users.html
competitor_one: false
competitor_two: true
title: "Bitbucket.org vs. GitLab.com"
pdf: gitlab-com-vs-bitbucket-org.pdf
competitor_one:
name: 'GitLab.com'
logo: '/images/comparison/gitlab-logo.svg'
competitor_two:
name: 'Bitbucket.org'
logo: '/images/comparison/bitbucket-logo.svg'
last_updated: 'February 14, 2017'
features:
- title: "Free unlimited collaborators"
description: "With GitLab.com, you don't have to start paying when you have more than 5 collaborators across all your private repositories."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Free CI with Shared or Own Runner"
description: "GitLab.com has shared runners that allow you to use GitLab CI completely free. Alternatively, you can set up your own Runner for faster build processing or special requirements."
link_description: ""
link:
competitor_one: true
competitor_two: sortof
- title: "Track app deployments with Deploy Boards"
description: "Deploy Boards offer a consolidated view of the current health and status of each CI environment running on Kubernetes, pod by pod. Not available with BitBucket Pipelines."
link_description: "Learn more about Deploy Boards"
link: https://docs.gitlab.com/ee/user/project/deploy_boards.html
competitor_one: true
competitor_two: false
- title: "Fast page load"
description: "Bitbucket.org has faster pageloads than GitLab.com right now, we're actively working on improving this. Self-hosted instances of GitLab CE/EE will be performant up to thousands of users."
link_description: "Read more"
link: https://gitlab.com/gitlab-com/operations/issues/42/
competitor_one: false
competitor_two: true
- title: "Flexible permissions"
description: "Set permissions according to people's role, rather than either read or write access to a repository. Don't share the source code with people that only need access to the issue tracker."
link_description: "See the various roles"
link: https://docs.gitlab.com/ce/user/permissions.html
competitor_one: true
competitor_two: false
- title: "Innersourcing"
description: "Internal projects in GitLab allow you to promote innersourcing of your internal repositories."
link_description: "Find out more about innersourcing"
link: https://about.gitlab.com/2014/09/05/innersourcing-using-the-open-source-workflow-to-improve-collaboration-within-an-organization/
competitor_one: true
competitor_two: false
- title: "Work-in-Progress Protection"
description: "Simply add 'WIP' to the title of a merge request to prevent anyone from merging it. This gives you all the code review power of merge requests, while protecting unfinished work."
link_description: "WIP Merge documentation"
link: https://docs.gitlab.com/ce/user/project/wip_merge_requests.html
competitor_one: true
competitor_two: false
- title: "Commit graph and reporting tools"
description: "GitLab provides commit graphs and reporting tools about collaborators' work. Bitbucket does not have that."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "Email notifications and todos"
description: "GitLab provides advanced notification mechanisms to let developers know what happens in the project."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "Ability to block certain filetypes to be pushed"
description: "GitLab allows you to define rules to prevent certain filetypes to be pushed. Bitbucket requires a paid plugin to achieve this functionality."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "The best place for large open source projects"
description: "GitLab is meant to be the best place for any software project. The team behind GitLab is addressing issues that maintainers and contributors to large open source projects are facing, to make it easier to do both. Bitbucket hasn't made significant steps to reach this stage."
link_description: "Making GitLab better for large open source projects"
link: https://about.gitlab.com/2016/01/15/making-gitlab-better-for-large-open-source-projects/
competitor_one: sortof
competitor_two: false
- title: "Powerful Issue Tracker"
description: "Quickly set the status, assignee or milestone for multiple issues at the same time or easily filter them on any properties. See milestones and issues across projects. Bitbucket does not have issues."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "Due date"
description: "In GitLab, you can set a due date for individual issues. This is very convenient if you have small tasks with a specific deadline. Bitbucket does not have issues."
link_description: "Due dates documentation"
link: https://docs.gitlab.com/ce/user/project/issues/due_dates.html
competitor_one: true
competitor_two: false
- title: "Move issues between projects"
description: "You can move issues between projects in GitLab. All links, history and comments will be copied and the original issue will reference the newly moved issue. This makes working with multiple issue trackers much easier. Bitbucket does not have issues."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "Group-level milestones"
description: "View all the issues for the milestone you’re currently working on across multiple projects. Bitbucket does not have milestones."
link_description: "Example milestone for GitLab 8.2 (need to be logged in)"
link: https://gitlab.com/groups/gitlab-org/milestones/8-2?title=8.2
competitor_one: true
competitor_two: false
- title: "Create new branches from Issues"
description: "In GitLab, you can quickly create a new branch from an issue on the issue tracker. It will include the issue number and title automatically, making it easy to track which branch belongs to which issue. Bitbucket does not have issues."
link_description: "See how in our documentation"
link: https://docs.gitlab.com/ce/user/project/repository/web_editor.html#create-a-new-branch-from-an-issue
competitor_one: true
competitor_two: false
- title: "Application performance monitoring"
description: "GitLab collects and displays performance metrics for deployed apps, leveraging Prometheus. Developers can quickly and easily determine the impact of any changes, without leaving GitLab. Bitbucket requires a 3rd party product, adding additional cost and separate workflows."
link_description: "Learn more about monitoring deployed apps"
link: http://docs.gitlab.com/ce/user/project/integrations/prometheus.html
competitor_one: true
competitor_two: false
- title: "Cycle Analytics"
description: "GitLab provides a dashboard that lets teams measure the time it takes to go from an idea to production. GitLab can provide this data because it has all the tools built-in: from the idea, to the CI, to code review, to deploy to production. Bitbucket can't provide this data."
link_description: "Feature Highlight: Cycle Analytics"
link: https://about.gitlab.com/2016/09/21/cycle-analytics-feature-highlight/
competitor_one: true
competitor_two: false
- title: "Slash commands"
description: "GitLab provides a convenient way to change meta data of an issue or merge request withouth leaving the comment field with slash commands."
link_description: "Documentation about slash commands"
link: https://docs.gitlab.com/ce/user/project/slash_commands.html
competitor_one: true
competitor_two: false
- title: "Issue board"
description: "Bitbucket has acquired Trello, but is not integrated with it. GitLab has built-in Issue boards, integrated with the rest of the tools."
link_description: "Feature highlight: Issue Boards"
link: https://about.gitlab.com/2016/08/22/announcing-the-gitlab-issue-board/
competitor_one: true
competitor_two: sortof
- title: "Time tracking"
description: "Time Tracking in GitLab lets your team add estimates and record time spent on issues and merge requests. Bitbucket doesn't have this feaure out of the box."
link_description: "Check the Time tracking feature"
link: https://about.gitlab.com/features/time-tracking/
competitor_one: true
competitor_two: false
- title: "Built-in Docker Registry"
description: "GitLab Container Registry is a secure and private registry for Docker images. It allows for easy upload and download of images from GitLab CI. It is fully integrated with Git repository management."
link_description: "Documentation on Container Registry"
link: https://docs.gitlab.com/ce/user/project/container_registry.html
competitor_one: true
competitor_two: false
- title: "New features every month"
description: "GitLab is updated with new features and improvements every month on the 22nd."
link_description: ""
link:
competitor_one: true
competitor_two: false
title: "GitHub Enterprise vs. GitLab EE"
pdf: gitlab-ee-vs-github-enterprise.pdf
competitor_one:
name: 'GitLab Enterprise Edition'
logo: '/images/comparison/ee-gitlab-logo.svg'
competitor_two:
name: 'GitHub Enterprise'
logo: '/images/comparison/github-logo.svg'
last_updated: 'January 31, 2017'
features:
- title: "Handles huge repositories well"
description: "Big repository? Huge (>5GB) binary files? No problem. GitLab is built to handle very large repositories, and Git LFS is supported."
link_description: "Git LFS documentation"
link: https://docs.gitlab.com/ee/workflow/lfs/manage_large_binaries_with_git_lfs.html
competitor_one: true
competitor_two: true
- title: "One integrated tool"
description: "GitHub requires the integration of multiple 3rd party tools to complete the software development lifecycle. GitLab has a completely integrated solution that covers the entire development lifecycle."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "Access to the server"
description: "You have complete control of the server/instance, so you can install additional software (intrusion detection, performance monitoring, etc.) and view log files on the server itself."
link_description: "Learn more about logging"
link: https://docs.gitlab.com/ce/administration/logs.html
competitor_one: true
competitor_two: false
- title: "Runs on metal"
description: "GitLab can run on metal, if you choose to. GitHub needs to be run in a VM."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "HA setups"
description: "For mission critical releases, you cannot afford downtime. GitHub bundles everything (app server, database etc) into a virtual appliance, while GitLab offers support for HA. GitHub also requires you to shut down your server for back-ups preventing the delivery of code, while with GitLab, you can work in readonly mode during backups."
link_description: "More information about active servers"
link: https://about.gitlab.com/high-availability/
competitor_one: true
competitor_two: false
- title: "Run your own software on your instance"
description: "You are free to run your own software on the instance that GitLab is running on. Have your own intrusion detection system? No problem."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Use your configuration management software"
description: "GitHub requires the complex configuration of integration tools, from CI to chat apps. With GitLab, you can use your choice of configuration management software, from Puppet, Chef, Ansible for quick and straightforward implementation."
link_description: "Read about configuration management here"
link: https://about.gitlab.com/installation/
competitor_one: true
competitor_two: false
- title: "Track app deployments with Deploy Boards"
description: "Deploy Boards offer a consolidated view of the current health and status of each CI environment running on Kubernetes, pod by pod. Not available with most of GitHub's third party CI/CD solutions."
link_description: "Learn more about Deploy Boards"
link: https://docs.gitlab.com/ee/user/project/deploy_boards.html
competitor_one: true
competitor_two: false
- title: "Use standard Unix tools for maintenance and monitoring"
description: "Use the tools you know for monitoring and maintenance, whether they're standard or your own. GitLab doesn't restrict you."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Powerful AD / LDAP integration"
description: "Sync groups, manage SSH-keys, manage permissions, authentication and more. You can manage an entire GitLab instance through the LDAP / AD integration."
link_description: "More information about AD / LDAP integration"
link: https://docs.gitlab.com/ee/administration/auth/ldap.html
competitor_one: true
competitor_two: true
- title: "Multiple approvals in code review"
description: "In GitLab, to ensure strict code review, you can require a specific number of approvals on a merge request by different users before being able to merge it. You can undo an approval by removing it after the fact."
link_description: "Approvals Documentation"
link: https://docs.gitlab.com/ee/user/project/merge_requests/merge_request_approvals.html
competitor_one: true
competitor_two: false
- title: "Ease of Migration"
description: "GitLab lets you easily migrate all repos and merge request data from your previous provider."
link_description: ""
link:
competitor_one: true
competitor_two: sortof
- title: "Chat integration"
description: "GitLab ships with Mattermost, an open-source Slack alternative. GitHub requires the installation or the purchase of an external tool."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "Issue Weights"
description: "GitLab lest you manage issues using Agile practices by setting the weight of an issue."
link_description: "Issue Weights Documentation"
link: https://docs.gitlab.com/ee/workflow/issue_weight.html
competitor_one: true
competitor_two: false
- title: "Custom Push Rules (pre-received hooks)"
description: "GitHub allows site administrators to create pre-received hooks at a global or project level. GitLab also allows the creation of those hooks at a project or global level, but they can be set by either the project owner or an administrator, and provides a simple user interface to define those push rules."
link_description: "Documentation on push rules"
link: https://docs.gitlab.com/ee/push_rules/push_rules.html#prevent-pushing-secrets-to-the-repository
competitor_one: true
competitor_two: sortof
- title: "Prevent committing secrets in the repositories"
description: "GitLab provides a way to avoid committing sensitive files to your repositories automatically."
link_description: "Documentation"
link: https://docs.gitlab.com/ee/push_rules/push_rules.html#prevent-pushing-secrets-to-the-repository
competitor_one: true
competitor_two: false
- title: "Ability to set a project size"
description: "GitLab allows to set a project size limit at a global, group and project level."
link_description: "Documentation on account and limit settings"
link: https://docs.gitlab.com/ee/user/admin_area/settings/account_and_limit_settings.html
competitor_one: true
competitor_two: false
- title: "Multiple issues and merge request templates"
description: "Create a template for issues and merge requests in your project to ensure all information is entered correctly and to make it easy to standardize. While GitHub only allows one template, GitLab allows multiple templates."
link_description: "Templates for Issues and Merge Requests Documentation"
link: https://docs.gitlab.com/ee/customization/issue_and_merge_request_template.html
competitor_one: true
competitor_two: sortof
- title: "Geographic Replication with GitLab Geo"
description: "To improve collaboration, remote teams need the ability to be able to seamlessly work across geographical boundaries. GitLab Geo creates read only mirrors of your GitLab instance so your remote employees can clone and fetch large repos quickly, while GitHub has no similar feature."
link_description: "Read the Geo docs for more information"
link: http://docs.gitlab.com/ee/gitlab-geo/
competitor_one: true
competitor_two: false
- title: "Lock Files"
description: "Working with multiple people on the same file can be a risk. Conflicts when merging a non-text file are hard to overcome and will require a lot of manual work to resolve. With GitLab, File Locking helps you avoid merge conflicts and better manage your binary files by preventing everyone, except you, from modifying a specific file or entire directory."
link_description: "Read the File Locking documentation"
link: http://docs.gitlab.com/ee/user/project/file_lock.html
competitor_one: true
competitor_two: false
- title: "Application performance monitoring"
description: "GitLab collects and displays performance metrics for deployed apps, leveraging Prometheus. Developers can quickly and easily determine the impact of any changes, without leaving GitLab. GitHub requires a 3rd party product, adding additional cost and separate workflows."
link_description: "Learn more about monitoring deployed apps"
link: http://docs.gitlab.com/ce/user/project/integrations/prometheus.html
competitor_one: true
competitor_two: false
- title: "Monitoring built-in"
description: "GitLab ships with an open source monitoring solution, Prometheus, which offers world-class monitoring of the GitLab service. GitHub only provides hardware metrics using SNMP."
link_description: "Documentation about Monitoring"
link: http://docs.gitlab.com/ce/administration/monitoring/prometheus/index.html
competitor_one: true
competitor_two: false
- title: "Access to and possibility to modify your source code"
description: "GitLab Enterprise Edition is publically readable, meaning you can scan or modify the code to meet your security and development needs. The Ruby code in GitHub is proprietary, meaning you cannot edit or view the source code."
link_description: "Read the GitLab Enterprise Edition license."
link: https://gitlab.com/gitlab-org/gitlab-ee/blob/master/LICENSE
competitor_one: true
competitor_two: false
- title: "Reduce costs with simple licence management"
description: "GitHub requires integration with multiple products, each with different billing cycles. GitHub also has complex licensing rules, whereas GitLab has the simplest licence management, and is simply the most comprehensive and affordable software development solution on the market."
link description:
link:
competitor_one: true
competitor_two: false
- title: "Reduce 3rd party maintenance with an integrated solution"
description: "GitHub’s 3rd party integrations mean that if something breaks, you will need to contact both vendors to address the problem, resulting in longer wait times. With an integrated solution, GitLab’s rapid response time to issues, means that you can be back up and running in no time."
link description:
link:
competitor_one: true
competitor_two: false
- title: "Omnibus Installation to get up and running quicker"
description: "An installation of GitHub requires the implementation of multiple products, each with their own complexities. GitLab has an omnibus package which spans the entire software supply chain, and has all dependencies built in for a simple and straightforward installation and configuration."
link description:
link:
competitor_one: true
competitor_two: false
- title: "Review your teams performance with Cycle Analytics"
description: "Team want to improve their each stage of their workflow, but are faced with no way to measure this with GitHub with it’s 3rd party integrations. With built in Cycle Analytics, GitLab records the median time it takes the team to complete each stage in their workflow from idea to production, and provides insights into areas for improvement."
link description:
link:
competitor_one: true
competitor_two: false
- title: "New features every month"
description: "GitLab is updated with new features and improvements every month on the 22nd."
link_description: ""
link:
competitor_one: true
competitor_two: false
title: "GitLab EEP vs. GitLab EES"
pdf: gitlab-ees-vs-gitlab-eep.pdf
competitor_one:
name: 'GitLab CE'
logo: '/images/comparison/ce-gitlab-logo.svg'
competitor_two:
name: 'GitLab EE'
logo: '/images/comparison/ee-gitlab-logo.svg'
features:
- title: "Feature 1"
description: "Lorem ipsum dolor sit amet."
competitor_one: true
competitor_two: true
- title: "Feature 2"
description: "Lorem ipsum dolor sit amet."
competitor_one: true
competitor_two: false
- title: "Track app deployments with Deploy Boards"
description: "Deploy Boards offer a consolidated view of the current health and status of each CI environment running on Kubernetes, pod by pod."
link_description: "Learn more about Deploy Boards"
link: https://docs.gitlab.com/ee/user/project/deploy_boards.html
competitor_one: true
competitor_two: false
title: "GitHub.com vs. GitLab Self-hosted"
pdf: gitlab-self-hosted-vs-github.pdf
competitor_one:
name: 'GitLab Self-hosted'
logo: '/images/comparison/gitlab-logo.svg'
competitor_two:
name: 'GitHub.com'
logo: '/images/comparison/github-logo.svg'
last_updated: 'February 07, 2017'
features:
- title: "Free for private projects"
description: "GitLab is free for unlimited private projects. GitHub doesn't provide private projects for free."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "Built-in Continuous Integration and Continuous Deployment"
description: "GitLab has built-in CI/CD, for free. GitHub has 3rd party CI/CD, which depends on GitHub, that are expensive if your projects are private."
link_description: "Documentation on CI"
link: https://docs.gitlab.com/ce/ci/quick_start/README.html
competitor_one: true
competitor_two: false
- title: "CI/CD best practices"
description: "Everyone in your organization with GitLab is able to setup and manage CI/CD. GitHub and its external CI/CD encourages this knowledge to be restricted to a bunch of devops."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "The most comprehensive import feature set"
description: "GitLab can import projects and issues from more sources (GitHub, BitBucket, Google Code, FogBugz, Gitea and from any git URL) than GitHub or any other VCS. We even have you covered for your move from SVN to Git with comprehensive guides and documentation."
link_description: "Making it easier to get up and running with GitLab"
link: https://docs.gitlab.com/ce/user/project/settings/import_export.html#project-import-export
competitor_one: false
competitor_two: true
- title: "Export projects"
description: "GitLab allows you to export your project to other systems."
link_description: "We don't restrict access to your data"
link: https://docs.gitlab.com/ce/user/project/settings/import_export.html#project-import-export
competitor_one: false
competitor_two: true
- title: "Track app deployments with Deploy Boards"
description: "Deploy Boards offer a consolidated view of the current health and status of each CI environment running on Kubernetes, pod by pod. Not available with most of GitHub's third party CI/CD solutions."
link_description: "Learn more about Deploy Boards"
link: https://docs.gitlab.com/ee/user/project/deploy_boards.html
competitor_one: true
competitor_two: false
- title: "More control during downtime"
description: "When GitHub is down, you have to wait for GitHub to make it available again. When your GitLab instance is down, everything is under your control."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "You decide when you upgrade"
description: "GitLab releases a new version each month, and lets you choose when to upgrade. GitHub updates its product without you being able to do anything about it."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "Flexible permissions"
description: "Set permissions according to people's role, rather than either read or write access to a repository. Don't share the source code with people that only need access to the issue tracker."
link_description: "See the various roles"
link: https://docs.gitlab.com/ce/user/permissions.html
competitor_one: true
competitor_two: false
- title: "Innersourcing"
description: "Internal projects in GitLab allow you to promote innersourcing of your internal repositories."
link_description: "Find out more about innersourcing"
link: https://about.gitlab.com/2014/09/05/innersourcing-using-the-open-source-workflow-to-improve-collaboration-within-an-organization/
competitor_one: true
competitor_two: false
- title: "Faster from Idea to Production"
description: "GitLab has a different approach to code development and deployment compared with GitHub. GitLab focuses on delivering a holistic solution that will see developers from idea to production seamlessly and on a single platform."
link_description: "Learn more about our vision"
link: https://about.gitlab.com/direction/#vision
competitor_one: true
competitor_two: sortof
- title: "Work-in-Progress Protection"
description: "Simply add 'WIP' to the title of a merge request to prevent anyone from merging it. This gives you all the code review power of merge requests, while protecting unfinished work."
link_description: "WIP Merge documentation"
link: https://docs.gitlab.com/ce/user/project/wip_merge_requests.html
competitor_one: true
competitor_two: false
- title: "The best place for large open source projects"
description: "GitLab is meant to be the best place for any software project. The team behind GitLab is addressing issues that maintainers and contributors to large open source projects are facing, to make it easier to do both."
link_description: "Making GitLab better for large open source projects"
link: https://about.gitlab.com/2016/01/15/making-gitlab-better-for-large-open-source-projects/
competitor_one: sortof
competitor_two: true
- title: "Powerful Issue Tracker"
description: "Quickly set the status, assignee or milestone for multiple issues at the same time or easily filter them on any properties. See milestones and issues across projects."
link_description:
link:
competitor_one: true
competitor_two: true
- title: "Due date"
description: "In GitLab, you can set a due date for individual issues. This is very convenient if you have small tasks with a specific deadline."
link_description: "Due dates documentation"
link: https://docs.gitlab.com/ce/user/project/issues/due_dates.html
competitor_one: true
competitor_two: false
- title: "Move issues between projects"
description: "You can move issues between projects in GitLab. All links, history and comments will be copied and the original issue will reference the newly moved issue. This makes working with multiple issue trackers much easier."
link_description:
link:
competitor_one: true
competitor_two: false
- title: "Group-level milestones"
description: "View all the issues for the milestone you’re currently working on across multiple projects."
link_description: "Example milestone for GitLab 8.2 (need to be logged in)"
link: https://gitlab.com/groups/gitlab-org/milestones/8-2?title=8.2
competitor_one: true
competitor_two: false
- title: "Create new branches from Issues"
description: "In GitLab, you can quickly create a new branch from an issue on the issue tracker. It will include the issue number and title automatically, making it easy to track which branch belongs to which issue."
link_description: "See how in our documentation"
link: https://docs.gitlab.com/ce/user/project/repository/web_editor.html#create-a-new-branch-from-an-issue
competitor_one: true
competitor_two: false
- title: "Application performance monitoring"
description: "GitLab collects and displays performance metrics for deployed apps, leveraging Prometheus. Developers can quickly and easily determine the impact of any changes, without leaving GitLab. GitHub requires a 3rd party product, adding additional cost and separate workflows."
link_description: "Learn more about monitoring deployed apps"
link: http://docs.gitlab.com/ce/user/project/integrations/prometheus.html
competitor_one: true
competitor_two: false
- title: "Assign multiple people to an issue / MR"
description: "GitHub allows you to assign multiple people to an issue or pull request. GitLab doesn't allow you to do this, but allows for approvals in merge requests, which offsets this there. For issues, GitLab does not have an equivalent feature, but a feature request has been submitted for this."
link_description: "GitLab issue to implement multiple assignees"
link: https://gitlab.com/gitlab-org/gitlab-ce/issues/13386
competitor_one: false
competitor_two: true
- title: "Allow edits from upstream maintainers in branch"
description: "In GitHub, when a user opens a pull request from a fork, they are given the option that allows the upstream repository contributors to collaborate with them on their new branch. GitLab allows you to restrict pushes very carefully, but does not have this option."
link_description: "GitLab issue to implement the same feature"
link: https://gitlab.com/gitlab-org/gitlab-ce/issues/21975
competitor_one: false
competitor_two: true
- title: "Cycle Analytics"
description: "GitLab provides a dashboard that lets teams measure the time it takes to go from an idea to production. GitLab can provide this data because it has all the tools built-in: from the idea, to the CI, to code review, to deploy to production. GitHub can't provide this data."
link_description: "Feature Highlight: Cycle Analytics"
link: https://about.gitlab.com/2016/09/21/cycle-analytics-feature-highlight/
competitor_one: true
competitor_two: false
- title: "Slash commands"
description: "GitLab provides a convenient way to change meta data of an issue or merge request withouth leaving the comment field with slash commands."
link_description: "Documentation about slash commands"
link: https://docs.gitlab.com/ce/user/project/slash_commands.html
competitor_one: true
competitor_two: false
- title: "Issue board"
description: "GitHub has Projects, which are not tight to labels in any way, making it hard to automatize flows. GitLab has Issue boards. Each list of an issue board is based on a label that exists in your issue tracker. The Issue Board will therefore match the state of your issue tracker in a user friendly way."
link_description: "Feature highlight: Issue Boards"
link: https://about.gitlab.com/2016/08/22/announcing-the-gitlab-issue-board/
competitor_one: true
competitor_two: 'sortof'
- title: "Drag and drop tasks"
description: "You can change the order of tasks in markdown on GitHub. GitLab does not have this ability, but is considering implementing it."
link_description: "See the GitLab issue to implement this"
link: https://gitlab.com/gitlab-org/gitlab-ce/issues/18003
competitor_one: false
competitor_two: true
- title: "Time tracking"
description: "Time Tracking in GitLab lets your team add estimates and record time spent on issues and merge requests. GitHub doesn't have this feaure out of the box."
link_description: "Check the Time tracking feature"
link: https://about.gitlab.com/features/time-tracking/
competitor_one: true
competitor_two: false
- title: "Built-in Docker Registry"
description: "GitLab Container Registry is a secure and private registry for Docker images. It allows for easy upload and download of images from GitLab CI. It is fully integrated with Git repository management."
link_description: "Documentation on Container Registry"
link: https://docs.gitlab.com/ce/user/project/container_registry.html
competitor_one: true
competitor_two: false
- title: "Monitoring built-in"
description: "GitLab ships with an open source monitoring solution, Prometheus, which offers world-class monitoring of the GitLab service. GitHub only provides hardware metrics via SNMP."
link_description: "Documentation about Monitoring"
link: http://docs.gitlab.com/ce/administration/monitoring/prometheus/index.html
competitor_one: true
competitor_two: false
- title: "New features every month"
description: "GitLab is updated with new features and improvements every month on the 22nd."
link_description: ""
link:
competitor_one: true
competitor_two: false
title: "GitSwarm vs. GitLab"
pdf: gitlab-vs-gitswarm.pdf
competitor_one:
name: 'GitLab'
logo: '/images/comparison/gitlab-logo.svg'
competitor_two:
name: 'GitSwarm'
logo: 'null'
last_updated: 'January 31, 2017'
features:
- title: ""
description: ""
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: ""
description: ""
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: ""
description: ""
link_description: ""
link:
competitor_one: true
competitor_two: false
title: "Jenkins vs GitLab CI"
pdf: gitlab-vs-jenkins.pdf
competitor_one:
name: 'GitLab'
logo: '/images/comparison/gitlab-logo.svg'
competitor_two:
name: 'Jenkins'
logo: '/images/comparison/jenkins-logo.svg'
last_updated: 'March 17, 2017'
features:
- title: "No installation needed"
description: "GitLab CI ships with GitLab and is ready to use out of the box."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Minimal build configuration"
description: "GitLab CI requires less configuration for your builds than a similar Jenkins setup."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Extensible"
description: "Both GitLab CI and Jenkins are extensible through an API or plugin system but GitLab's core CI feature set is more comprehensive than Jenkins."
link_description: ""
link:
competitor_one: true
competitor_two: true
- title: "Built for containers and Docker"
description: "GitLab ships with its own Docker container registry, Docker CI Runner and is ready for a complete CI/CD container workflow, while Jenkins requires you to install, configure and maintain additional plugins to create a similar workflow."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Cloud Native"
description: "GitLab CI/CD is Cloud Native, purpose built for the cloud model. GitLab ships with Red Hat OpenShift and Kubernetes support out of the box.'"
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Container debugging on any environment"
description: "Easily debug your containers in any of your environments using the built-in GitLab Web Terminal."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Environment monitoring"
description: "GitLab ships with Prometheous allowing you to monitor the performance of your deployed environments without any addtional setup."
link_description: ""
link: https://prometheus.io/
competitor_one: true
competitor_two: false
- title: "Integrates with Cycle Analytics"
description: "GitLab CI integrates with GitLab Cycle Analytics allowing you see how much of your cycle time from idea to production is spent on development, testing and review."
link_description: ""
link:
competitor_one: true
competitor_two: false
title: "SVN vs. GitLab"
pdf: gitlab-vs-svn.pdf
competitor_one:
name: 'GitLab'
logo: '/images/comparison/gitlab-logo.svg'
competitor_two:
name: 'SVN'
logo: 'null'
last_updated: 'January 31, 2017'
features:
- title: "Distributed"
description: "Git, on which GitLab is built, is fully distributed. Every user has a complete copy of the repository, allowing for much faster access to history, easier branching and an overall better experience."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Access Control"
description: "For someone to commit to a local respository, no access has to be given in Git. At the same time, the owner of the canonical repository has the ability to restrict pushes to the repository or certain branches."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Powerful Branching"
description: "A branch in Git contains the entire history that preceeds it. It's also created or moved towards instantly and easily shared."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Speed"
description: "Git is really fast. Performing a diff, viewing history, committing and merging changes, obtaining any revision and any form of branching is much faster in Git than SVN."
link_description: ""
link:
competitor_one: true
competitor_two: false
- title: "Size Requirements"
description: "A single repository in Git is typically a number of times smaller than the same repository in SVN."
link_description: ""
link:
competitor_one: true
competitor_two: false