...
 
Commits (2919)
......@@ -3,6 +3,7 @@ source/javascripts/autodevops-animation.js
source/javascripts/mobile-menu.js
source/javascripts/rotate-devops_tools.js
source/javascripts/testimonials.js
source/javascripts/home.js
vendor/
public/
node_modules/
{
"extends": "eslint-config-es5",
"parserOptions": {
"ecmaVersion": 6
},
"globals": {
"$": true,
"jQuery": true,
......
......@@ -11,6 +11,15 @@ variables:
.install: &install
bundle install --jobs 4 --path vendor
# This injects master, merge requests, and tags as default only behavior
# in order to have all jobs run in all cases for these refs, except where
# otherwise intended (for example, to only create review apps for MRs.)
.only-default: &only-default
only:
- master
- merge_requests
- tags
before_script: [*install]
cache:
......@@ -25,6 +34,7 @@ stages:
- deploy
lint 0 2:
<<: *only-default
stage: build
script:
- bundle exec rake lint
......@@ -32,6 +42,7 @@ lint 0 2:
- gitlab-org
lint 1 2:
<<: *only-default
cache: {}
before_script: []
stage: build
......@@ -43,6 +54,7 @@ lint 1 2:
- gitlab-org
crop_pictures:
<<: *only-default
cache: {}
before_script: []
stage: prepare
......@@ -61,10 +73,8 @@ pngbot_commit:
image: registry.gitlab.com/jramsay/pngbot:v0.1.0
before_script: []
cache: {}
except:
- master@gitlab-com/www-gitlab-com
only:
- branches@gitlab-com/www-gitlab-com
- merge_requests@gitlab-com/www-gitlab-com
stage: prepare
script:
- pngbot
......@@ -72,6 +82,7 @@ pngbot_commit:
- gitlab-org
rubocop:
<<: *only-default
stage: build
script:
- bundle exec rubocop
......@@ -83,24 +94,40 @@ rubocop:
stage: build
script:
- bundle exec rspec
artifacts:
expire_in: 7 days
paths:
- tmp/capybara
when: on_failure
tags:
- gitlab-org
rspec_master:
spec 0 2:
<<: *rspec_job
allow_failure: true
only:
refs:
- master
only:
- master
rspec_branch:
spec 0 2:
<<: *rspec_job
allow_failure: false
except:
refs:
- master
only:
- tags
- merge_requests
spec 1 2:
<<: *only-default
cache: {}
before_script: []
stage: build
script:
- yarn install
- yarn run test
tags:
- gitlab-org
enforce_relative_links:
<<: *only-default
stage: build
image: alpine
allow_failure: true
......@@ -124,6 +151,9 @@ check_links:
- coala --no-config --ci --bears InvalidLinkBear --settings follow_redirects=True --files="$(paste -s -d, new_files)"
when: manual
allow_failure: true
only:
- merge_requests
- tags
except:
- master
tags:
......@@ -157,6 +187,9 @@ build_branch:
<<: *build_base
script:
- bundle exec rake build
only:
- merge_requests
- tags
except:
- master
......@@ -170,6 +203,7 @@ build_master:
- master
codequality:
<<: *only-default
stage: build
image: docker:stable
allow_failure: true
......@@ -194,6 +228,7 @@ codequality:
- gl-code-quality-report.json
dependency_scanning:
<<: *only-default
stage: build
image: docker:stable
allow_failure: true
......@@ -237,7 +272,7 @@ review:
url: https://$CI_COMMIT_REF_SLUG.about-src.gitlab.com
on_stop: review_stop
only:
- branches@gitlab-com/www-gitlab-com
- merge_requests@gitlab-com/www-gitlab-com
except:
- master@gitlab-com/www-gitlab-com
tags:
......@@ -259,7 +294,7 @@ review_stop:
name: review/$CI_COMMIT_REF_SLUG
action: stop
only:
- branches@gitlab-com/www-gitlab-com
- merge_requests@gitlab-com/www-gitlab-com
except:
- master@gitlab-com/www-gitlab-com
tags:
......
......@@ -4,7 +4,7 @@
### Target audience
<!--- For whom are we doing this? Include either a persona from https://design.gitlab.com/#/getting-started/personas or define a specific company role. e.a. "Release Manager" or "Security Analyst" -->
<!--- For whom are we doing this? Include either a persona from https://design.gitlab.com/getting-started/personas or define a specific company role. e.a. "Release Manager" or "Security Analyst". Use the persona labels as well https://gitlab.com/groups/gitlab-org/-/labels?utf8=%E2%9C%93&subscribed=&search=persona%3A -->
### Further details
......@@ -12,11 +12,11 @@
### Proposal
<!--- How are we going to solve the problem? -->
<!--- How are we going to solve the problem? Try to include the user journey! -->
### What does success look like, and how can we measure that?
<!--- If no way to measure success, link to an issue that will implement a way to measure this -->
<!--- Define both the success metrics and acceptance criteria. Note thet success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this -->
### Links / references
......
......@@ -2,9 +2,6 @@
### What is this blog post about?
<!-- After you commit a version of your blog post, update the link below to point to the blog post review app -->
**Review App**: https://XXXXX.about.gitlab.com/YYYY/MM/DD/your-blog-post/
<!-- What do you want to blog about? Add your description here -->
### What are the relevant issue numbers?
......@@ -14,12 +11,11 @@ Closes https://gitlab.com/gitlab-com/www-gitlab-com/issues/XXXX
### Checklist
- [ ] Link to issue added, and set to close the when this MR is merged
- [ ] Link to issue added, and set to close when this MR is merged
- [ ] Due date and milestone added for the desired publish date
- [ ] If [time sensitive](https://about.gitlab.com/handbook/marketing/blog/#time-sensitive-posts-official-announcements-company-updates-breaking-changes-and-news)
- [ ] Added ~"priority" label
- [ ] Mentioned `@rebecca` to give her a heads up ASAP
- [ ] Link to the Review App added above
- [ ] Reviewed by team member
- [ ] Reviewed by [content team](https://about.gitlab.com/handbook/marketing/blog/#editorial-reviews)
......
......@@ -56,11 +56,10 @@ The PM leading the post is responsible for adding and checking the following ite
- [ ] Make sure all feature descriptions are positive and cheerful
- [ ] Make sure all features listed in the [direction](https://about.gitlab.com/direction/)
page are included in the post
- [ ] Mention the [release managers](https://about.gitlab.com/community/release-managers/) to remind them
to add the [upgrade barometer](https://about.gitlab.com/handbook/marketing/blog/release-posts#upgrade-barometer) section
- [ ] Mention the [Distribution PM (Joshua)](https://about.gitlab.com/handbook/engineering/dev-backend/distribution/) asking him
if there's any relevant info to be added to the [upgrade warning](https://about.gitlab.com/handbook/marketing/blog/release-posts#upgrade-warning) section. If not, delete the `upgrade` block in the relese post data file
- [ ] Mention managers to remind them to add their team performance improvements: @gitlab-com/backend-managers and @gitlab-org/frontend/frontend-managers
- [ ] Make sure Upgrade barometer is in
- [ ] Check with the [Messaging Lead](https://about.gitlab.com/handbook/marketing/blog/release-posts/#messaging-lead) on what the top features should be.
- [ ] Check with the [Messaging Lead](https://about.gitlab.com/handbook/marketing/blog/release-posts/#messaging-lead) on what the top features should be.
- [ ] Check if deprecations are included
- [ ] Alert people one working day before each due date (post a comment to #release-post Slack channel)
- [ ] Make sure all images (png, jpg, and gifs) are smaller than 300 KB each
......@@ -187,7 +186,7 @@ The [structural review](https://about.gitlab.com/handbook/marketing/blog/release
- [ ] Tweet social sharing text (for Twitter, FB, and LinkedIn)
- [ ] Assign the MR to the next reviewer (marketing)
- [ ] Marketing review (PMMs - [messaging lead](https://about.gitlab.com/handbook/marketing/blog/release-posts/#messaging-lead)): `@mention`
- [ ] Write the introduction (**by the 6th day before the 22nd**)
- [ ] Write the introduction (**by the 6th working day before the 22nd**)
- [ ] Check/copyedit feature blocks
- [ ] Check/copyedit `features.yml`
- [ ] Check/copyedit homepage blurb
......
......@@ -13,6 +13,12 @@
- source: 'data/gitlab_com.yml'
public: 'pricing#gitlab-com'
- source: 'data/depts.yml'
public: 'handbook/product/categories/'
- source: 'data/stages.yml'
public: 'handbook/product/categories/'
- source: 'data/categories.yml'
public: 'handbook/product/categories/'
......
......@@ -38,6 +38,8 @@ linters:
enabled: false
SelectorDepth:
max_depth: 4
SelectorFormat:
ignored_names: vs__actions
SingleLinePerProperty:
allow_single_line_rule_sets: false
StringQuotes:
......
---
layout: blank
title: Redirecting
canonical_path: "/2018/10/24/setting-up-gitlab-ci-for-android-projects/"
---
- path = current_page.data.canonical_path
%p{ :style => "text-align: center; margin-top: 30px;" }
Redirecting to
%a{ href: "#{path}" } https://about.gitlab.com#{path}
:javascript
window.location.replace("#{path}")
\ No newline at end of file
......@@ -43,5 +43,6 @@ group :development, :test do
gem 'rspec', '~> 3.5', require: false
gem 'rubocop', '~> 0.59.0', require: false
gem 'capybara'
gem 'capybara-screenshot'
gem 'selenium-webdriver'
end
......@@ -21,6 +21,9 @@ GEM
rack-test (>= 0.6.3)
regexp_parser (~> 1.2)
xpath (~> 3.2)
capybara-screenshot (1.0.22)
capybara (>= 1.0, < 4)
launchy
childprocess (0.9.0)
ffi (~> 1.0, >= 1.0.11)
coffee-script (2.4.1)
......@@ -85,6 +88,8 @@ GEM
i18n_data (0.8.0)
jaro_winkler (1.5.1)
kramdown (1.17.0)
launchy (2.4.3)
addressable (~> 2.3)
libv8 (6.7.288.46.1)
listen (3.0.8)
rb-fsevent (~> 0.9, >= 0.9.4)
......@@ -236,6 +241,7 @@ PLATFORMS
DEPENDENCIES
builder (~> 3.0)
capybara
capybara-screenshot
countries
docopt
faraday (>= 0.15.0)
......
......@@ -178,6 +178,32 @@ you save the new version of the file (otherwise, just restart the container)
> **Note**: Subsequent runs will just require `docker start middleman`.
## Building a single file
If you only want Middleman to build a single file, you can do that via the `--glob` parameter.
Here are a few things to keep in mind:
* The glob parameter must match the **destination** file.
* The `--no-clean` option should be included or Middleman will wipe out
files that do not match the glob parameter.
For example, here's how to rebuild the Contribute page. Note how
`source/company/culture/index.html.md.erb` is mapped to
`company/culture/contribute/index.html`:
```sh
bundle exec middleman build --glob={company/culture/contribute/index.html} --no-clean
```
For blog posts,
`source/posts/2017-05-23-attributes-of-successful-development-teams.html.md`
maps to `2017/05/23/attributes-of-successful-development-teams/index.html`:
```sh
bundle exec middleman build --glob={2017/05/23/attributes-of-successful-development-teams/index.html} --no-clean
```
## 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:
......
......@@ -78,7 +78,7 @@ configure :build do
product_vision_content = direction_all_content = wishlist = nil
# Create threads to fetch content for shared pages
threads = []
teams = %w[manage plan create verify package release configure monitor secure gitaly gitter geo]
teams = %w[manage plan create verify package release configure monitor secure defend gitaly gitter geo]
threads << Thread.new { wishlist = generate_wishlist } # wishlist, shared by most pages
threads << Thread.new { product_vision_content = generate_product_vision } # /direction/product-vision/
threads << Thread.new { direction_all_content = generate_direction(teams) } # /direction/
......@@ -198,6 +198,7 @@ ignore '/direction/release/template.html'
ignore '/direction/configure/template.html'
ignore '/direction/monitor/template.html'
ignore '/direction/secure/template.html'
ignore '/direction/defend/template.html'
ignore '/direction/distribution/template.html'
ignore '/includes/*'
ignore '/releases/template.html'
......
button_link: /product/
button_text: Learn more
content: |
Heres where we put the anouncement of whatever we want. What's exciting is that we can include [links like this](/product/), since it's markdown.
button_link: /2019/01/10/gitlab-2018-year-in-review/
content: "2018: GitLab's year in review - Read more in our blog post."
......@@ -16,6 +16,13 @@
links:
- url: https://azuremarketplace.microsoft.com/en-us/marketplace/apps/gitlab.gitlab-ce?utm_campaign=social&utm_content=190745898c2e43f08560396ba1a0208d&utm_medium=e&utm_source=mkt-gitlab-cegitlab-ce&tab=PlansAndPrice
title: Find us on the Azure Marketplace
- title: GitLab on Jelastic PaaS
content: A private GitLab instance automatically installed and scaled on Jelastic PaaS. The instance is secured with built-in SSL that can be upgraded to Let's Encrypt or higher level certificates for custom domains. Runners are automatically scaled vertically, horizontal scaling is available in a click or based on triggers.
links:
- url: https://github.com/jelastic-jps/gitlab
title: Install GitLab on Jelastic PaaS
- url: https://jelastic.com/blog/private-gitlab-server-auto-installation
title: Automatic installation guide
- title: Native Apps
id: native-apps
applications:
......@@ -158,6 +165,13 @@
title: Repository on GitHub
- url: https://www.npmjs.com/package/gitlab-time-tracker
title: Package on NPM
- title: 'Release It!'
content: 'Automate the tedious tasks of software releases. Happily release and publish your Git repositories, npm packages, GitHub & GitLab releases, changelogs, and much more!'
links:
- url: https://github.com/webpro/release-it
title: Repository on GitHub
- url: https://www.npmjs.com/package/release-it
title: Package on npm
- title: API Clients
id: api-clients
applications:
......
title: Axway
cover_image: '/images/blogimages/axway-case-study-image.png'
cover_title: |
Axway realizes a 26x faster DevOps cycle by switching from Subversion to GitLab
Axway realizes a 26x faster release cycle by switching from Subversion to GitLab
cover_description: |
To help customers better leverage their data, Axway stays ahead of the market by releasing new code faster, using GitLab for source code management
twitter_image: '/images/blogimages/axway-case-study-image.png'
......
......@@ -36,7 +36,10 @@ customer_study_content:
to fostering the growth and evolution of cloud native systems through the
stewardship of open source projects including ensuring the technology is
available, accessible, integrated, and reliable. The CNCF currently hosts a
dozen open source projects such as Kubernetes, Prometheus, and CoreDNS.
dozen open source projects such as Kubernetes, Prometheus, and CoreDNS. The [CNCF dashboard](https://cncf.ci)
displays the daily status on both the latest release and the latest development version (i.e., head).
The newest release includes, for the first time, the Linux Foundation Open Network Automation
Platform (ONAP) project.
- |
The CNCF Continuous Integration (CI) Working Group, lead by Camille Fournier,
......
title: European-Space-Agency
cover_image: '/images/blogimages/ESA_case_study_image.jpg'
cover_title: |
Connecting the cosmos with Earth - How the European Space Agency uses GitLab to focus on space missions
cover_description: |
ESA is improving the way it approaches mission operations software creation. GitLab is allowing teams to cross borders, increase cooperation and reshape working culture.
twitter_image: '/images/blogimages/ESA_case_study_image.jpg'
customer_logo: 'images/case_study_logos/esa_logo_color2.svg'
customer_logo_css_class: brand-logo-tall
customer_industry: Technology
customer_location: France, Netherlands, Italy, Germany, Spain, United Kingdom, Belgium
customer_employees: 5,000
customer_overview: |
The European Space Agency (ESA) provides a European-wide Space Programme. ESA's programmes are designed to find out more about Earth, its immediate space environment, our Solar System and the Universe, as well as to develop satellite-based technologies and services, and to promote European industries. ESA also works closely with space organizations outside Europe.
customer_challenge: |
ESA shapes the development of Europe’s space capability and ensures that the investment in space continues to deliver results and benefits to the citizens of Europe and the world. The organisation looks to the stars, but faces the challenges of geographical separation, long-term software redundancy requirements, and many different software customer needs.
key_benefits:
- |
Code deploy speed is now in a matter of minutes when it took weeks just a few years ago
- |
The toolchain has been simplified with the usage of GitLab CI
- |
A culture of collaboration has bloomed and is increasing around the organization
- |
Synergy exploitation is increased
customer_stats:
- stat: ~15%
label: of ESA employees are actively using GitLab
- stat: "140"
label: groups, over 1500 projects
- stat: 60k+
label: jobs the first year using GitLab CI
customer_study_content:
- title: the customer
subtitle: Leading the charge as Europe’s gateway to space- The European Space Agency enables European space research and technology and space applications.
content:
- |
The European Space Agency (ESA) is responsible for coordinating the financial and intellectual resources of its 22 member states
to ensure that investment in space continues to deliver benefits to the citizens of Europe and the world. The organization focuses
on a wide variety of missions focused on space exploration and continued research. Some of their recent missions include
sending orbiters to Mercury and studying hypervelocity stars in the Milky Way.
- title: the challenge
subtitle: Without a central version control system in place, opportunities for collaboration, synergies and multiple exploitations of effort were less visible.
content:
- |
The European Space Agency has always carefully deployed new technologies. Validation and security have been at the fore,
and there is less drive to invoke newer practices or technologies for their own sake unless they clearly bring added
benefits for ESA’s core business. This sometimes resulted in using older, trusted tools to share code, at the expense of timeliness.
- |
In 2015 different teams within ESA were using a heterogeneous approach to control systems, some examples were Subversion or CVS.
The emergence of Git, and its subsequent adoption by the ESA IT Department was a harmonious intersection of user needs and secure
technology. GitLab was validated and adopted for the European Space Agency as a code repository platform in 2016. Usage was initially
limited to a hand-picked group of first-wave users, but demand quickly escalated.
- |
In just two years, more than 140 groups adopted GitLab as their software versioning tool. Across ESA, more than 1500 software projects
have been created. These range from mission control systems, onboard software for spacecraft, image processing and monitoring tools for
Labs. The ESA IT Department also uses GitLab to host their code tools and configurations infrastructure.
- blockquote: “I think our use case is quite interesting at ESA. Our team develops software, and we are also flying spacecraft. So developing software is in addition to our main activity. There are a lot of tools that we
require to support us in our actual job. In that sense, we want to minimize the time that we spend to build these tools. Furthermore,
GitLab has also shown that it is very effective in sharing our tools with other teams.”
attribution: Bruno Sousa
attribution_title: Spacecraft Operations Manager at ESA
- title: the solution
subtitle: Creating a culture where collaboration is contagious because sharing is so easy
content:
- |
GitLab was introduced to the ESA population in 2016. Teams across Europe embraced the tool at all ESA Establishments, and sites.
They can now collaborate and share code and insights both within their teams and with other teams. The process is faster, in real time,
and produces reliable, stable results. Users can use more of their time to focus on their mission-critical tasks and spend less time keeping
tools running.
- |
The adoption rate was high. Within one week 40 projects were running in GitLab. “Right now, we have 15% of our user population using GitLab”,
a representative from the ESA IT Department GitLab project commented.
- |
For ESA, this represents a departure from the previous software development culture. In the past, it was assumed that there were fewer
synergies to be exploited. Version control systems were individualised, or teams had not implemented them. As the technology now matches
ESA’s needs, GitLab lets ESA approach more standardisation and efficiency.
- blockquote: “To see people collaborating is contagious. People are saying, ‘Hey, I want to have a project like that!’ or ‘I want to participate.’ These kinds of things can happen because everybody has access,”
attribution: Redouane Boumghar
attribution_title: Research Fellow at ESA
- content:
- |
Initially, ESA implemented GitLab to exploit the version control capabilities within the tool. However, the user community has also benefitted
from the Continuous Integration (CI/CD) capabilities within GitLab. ESA began exploiting CI/CD capabilities in November 2017, and there are
currently 60,000 jobs in GitLab. Feedback to the ESA IT Department from the user community has conveyed the user’s satisfaction with this development.
One user reported “We initially started using version control, but we discovered that we could use CI on our project. We tried it out and were immensely
impressed with how well it all worked together”.
- |
ESA’s diversity of teams and tasks provides unique challenges. Bruno Sousa explains why his tasks require CI/CD saying, “For our use case, in particular,
the CI/CD capabilities are extremely important. In my role I simultaneously responsible for flying a spacecraft and developing a tool for us, and also
potentially for other missions. I don’t have the time to deploy the software over and over again, so GitLab is very helpful in facilitating the whole
process. It makes everything easier so that I can focus on my core task of flying the spacecraft.”
- title: the results
subtitle: Increasing excitement and speed around code deployments with innovation as a result
content:
- |
GitLab has provided a software development turnaround speed that ESA had not previously been able to achieve. The code is now continuously deployed
in a matter of minutes, when previously it may have taken weeks.
- |
GitLab is able to address challenges along many stages of the software development pipeline. In the past different ESA teams were using a variety of
CI/CD engines. Now they are being replaced with GitLab CI because GitLab is more user-friendly. As more users move to GitLab, ESA’s obligation to
maintain other tools is removed. GitLab CI is then integrated into more version control systems.
- |
The automation in GitLab also saves ESA IT Department resources. With operation and backup fully automated, IT Specialists can focus on monitoring the
tool and importantly, addressing more IT challenges for the European Space Agency.
title: Goldman Sachs
cover_image: '/images/blogimages/Goldman_Sachs_case_study.jpg'
cover_title: |
Goldman Sachs improves from two daily builds to over a thousand per day
cover_description: |
Engineering teams removed toolchain complexity and accelerated DevOps adoption through GitLab's automation
twitter_image: '/images/blogimages/Goldman_Sachs_case_study.jpg'
customer_logo: 'images/case_study_logos/GSsignature_Blue.png'
customer_logo_css_class: brand-logo-tall
customer_industry: Financial Services
customer_location: United States
customer_employees: 35,000+
customer_overview: |
Goldman Sachs Technology Division and global strategists groups are at the critical center of their business. The dynamic environment at Goldman Sachs requires innovative strategic thinking and immediate, real-time solutions.
customer_challenge: |
Goldman Sachs was looking to increase developer efficiency and software quality, achieve faster development cycles, and enable concurrent development activities.
customer_solution: GitLab Premium
key_benefits:
- |
Supporting an exponentially larger number of builds than previously thought possible
- |
Simplified Workflow - GitLab’s single application allows developers to manage all efforts in one UI.
- |
Simplified administration using one centralized instance for all repositories
customer_stats:
- stat: 1000+
label: CI feature branch builds a day by some teams
- stat: 52k
label: test cases across 11k test classes
- stat: 1500+
label: adopters in the first two weeks
customer_study_content:
- title: the customer
subtitle: Goldman Sachs solves clients engineering challenges
content:
- |
Goldman Sachs is achieving what was previously assumed to be impossible. With the help of GitLab,
the engineering team is now self-serving thousands of daily builds and dozens of teams are moving
to production on a daily basis. Goldman Sachs empowered users with a strategic development tool and
removed barriers around tool confusion and communication to speed up the delivery cycle.
- |
The Goldman Sachs engineering group is part of the technology division and global strategy groups which are the
critical center of the financial service provider’s business. They solve the most challenging and pressing
engineering problems for Goldman Sachs clients. The group builds massively scalable software and systems, architects
low latency infrastructure solutions, proactively guards against cyber threats, and leverages machine learning
alongside financial engineering to continuously turn data into action.
- |
Goldman Sachs dynamic environment requires innovative strategic thinking and immediate, real solutions.
The group was looking to increase developer efficiency and software quality through faster development cycles
and decreasing the time spent from feature design to production rollout. They wanted to accomplish all of this
while enabling concurrent development activities.
- title: the challenge
subtitle: Increasing build speed by demolishing toolchain complexity
content:
- |
The firm had built its own toolchain but was looking for a solution to increase concurrent development. They wanted a modern
toolset for managing code that developers coming into the firm would likely already be familiar with; this led to an evaluation
of GitLab and other git-based vendor products.
- |
From their discovery process, they decided GitLab had the best CI/CD infrastructure to meet their needs. Initial users reported
that it was easy to use and offered a complete end-to-end platform for software development allowing them to replace their current
toolchain and increase speed and coordination in the process.
- title: the solution
subtitle: GitLab increases Goldman Sachs build velocity
content:
- |
GitLab is used as a complete ecosystem for development, source code control and reviews, builds,
testing, QA, and production deployments. All the new strategic pieces of Goldman Sachs’ software
development platforms are tied into GitLab.
- |
GitLab is helping the business-line engineering teams move faster to develop and improve their software
and deliver for clients. One of the firm’s most important projects has moved from a release cycle of once
every 1-2 weeks to once every few minutes because of GitLab.
- blockquote: GitLab has allowed us to dramatically increase the velocity of development in our
Engineering Division. We believe GitLab’s dedication to helping enterprises rapidly and effectively
bring software to market will help other companies achieve the same sort of efficiencies we have seen inside Goldman Sachs.
We now see some teams running and merging 1000+ CI feature branch builds a day!
attribution: Andrew Knight
attribution_title: Managing Director at Goldman Sachs
- content:
- |
GitLab provided them a single application to roll out DevOps to the thousands of users at the bank. The ease of
people only having to learn one application accelerated their adoption time. They were concerned that multiple tools,
like most companies use, would be confusing, difficult to maintain and would deter adoption.
- title: the results
subtitle: Dozens of teams pushing to production in less than 24 hours
content:
- |
The engineering group at Goldman Sachs is achieving this increased efficiency and speed by collaborating and connecting on a new level.
They are seeing dozens of teams pushing to production in less than 24 hours. By tying together all the different parts of the development
lifecycle into one consistent ecosystem, GitLab has helped developers work more effectively. All the different parts of what they need to
do can be brought together under a single umbrella to be more efficient.
- |
The team is also using GitLab as a means of moving teams to more strategic infrastructure which supports containers, as well as other
strategic initiatives that are only offered on the new platform. This really helps make sure that the group is focusing efforts to use
the latest technologies in the right places, and not just retrofit to the legacy infrastructure. GitLab also works well with Kubernetes
out of the box which simplified their process.
- blockquote: We’re bringing into the firm a platform that our engineers actually want to use – which helps drive adoption across multiple teams
and increase productivity without having to ‘force’ anyone to adopt it. This is really helping to create an ecosystem where our end users are
actively helping us drive towards our strategic goals - more releases, better controls, better software.
attribution: George Grant
attribution_title: VP technology fellow, Goldman Sachs
This diff is collapsed.
......@@ -36,6 +36,12 @@
- country: Spain
employee_factor: 1
entity: Safeguard - Spain
- country: France
employee_factor: 1
entity: Safeguard - France
- country: Brazil
employee_factor: 1
entity: Safeguard - Brazil
- country: '*'
contractor_factor: 1.17
entity: GitLab BV
# Country factor data that is used by the compensation calculator
- country: Belgium
country_factor: 1
- country: China
country_factor: 0.66
- country: India
country_factor: 0.75
- country: Netherlands
country_factor: 0.85
- country: United Kingdom
country_factor: 0.85
- country: Germany
country_factor: 1
- country: United States
country_factor: 1
- country: Israel