399 lines
42 KiB
BibTeX
399 lines
42 KiB
BibTeX
@misc{2025StackOverflow,
|
|
title = {2025 {{Stack Overflow Developer Survey}}},
|
|
urldate = {2026-04-18},
|
|
abstract = {The 2025 Developer Survey is the definitive report on the state of software development. In its fifteenth year, Stack Overflow received over 49,000+ responses from 177 countries across 62 questions focused on 314 different technologies, including new focus on AI agent tools, LLMs and community platforms. This annual Developer Survey provides a crucial snapshot into the needs of the global developer community, focusing on the tools and technologies they use or want to learn more about.},
|
|
langid = {english},
|
|
file = {C:\Users\Roman\Zotero\storage\29SDLBQ5\2025.html}
|
|
}
|
|
|
|
@article{arefeen_continuous_2019,
|
|
title = {Continuous {{Integration Using Gitlab}}},
|
|
author = {Arefeen, Mohammed Shamsul and Schiller, Michael},
|
|
year = 2019,
|
|
month = sep,
|
|
journal = {Undergraduate Research in Natural and Clinical Science and Technology Journal},
|
|
volume = {3},
|
|
pages = {1--6},
|
|
issn = {2561-5637},
|
|
doi = {10.26685/urncst.152},
|
|
urldate = {2026-04-15},
|
|
abstract = {The method of Continuous Integration (CI) enables developers to use fast-paced development environments, such as Agile, without the quality of code being compromised. The use of stable repositories on which developers frequently make small changes, running tests with each modification, results in code that is highly tested and readily deployable. GitLab, like other tools of its kind, offers CI features along with code versioning, and several team organizational features that correctly map with Agile artifacts. Before discussing GitLab, this report contains a literature review explaining existing CI practices, and it identifies fundamental aspects that are necessary to achieving the industry standards of CI. This report also evaluates GitLab's effectiveness in maintaining CI standards using an available open-source project (OpenMCT), while also offering insight on the implications of the gathered findings. The paper concludes with possible directions of future inquiry, and also provides guidance on how one might expand on the work initiated by the team.},
|
|
langid = {english},
|
|
keywords = {agile,continuous integration,GitLab,software testing}
|
|
}
|
|
|
|
@book{bass_devops_2015,
|
|
title = {{{DevOps}}: A Software Architect's Perspective},
|
|
shorttitle = {{{DevOps}}},
|
|
author = {Bass, Len and Weber, Ingo and Zhu, Liming},
|
|
year = 2015,
|
|
series = {{{SEI}} Series in Software Engineering},
|
|
publisher = {Addison-Wesley Professional},
|
|
address = {Upper Saddle River, NJ},
|
|
isbn = {978-0-13-404984-7}
|
|
}
|
|
|
|
@article{choudhuryGitLabWorkWhere2020,
|
|
title = {{{GitLab}}: {{Work}} Where You Want, When You Want},
|
|
shorttitle = {{{GitLab}}},
|
|
author = {Choudhury, Prithwiraj and Crowston, Kevin and Dahlander, Linus and Minervini, Marco S. and Raghuram, Sumita},
|
|
year = 2020,
|
|
month = nov,
|
|
journal = {Journal of Organization Design},
|
|
volume = {9},
|
|
number = {1},
|
|
pages = {23},
|
|
issn = {2245-408X},
|
|
doi = {10.1186/s41469-020-00087-8},
|
|
urldate = {2026-04-15},
|
|
abstract = {GitLab is a software company that works ``all remote'' at the scale of more than 1000 employees located in more than 60 countries. GitLab has no physical office and its employees can work from anywhere they choose. Any step of the organizational life of a GitLab employee (e.g., hiring, onboarding and firing) is performed remotely, except for a yearly companywide gathering. GitLab strongly relies on asynchronous coordination, allowing employees to work anytime they want. After highlighting some of the main practices implemented by GitLab to effectively work all remotely and asynchronously, I asked renowned organizational scientists their thoughts on this interesting case and to question the generalizability of the all remote asynchronous model. Understanding whether and under what conditions this model can succeed can be of guidance for organizational designers that are now considering different remote models in response of the COVID-19 shock and its aftermath.},
|
|
langid = {english},
|
|
keywords = {All remote,COVID-19,New forms of organizing,Organizational design,Remote work,Virtual organizations},
|
|
file = {C:\Users\Roman\Zotero\storage\HUKLD34S\Choudhury et al. - 2020 - GitLab work where you want, when you want.pdf}
|
|
}
|
|
|
|
@book{cowell_automating_2023,
|
|
title = {Automating {{DevOps}} with {{GitLab CI}}/{{CD Pipelines}}: {{Build}} Efficient {{CI}}/{{CD}} Pipelines to Verify, Secure, and Deploy Your Code Using Real-Life Examples},
|
|
shorttitle = {Automating {{DevOps}} with {{GitLab CI}}/{{CD}} Pipelines},
|
|
author = {Cowell, Christopher and Lotz, Nicholas and Timberlake, Chris},
|
|
year = 2023,
|
|
pages = {348},
|
|
publisher = {Packt Publishing},
|
|
address = {Birmingham},
|
|
isbn = {978-1-80323-300-0}
|
|
}
|
|
|
|
@misc{degeler_gitlab_2014,
|
|
title = {{{GitLab}} Is Building a Business with 0.1\% of Paying Customers},
|
|
author = {Degeler, Andrii},
|
|
year = 2014,
|
|
month = jun,
|
|
urldate = {2026-04-16},
|
|
abstract = {Long-distance relationships are never easy, but it seems to be less so for the relationships between co-founders of tech companies. See GitLab, for example.},
|
|
langid = {english}
|
|
}
|
|
|
|
@book{duvall_continuous_2007,
|
|
title = {Continuous Integration: {{Improving}} Software Quality and Reducing Risk},
|
|
shorttitle = {Continuous Integration},
|
|
author = {Duvall, Paul M. and Matyas, Steve and Glover, Andrew},
|
|
year = 2007,
|
|
series = {Addison-Wesley Signature Series (Fowler)},
|
|
pages = {336},
|
|
publisher = {Addison-Wesley},
|
|
address = {Upper Saddle River, NJ},
|
|
isbn = {978-0-321-33638-5}
|
|
}
|
|
|
|
@inproceedings{fairbanksAnalyzingEffectsCI2023,
|
|
title = {Analyzing the {{Effects}} of {{CI}}/{{CD}} on {{Open Source Repositories}} in {{GitHub}} and {{GitLab}}},
|
|
booktitle = {2023 {{IEEE}}/{{ACIS}} 21st {{International Conference}} on {{Software Engineering Research}}, {{Management}} and {{Applications}} ({{SERA}})},
|
|
author = {Fairbanks, Jeffrey and Tharigonda, Akshharaa and Eisty, Nasir U.},
|
|
year = 2023,
|
|
month = may,
|
|
pages = {176--181},
|
|
issn = {2770-8209},
|
|
doi = {10.1109/SERA57763.2023.10197778},
|
|
urldate = {2026-04-17},
|
|
abstract = {Numerous articles emphasize the benefits of implementing Continuous Integration and Delivery (CI/CD) pipelines in software development. These pipelines are expected to improve a project's reputation and decrease the number of commits and issues in the repository. Although CI/CD adoption may be slow initially, it is believed to accelerate service delivery and deployment in the long run. This study aims to investigate the impact of CI/CD on commit velocity and issue counts in two open-source repositories, GitLab and GitHub. By analyzing more than 12,000 repositories and recording every commit and issue, it was discovered that CI/CD enhances commit velocity by 141.19\% but also increases the number of issues by 321.21\%.},
|
|
keywords = {CI/CD,Codes,Mining Repositories,Open-Source Software,Pipelines,Recording,Software,Software development management,Software engineering,Software Engineering},
|
|
file = {C:\Users\Roman\Zotero\storage\ZVGXIL24\Fairbanks et al. - 2023 - Analyzing the Effects of CICD on Open Source Repositories in GitHub and GitLab.pdf}
|
|
}
|
|
|
|
@book{forsgren_accelerate_2018,
|
|
title = {Accelerate: {{The}} Science of Lean Software and {{DevOps}}. {{Building}} and Scaling High Performing Technology Organizations},
|
|
shorttitle = {Accelerate},
|
|
author = {Forsgren, Nicole and Humble, Jez and Kim, Gene},
|
|
year = 2018,
|
|
publisher = {IT Revolution Press},
|
|
address = {Portland, OR},
|
|
isbn = {978-1-942788-33-1}
|
|
}
|
|
|
|
@misc{fowler_continuous_2006,
|
|
title = {Continuous Integration},
|
|
author = {Fowler, Martin},
|
|
year = 2006,
|
|
month = may,
|
|
urldate = {2026-05-04},
|
|
howpublished = {martinfowler.com}
|
|
}
|
|
|
|
@misc{GitHubcomHelpDocumentation,
|
|
title = {{{GitHub}}.Com {{Help Documentation}}},
|
|
journal = {GitHub Docs},
|
|
urldate = {2026-06-07},
|
|
abstract = {Get started, troubleshoot, and make the most of GitHub. Documentation for new users, developers, administrators, and all of GitHub's products.},
|
|
howpublished = {https://docs-internal.github.com/en},
|
|
langid = {english},
|
|
file = {C:\Users\Roman\Zotero\storage\CBUZVQLS\en.html}
|
|
}
|
|
|
|
@misc{GitHubInnovationGraph,
|
|
title = {{{GitHub Innovation Graph}}},
|
|
urldate = {2026-05-19},
|
|
abstract = {Explore a universe of data about how the world is building software together on GitHub.},
|
|
langid = {english},
|
|
file = {C:\Users\Roman\Zotero\storage\EBU9LPUD\innovationgraph.github.com.html}
|
|
}
|
|
|
|
@misc{gitlab_about,
|
|
title = {About {{Gitlab}}},
|
|
author = {{Gitlab}},
|
|
urldate = {2026-04-17},
|
|
abstract = {Your intelligent orchestration platform for DevSecOps},
|
|
langid = {american},
|
|
file = {C:\Users\Roman\Zotero\storage\KG655MR3\about.gitlab.com.html}
|
|
}
|
|
|
|
@misc{gitlab_gitlab_nodate,
|
|
title = {{{GitLab Docs}}},
|
|
author = {{Gitlab}},
|
|
urldate = {2026-04-16}
|
|
}
|
|
|
|
@misc{gitlab_s1_2021,
|
|
title = {Form {{S-1}} Registration Statement},
|
|
author = {{GitLab Inc.}},
|
|
year = 2021,
|
|
month = sep,
|
|
urldate = {2026-05-04},
|
|
howpublished = {U.S. Securities and Exchange Commission, EDGAR Filing System}
|
|
}
|
|
|
|
@misc{GitLab16522166,
|
|
title = {{{GitLab}} 1652216-6},
|
|
urldate = {2026-06-07},
|
|
howpublished = {https://certificate-directory-v2-9z7a0xjllzon1iz8.s3.amazonaws.com/14921/GitLab\%201652216-6.pdf?X-Amz-Security-Token=IQoJb3JpZ2luX2VjENr\%2F\%2F\%2F\%2F\%2F\%2F\%2F\%2F\%2F\%2FwEaCXVzLWVhc3QtMSJHMEUCIAzg2qbnPWjF8ANiP85mhwOssqnFk9NRY4FZSgSwUBFQAiEA0y0GOUV6dDKowIVpqPJWBeGMdqtJlOcSbeOa0DyiAdcqhgQIo\%2F\%2F\%2F\%2F\%2F\%2F\%2F\%2F\%2F\%2F\%2FARAAGgw4MzU4NTczNjE3NDAiDKUVvC\%2FRBunDtasKzSraA7HJRbCduWk09yPpaUUglYHlfaN0\%2B0nGdnBT6q2OcFf1C7d\%2F5A8Z7Ogtcnyu3Hs4UyxFq8tkBj7mt52NlqnHGXG2SX31PNa7kN9tYNbpS\%2BM\%2Fpf2yGGC3yEeNfJYZn4ZL9q\%2FDXMpetx\%2B8cQt3Umt3VSvr\%2Fb\%2FXbYZokMQS\%2BJ7\%2F1HN39\%2BHJaYQP6RqSVpHQvFnp\%2F17od3vQaJRGteA7\%2Fao\%2FnYH2eeqNpvdYSDpo3mValWYrQdT4xaPFFcIAQB3CEiyo4SgtxyXLhyJwtXLhXpb4Y7VsdT4y72IC5hD0Y57fE7HiPSJYiefi4keRQpH9Ia\%2Bp\%2BhbvwdnCHhpmiQEinu4ZsrC5s0ebGV\%2FszfWQIYhr6BPt8QgoUhjwvvZAdqSoykwoTdUQ2UAoN0wgfDH2dmaYJCKB6I7FmSOpW2\%2Fbl5iLe35pAmTbB9aWMIUHoK3Ld1U\%2FmARNxUWSC1fQR\%2Bp3s4QDbBf7mk2BlyhdtVPBWlyNLGHX\%2BSLDt9ZkqVpYCNeh2uNxam0weP\%2F5gDIYP1yplLkvCIY2j6NZMfV\%2FRAMCDU\%2Fb0hUX6uBA2nwcuo7ZnuM1YDimdyPDG9hXexUygAJ8pJgEJRp00n6nPPL\%2F9uAinVoO4bqWy7\%2Fk87oMasJ1hDD\%2F3ZbRBjqlARwki9a6twsl5UVDOnOk\%2BwV3FkfNcYOtHRRzhQSHXeUzg8bFUGaAdTQz6a08ugI\%2FJPHz1MCIlFHSrMijL\%2BTacILY8TVeEaA9DdiJXGks\%2FjC\%2B6KArZIjEHPDel80HrGFwi99p\%2Fssdba1eWw9XrVEAyJKvkCX2PGI663\%2BmpmfS1vgHH12l5QI9LJGSsvJdYA3AB15FycyJSx5jVAywgWK7EOQEBWhH2g\%3D\%3D\&X-Amz-Algorithm=AWS4-HMAC-SHA256\&X-Amz-Date=20260607T195034Z\&X-Amz-SignedHeaders=host\&X-Amz-Credential=ASIA4FHH3FNGHFS3J34L\%2F20260607\%2Fus-east-1\%2Fs3\%2Faws4\_request\&X-Amz-Expires=900\&X-Amz-Signature=fab520a96bdce151deb3dc36a7bde5bd42c32105ff15fe58dee07bc5f542679d},
|
|
file = {C:\Users\Roman\Zotero\storage\XSV4JT3D\GitLab 1652216-6.pdf}
|
|
}
|
|
|
|
@misc{GitLabcomDatabaseIncident,
|
|
title = {{{GitLab}}.Com Database Incident},
|
|
urldate = {2026-04-17},
|
|
abstract = {Yesterday we had a serious incident with one of our databases. We lost six hours of database data (issues, merge requests, users, comments, snippets, etc.) for GitLab.com.},
|
|
langid = {american},
|
|
file = {C:\Users\Roman\Zotero\storage\PIAEFUHX\gitlab-dot-com-database-incident.html}
|
|
}
|
|
|
|
@inproceedings{golzadeh_rise_2022,
|
|
title = {On the Rise and Fall of {{CI}} Services in {{GitHub}}},
|
|
booktitle = {Proceedings of the 2022 {{IEEE}} International Conference on Software Analysis, Evolution and Reengineering ({{SANER}} 2022)},
|
|
author = {Golzadeh, Mehdi and Decan, Alexandre and Mens, Tom},
|
|
year = 2022,
|
|
pages = {662--672},
|
|
address = {Honolulu, HI},
|
|
doi = {10.1109/SANER53432.2022.00084}
|
|
}
|
|
|
|
@inproceedings{hilton_usage_2016,
|
|
title = {Usage, Costs, and Benefits of Continuous Integration in Open-Source Projects},
|
|
booktitle = {Proceedings of the 31st {{IEEE}}/{{ACM}} International Conference on Automated Software Engineering ({{ASE}} 2016)},
|
|
author = {Hilton, Michael and Tunnell, Timothy and Huang, Kai and Marinov, Darko and Dig, Danny},
|
|
year = 2016,
|
|
pages = {426--437},
|
|
address = {Singapore},
|
|
doi = {10.1145/2970276.2970358}
|
|
}
|
|
|
|
@misc{HowGitLabCan,
|
|
title = {How {{GitLab}} Can Support Your {{ISO}} 27001 Compliance Journey},
|
|
journal = {GitLab},
|
|
urldate = {2026-06-07},
|
|
abstract = {As a strategic partner, GitLab's software security features can help support your ISO 27001 compliance.},
|
|
howpublished = {https://about.gitlab.com/blog/how-gitlab-can-support-your-iso-compliance-journey/},
|
|
langid = {american},
|
|
file = {C:\Users\Roman\Zotero\storage\ITFPQ5DP\how-gitlab-can-support-your-iso-compliance-journey.html}
|
|
}
|
|
|
|
@book{humble_continuous_2010,
|
|
title = {Continuous Delivery: {{Reliable}} Software Releases through Build, Test, and Deployment Automation},
|
|
shorttitle = {Continuous Delivery},
|
|
author = {Humble, Jez and Farley, David},
|
|
year = 2010,
|
|
series = {Addison-Wesley Signature Series (Fowler)},
|
|
pages = {512},
|
|
publisher = {Addison-Wesley Professional},
|
|
address = {Boston, MA},
|
|
isbn = {978-0-321-60191-9}
|
|
}
|
|
|
|
@misc{ISOIEC27017,
|
|
title = {{{ISO}}/{{IEC}} 27017:2015},
|
|
shorttitle = {{{ISO}}/{{IEC}} 27017},
|
|
journal = {ISO},
|
|
urldate = {2026-06-07},
|
|
abstract = {Information technology --- Security techniques --- Code of practice for information security controls based on ISO/IEC 27002 for cloud services},
|
|
howpublished = {https://www.iso.org/standard/43757.html},
|
|
langid = {english},
|
|
file = {C:\Users\Roman\Zotero\storage\GHQLR68Z\43757.html}
|
|
}
|
|
|
|
@misc{jrHowThis33yearold2018,
|
|
title = {How This 33-Year-Old College Dropout Co-Founded {{GitHub}}, Which Just Sold to {{Microsoft}} for \$7.5 Billion},
|
|
author = {Jr, Tom Huddleston},
|
|
year = 2018,
|
|
month = jun,
|
|
urldate = {2026-05-19},
|
|
abstract = {Chris Wanstrath co-founded GitHub in 2008, three years after dropping out of college.},
|
|
chapter = {Make It - Entrepreneurs},
|
|
langid = {english},
|
|
file = {C:\Users\Roman\Zotero\storage\KMZMLM2U\chris-wanstrath-co-founded-github-which-microsoft-bought-for-billions.html}
|
|
}
|
|
|
|
@book{kim_devops_2022,
|
|
title = {Das {{DevOps-Handbuch}}: {{Teams}}, Tools Und Infrastrukturen Erfolgreich Umgestalten},
|
|
shorttitle = {Das {{DevOps-Handbuch}}},
|
|
author = {Kim, Gene and Humble, Jez and Debois, Patrick and Willis, John and Forsgren, Nicole},
|
|
year = 2022,
|
|
edition = {2., aktualisierte und erweiterte Auflage},
|
|
pages = {520},
|
|
publisher = {O'Reilly / dpunkt.verlag},
|
|
address = {Heidelberg},
|
|
isbn = {978-3-96009-199-8}
|
|
}
|
|
|
|
@book{newman_building_2021,
|
|
title = {Building Microservices: {{Designing}} Fine-Grained Systems},
|
|
shorttitle = {Building Microservices},
|
|
author = {Newman, Sam},
|
|
year = 2021,
|
|
edition = {2},
|
|
publisher = {O'Reilly Media},
|
|
address = {Sebastopol, CA},
|
|
isbn = {978-1-4920-3402-5}
|
|
}
|
|
|
|
@misc{onlineGitHubVsGitLab2024,
|
|
title = {{GitHub vs. GitLab}},
|
|
author = {{online}, heise},
|
|
year = 2024,
|
|
month = feb,
|
|
urldate = {2026-05-19},
|
|
abstract = {GitHub und GitLab klingen \"ahnlich und sie bieten \"Ahnliches: Source Code Management und Hosting auf git-Basis. Wo liegen die Unterschiede?},
|
|
langid = {ngerman},
|
|
file = {C:\Users\Roman\Zotero\storage\EQGIJ525\GitHub-vs-GitLab-4597154.html}
|
|
}
|
|
|
|
@misc{onlineMicrosoftKauftGitHub2018,
|
|
title = {{Microsoft kauft GitHub f\"ur 7,5 Milliarden US-Dollar}},
|
|
author = {{online}, heise},
|
|
year = 2018,
|
|
month = jun,
|
|
urldate = {2026-05-19},
|
|
abstract = {Was sich bereits angedeutet hat, wurde nun best\"atigt: Der US-amerikanische Softwarekonzern Microsoft kauft GitHub und legt daf\"ur stolze 7,5 Milliarden US-Dollar auf den Tisch.},
|
|
langid = {ngerman},
|
|
file = {C:\Users\Roman\Zotero\storage\VIM5UJ9L\Microsoft-kauft-GitHub-fuer-7-5-Milliarden-US-Dollar-4067633.html}
|
|
}
|
|
|
|
@misc{onlineVersionsverwaltungGitLabRudert2022,
|
|
title = {{Versionsverwaltung: GitLab rudert beim L\"oschen inaktiver Repositories zur\"uck}},
|
|
shorttitle = {{Versionsverwaltung}},
|
|
author = {{online}, heise},
|
|
year = 2022,
|
|
month = aug,
|
|
urldate = {2026-04-17},
|
|
abstract = {Die Pl\"ane, brach liegende Repositories komplett zu l\"oschen, sind laut einem Tweet von GitLab vorerst auf Eis gelegt. Stattdessen sollen sie archiviert werden.},
|
|
langid = {ngerman},
|
|
file = {C:\Users\Roman\Zotero\storage\C88PQIJJ\Versionsverwaltung-GitLab-rudert-beim-Loeschen-inaktiver-Repositories-zurueck-7203006.html}
|
|
}
|
|
|
|
@book{painter_practical_2024,
|
|
title = {Practical {{GitLab}} Services: A Complete {{DevOps}} Guide for Developers and Administrators},
|
|
shorttitle = {Practical {{GitLab}} Services},
|
|
author = {Painter, Jeffrey},
|
|
year = 2024,
|
|
pages = {905},
|
|
publisher = {Apress (Springer Nature)},
|
|
address = {Berkeley, CA},
|
|
doi = {10.1007/979-8-8688-0427-4},
|
|
isbn = {979-8-8688-0426-7}
|
|
}
|
|
|
|
@misc{Q4FY2026GitLab,
|
|
title = {Q4 {{FY2026 GitLab Overview Investor Presentation}} - {{Q4-FY2026-GitLab-Overview-Investor-Presentation}}.Pdf},
|
|
urldate = {2026-05-19},
|
|
file = {C:\Users\Roman\Zotero\storage\ET483VJP\viewer.html}
|
|
}
|
|
|
|
@misc{researcherISO27001Vs2025,
|
|
title = {{{ISO}} 27001 vs. {{NIST}} 800-53: {{Key Differences Explained}}},
|
|
shorttitle = {{{ISO}} 27001 vs. {{NIST}} 800-53},
|
|
author = {Researcher, Security, Zakaria Sahnoune},
|
|
year = 2025,
|
|
month = mar,
|
|
journal = {Security Compass},
|
|
urldate = {2026-06-07},
|
|
abstract = {ISO 27001 and NIST 800-53 are two widely recognized cybersecurity frameworks that help organizations manage security risks and comply with regulatory requirements.},
|
|
langid = {american},
|
|
file = {C:\Users\Roman\Zotero\storage\NDHZP2Y8\iso-27001-vs-nist-800-53.html}
|
|
}
|
|
|
|
@article{rostami_usage_2023,
|
|
title = {On the Usage, Co-Usage and Migration of {{CI}}/{{CD}} Tools: {{A}} Qualitative Analysis},
|
|
shorttitle = {On the Usage, Co-Usage and Migration of {{CI}}/{{CD}} Tools},
|
|
author = {Rostami Mazrae, Pooya and Mens, Tom and Golzadeh, Mehdi and Decan, Alexandre},
|
|
year = 2023,
|
|
journal = {Empirical Software Engineering},
|
|
volume = {28},
|
|
number = {2},
|
|
pages = {52},
|
|
doi = {10.1007/s10664-022-10285-5}
|
|
}
|
|
|
|
@article{shahin_continuous_2017,
|
|
title = {Continuous Integration, Delivery and Deployment: A Systematic Review on Approaches, Tools, Challenges and Practices},
|
|
shorttitle = {Continuous Integration, Delivery and Deployment},
|
|
author = {Shahin, Mojtaba and Babar, Muhammad Ali and Zhu, Liming},
|
|
year = 2017,
|
|
journal = {IEEE access : practical innovations, open solutions},
|
|
volume = {5},
|
|
pages = {3909--3943},
|
|
doi = {10.1109/ACCESS.2017.2685629}
|
|
}
|
|
|
|
@article{soares_effects_2022,
|
|
title = {The Effects of Continuous Integration on Software Development: A Systematic Literature Review},
|
|
shorttitle = {The Effects of Continuous Integration on Software Development},
|
|
author = {Soares, Eliakim and Sizilio, Gustavo and Santos, Jadson and {da Costa}, Daniel Alencar and Kulesza, Uir{\'a}},
|
|
year = 2022,
|
|
journal = {Empirical Software Engineering},
|
|
volume = {27},
|
|
number = {3},
|
|
pages = {78},
|
|
doi = {10.1007/s10664-021-10114-1}
|
|
}
|
|
|
|
@misc{teamGitLabIncGTLB,
|
|
title = {{{GitLab Inc}}. ({{GTLB}}): {{History}}, {{Ownership}}, {{Mission}}, {{How It Works}} \& {{Makes Money}}},
|
|
shorttitle = {{{GitLab Inc}}. ({{GTLB}})},
|
|
author = {{model team}, dcf},
|
|
urldate = {2026-04-19},
|
|
abstract = {With GitLab Inc. (GTLB) reporting a full fiscal year 2025 revenue of over \$759.2 million, up 31\% year-over-year, do you defintely understand how this all-remote powerhouse built the most comprehensive DevSecOps platform? The company's shift to an AI-powered platform is clearly paying off, evidenced by the 29\% year-over-year growth in customers spending over \$100,000 in Annual Recurring Revenue (ARR), but what does its open-source mission-to empower everyone to contribute-really mean for its valuation? You need to see the full picture, from its mixed ownership structure, which includes institutional giants like BlackRock, to the mechanics of how its single-application model actually makes money, so let's break down the history and the financial engine that drives it. GitLab Inc. (GTLB) History You want to understand how GitLab Inc. went from a side project to a DevSecOps powerhouse, and honestly, the journey is a masterclass in open-source monetization and strategic focus. The direct takeaway is that two key decisions-going all-remote and committing to a single-application DevSecOps platform-are responsible for its current scale, which saw it achieve \$759.2 million in revenue for its fiscal year 2025. GitLab Inc.'s Founding Timeline Year established The original open-source project was established in 2011 by Dmytro Zaporozhets. GitLab Inc., the company, was formally incorporated in September 2014, moving the project from a community effort to a commercial venture. Original location The first version of the software was created by Dmytro Zaporozhets from his home in Ukraine. The company later established its headquarters in San Francisco, United States, but famously maintained its all-remote structure from the start. Founding team members The project's creator was Dmytro Zaporozhets, a Ukrainian developer. The co-founder who joined in 2012 to build a business around the open-source code was Sytse 'Sid' Sijbrandij, a Dutch developer who would become the company's long-time CEO. Initial capital/funding The project was initially bootstrapped, meaning it was self-funded and grew organically without external capital. The first significant funding came in 2015, with a \$1.5 million seed round, followed by a \$4 million Series A round from Khosla Ventures later that year. GitLab Inc.'s Evolution Milestones Year Key Event Significance 2011 Initial Open-Source Creation Ukrainian developer Dmytro Zaporozhets created the first version as a side project, establishing the open-source foundation. 2014 GitLab Inc. Incorporation Sytse Sijbrandij formalized the business, leading to the creation of the all-remote company and the adoption of the open-core business model. 2016 Shift to Single-Application DevOps A critical pivot from being just a Git repository manager to a comprehensive DevOps platform, integrating Continuous Integration/Continuous Delivery (CI/CD). 2018 Achieved Unicorn Status Raised \$100 million in Series D funding, valuing the company at \$1.1 billion, validating its expansive DevSecOps strategy. 2021 Initial Public Offering (IPO) Began trading on the NASDAQ under the ticker GTLB on October 14, 2021, marking a major financial milestone and liquidity event. FY 2025 Revenue Surpasses \$750M Reported full fiscal year revenue of \$759.2 million, a 31\% year-over-year increase, showing strong enterprise adoption. GitLab Inc.'s Transformative Moments The company's trajectory wasn't just about incremental growth; it was shaped by a few defintely bold, high-stakes decisions that changed its market position. The Single-Application Vision: Moving beyond simple Git repository management to offer a complete DevSecOps platform in a single application was a game-changer. This integration of development, security, and operations tools reduced the common problem of tool sprawl for customers and became a core differentiator. The All-Remote Mandate: The decision to operate as a fully remote company from its inception allowed GitLab Inc. to hire top talent globally, lower overhead costs, and build a unique, highly transparent culture documented in its public handbook. This model proved to be a massive competitive advantage, especially post-2020. Embracing AI-Native Capabilities: The strategic focus in fiscal year 2025 on AI/ML integration, particularly with the launch of the GitLab Duo features, is the latest transformative move. This shift is designed to automate workflows and boost developer productivity by an estimated 40-50\% for early adopters, positioning the platform for the next wave of software development. This relentless focus on a single, integrated platform has been key to expanding its enterprise customer base, where customers with more than \$1 million in Annual Recurring Revenue (ARR) grew to 123 in FY 2025. You can dig deeper into the financial mechanics of this growth by Breaking Down GitLab Inc. (GTLB) Financial Health: Key Insights for Investors. GitLab Inc. (GTLB) Ownership Structure GitLab Inc. (GTLB) operates with a highly concentrated ownership structure, where institutional investors hold the vast majority of the company's shares, a common trait for high-growth, publicly-traded software companies. This structure means that while co-founder influence is still present, the company's stock price and strategic direction are defintely heavily influenced by the trading decisions of large asset managers like BlackRock and Vanguard Group Inc. Given Company's Current Status GitLab Inc. is a publicly traded company on the NASDAQ Global Select Market under the ticker symbol GTLB. It completed its initial public offering (IPO) in October 2021. As of November 2025, the company maintains a significant market capitalization, which was approximately \$7.39 billion just prior to its Q3 Fiscal Year 2026 earnings release, reflecting its standing as a leader in the DevSecOps platform space. Given Company's Ownership Breakdown The company's ownership profile is dominated by institutional capital, which provides both stability and a strong mandate for financial performance. This is a crucial detail for any investor Exploring GitLab Inc. (GTLB) Investor Profile: Who's Buying and Why?. Here is the breakdown of the common stock ownership as of the most recent filings near November 2025, based on the total shares outstanding. Shareholder Type Ownership, \% Notes Institutional Investors 88.72\% Includes major asset managers like Vanguard Group Inc. (holding \textasciitilde 9.16\%) and BlackRock, Inc. (holding \textasciitilde 4.89\%). Insider Ownership 3.75\% Represents shares held by executives and board members, including co-founder Sytse Sijbrandij. Retail/Individual Investors 7.53\% This is the remaining float, calculated as 100\% minus the institutional and insider holdings. Here's the quick math: when nearly 90\% of the stock is in the hands of institutions, their collective buying or selling can move the share price quickly, so tracking their 13F filings is a must. Given Company's Leadership The management team steering GitLab Inc. is a blend of long-time leaders and recent strategic hires, reflecting the company's focus on scaling its DevSecOps platform and integrating artificial intelligence (AI) capabilities. The executive leadership team, as of November 2025, includes: Bill Staples: Chief Executive Officer (CEO). James Shen: Interim Chief Financial Officer (CFO). He was appointed to this role in September 2025 following the departure of Brian Robins. Manav Khurana: Chief Product and Marketing Officer. Sabrina Farmer: Chief Technology Officer (CTO). Ian Steward: Chief Revenue Officer (CRO). Manu Narayan: Chief Information Officer (CIO). The recent appointment of an Interim CFO in September 2025 shows a focus on maintaining financial stability during a transition, which is typical when a key executive departs for a competitor like Snowflake. Interim appointments like this signal that the board is taking its time to find a long-term fit to drive the next phase of sustainable growth and profitability. GitLab Inc. (GTLB) Mission and Values GitLab Inc.'s purpose extends beyond its impressive financial metrics-like the \$759.2 million in revenue for fiscal year 2025-by focusing on a deeply collaborative and transparent culture that fundamentally changes how software is created. This cultural DNA, built on six core values, is what drives their platform-first strategy and their commitment to open contribution. GitLab Inc.'s Core Purpose You're looking for a company that stands on solid ground, and for GitLab Inc., that foundation is their mission to make all creative work accessible and modifiable, not just read-only. This is a powerful, almost philosophical stance for a software company, and it directly translates into their open-core business model (offering a free, open-source version alongside paid tiers). Official Mission Statement The company's mission is simple but ambitious: to enable everyone to contribute to and co-create the software that powers our world. This isn't just about code; it's about breaking down the barriers between development, security, and operations (DevSecOps) teams, plus all the other stakeholders. Enable everyone to contribute to and co-create the software that powers our world. Vision Statement Their vision is a clear roadmap for achieving that mission, aiming to be the singular platform that facilitates global digital transformation. Honestly, a single, integrated platform is what enterprises are demanding right now to cut down on tool sprawl and complexity. Be the platform that empowers everyone to contribute to all digital transformation. GitLab Inc. Slogan/Tagline While they don't use a punchy, one-word slogan, their positioning is crystal clear, especially as they integrate more artificial intelligence (AI) into their offerings, which is a key growth driver for the business. This focus helped them generate \$120.0 million in Non-GAAP Adjusted Free Cash Flow in FY2025. The most comprehensive AI-powered DevSecOps platform for software innovation. Start shipping better software faster. Core Values (CREDIT) GitLab Inc. is famously an all-remote company, and their six core values-which conveniently spell out CREDIT-act as a distributed decision-making framework for their global workforce. This level of transparency is defintely rare, with over 5,000 pages of their internal processes being public. You can see how these values directly support their mission. Collaboration: Prioritizing asynchronous communication and assuming good intent. Results: Focusing on output and measurable business outcomes. Efficiency: Working smarter, not just harder, to deliver value quickly. Diversity, Inclusion \& Belonging (DIB): A commitment to a global, all-remote team. Iteration: Doing the smallest thing possible and shipping it quickly; small, continuous improvements. Transparency: Making information public by default, which builds trust with users and investors. For a deeper dive into how these principles underpin their financial performance, check out Breaking Down GitLab Inc. (GTLB) Financial Health: Key Insights for Investors. GitLab Inc. (GTLB) How It Works GitLab Inc. operates by delivering the most comprehensive, AI-powered DevSecOps platform as a single application, allowing software teams to manage the entire software development lifecycle-from planning code to deployment and monitoring-in one place. This unified approach eliminates the friction and security gaps that come from stitching together disparate, best-of-breed tools, helping organizations ship more secure software faster. GitLab Inc.'s Product/Service Portfolio The company's offerings are structured around a tiered, subscription-based model that scales with the size and complexity of the customer's needs, driving revenue growth through a clear 'land and expand' strategy. For the fiscal year 2025, this strategy helped drive total revenue to \$759.2 million. Product/Service Target Market Key Features Free/Community Edition Individual Developers, Small Teams, Open Source Projects Core Git repository management, basic CI/CD (Continuous Integration/Continuous Delivery), and issue tracking. It is the foundation of the open-core model. Premium Mid-Market \& Scaling Teams (e.g., 9,893 customers with {$>\$$}5K ARR) Enhanced workflow management, enterprise-grade support (24/7), advanced CI/CD features, and compliance controls. Focuses on improving team efficiency and collaboration. Ultimate (including GitLab Duo) Large Enterprises \& Highly Regulated Industries (e.g., 1,229 customers with {$>\$$}100K ARR) Full DevSecOps capabilities: Advanced security testing (SAST, DAST), compliance, portfolio management, and GitLab Duo (AI-powered code generation and assistance). GitLab Inc.'s Operational Framework GitLab's operational framework is built on a few core principles that translate directly into value creation for customers. Honestly, it's all about consolidation and efficiency. They are the only cloud-agnostic, model-neutral DevSecOps platform, meaning you can run it anywhere, which is a huge draw for large companies. The company's revenue growth, which hit 31\% for FY 2025, is primarily driven by this 'land and expand' motion, where customers start with lower tiers and expand to Premium or Ultimate as they consolidate their toolchains. Single Application Approach: Instead of integrating 10+ disparate tools for planning, coding, testing, securing, and deploying, GitLab provides a single codebase and unified data model. This cuts down on integration costs and context switching for developers. Open-Core Business Model: The free, open-source Community Edition drives widespread adoption and a massive user base (over 50 million registered users), which acts as a powerful top-of-funnel for their paid Premium and Ultimate subscriptions. AI-Driven Development: A key FY25 investment theme was enabling AI/ML efficiencies across DevSecOps, with GitLab Duo moving from 'AI-assisted' to 'AI-driven' to boost developer productivity and ensure security and compliance for AI-generated code. You can see how this operational focus aligns with their core beliefs: Mission Statement, Vision, \& Core Values of GitLab Inc. (GTLB). GitLab Inc.'s Strategic Advantages The company's market success comes down to three clear advantages: platform completeness, a superior economic model, and their commitment to AI-native security. What this estimate hides, though, is the intense competition from Microsoft's GitHub, still the primary risk. Toolchain Consolidation: The single DevSecOps platform is a major differentiator against competitors like Microsoft Corporation's GitHub, which often requires users to integrate third-party tools for security and operations. This consolidation saves time and money for enterprise customers. Exceptional Unit Economics: GitLab maintains a very high gross profit margin, sitting at about 88.52\% as of late 2025, giving them significant capital flexibility to invest in their AI platform. High Customer Expansion: Their dollar-based net retention rate (DBNRR) was a strong 123\% in Q4 FY25, meaning existing customers spent 23\% more on average than they did the previous year. This shows the 'expand' part of their strategy is working defintely well. Financial Strength and Efficiency: For the full fiscal year 2025, the company achieved a non-GAAP operating margin of 10\% and a non-GAAP adjusted free cash flow of \$120.0 million, demonstrating a focus on profitable growth, which is rare in the high-growth software sector. GitLab Inc. (GTLB) How It Makes Money GitLab Inc. (GTLB) primarily generates revenue by selling subscriptions to its comprehensive DevSecOps platform, which is offered as both a cloud-based Software-as-a-Service (SaaS) and a self-managed solution. The company's financial engine is built on recurring subscription fees, meaning predictable, high-margin revenue from customers who pay per user to access its integrated development, security, and operations tools. GitLab Inc.'s Revenue Breakdown You need to see where the money is actually coming from, not just the top-line number. For the second quarter of fiscal year 2026 (ended July 31, 2025), GitLab's revenue was \$236.0 million, and the breakdown confirms the dominance of the subscription model. Revenue Stream \% of Total (Q2 FY2026) Growth Trend Subscription (SaaS \& Self-Managed) 90.13\% Increasing Professional Services \& Other 9.87\% Increasing That 90.13\% from subscriptions is the core of their business model, a classic high-quality SaaS revenue stream. The Subscription revenue of \$212.7 million in Q2 FY2026 was the main driver of the overall 29\% year-over-year revenue growth. Business Economics The real story here is how GitLab is monetizing its customer base, and that means looking beyond the initial sale. Their business economics are shifting toward a hybrid model to capture more value from heavy users, especially with the rise of AI-powered development. High Retention: The Dollar-Based Net Retention Rate (DBNRR) was 121\% in Q2 FY2026. This means existing customers, on average, spent 21\% more this year than last year. That's a huge lever for growth. Gross Margin Strength: Non-GAAP Gross Margin stood at a very healthy 90\% in Q2 FY2026. This high margin shows the platform's efficiency and scalability, proving that selling another user seat costs the company very little. Hybrid Pricing Model: GitLab is transitioning from a purely seat-based subscription to a seat-plus-usage model. This lets them charge for the base access and for consumption of high-value features, like their AI agent, GitLab Duo, which is priced at \$19 per month per user. This is defintely a smart move to monetize the AI productivity boom. Here's the quick math: a 121\% DBNRR means they grow revenue even if they don't add a single new customer, just by getting existing ones to expand their usage or upgrade their tier. GitLab Inc.'s Financial Performance The financial trend is clear: strong growth is being paired with a rapid move toward operational efficiency, which is what you want to see in a maturing software company. For more detail on the structural health of the business, you should check out Breaking Down GitLab Inc. (GTLB) Financial Health: Key Insights for Investors. Annual Revenue: Total revenue for the full fiscal year 2025 reached \$759.2 million, marking a robust 31\% increase year-over-year. Operating Profitability: The non-GAAP Operating Margin has seen massive expansion, moving from 10\% for the full FY2025 to 17\% in the more recent Q2 FY2026. This indicates serious operational leverage as the company scales. Cash Flow Generation: GitLab is generating substantial free cash flow (FCF), a sign of financial health. Non-GAAP Adjusted Free Cash Flow for FY2025 was \$120.0 million. In Q2 FY2026 alone, it was \$46.5 million. Enterprise Customer Growth: The most valuable customers are expanding quickly. The number of customers with over \$100,000 in Annual Recurring Revenue (ARR) grew 25\% year-over-year in Q2 FY2026, reaching 1,344 customers. These large contracts underpin the revenue stability. GitLab Inc. (GTLB) Market Position \& Future Outlook GitLab Inc. is defintely positioned as the leading integrated DevSecOps platform, aggressively challenging the incumbent toolchain model by consolidating the entire software development lifecycle (SDLC) into a single application. The company's focus on AI-driven security and compliance positions it to capture a larger share of the enterprise market, targeting an estimated full-year Fiscal Year 2025 revenue of approximately \$753 million. You're looking at a company that's not just selling a tool, but a platform philosophy-so its near-term success hinges on converting customers from fragmented toolchains (like Jira + Jenkins + GitHub) to its all-in-one solution. Competitive Landscape The DevOps market, valued at around \$16.13 billion in 2025, is a battleground between integrated platforms and best-of-breed toolchains. GitLab's primary competition comes from Microsoft-owned GitHub and the Atlassian ecosystem, each dominating different parts of the SDLC. Here's the quick math on the relative market positioning as of late 2025, based on platform adoption and CI/CD tool usage: Company Market Share, \% Key Advantage GitLab Inc. 12\% Single, integrated DevSecOps platform; strong self-managed/compliance features. GitHub (Microsoft) 55\% Dominant code hosting, largest developer community, expansive third-party Actions ecosystem. Atlassian (Bitbucket) 18.61\% Deep integration with Jira and Confluence; strong presence in the Continuous Integration/Continuous Delivery (CI/CD) tools market. Opportunities \& Challenges GitLab's strategic initiatives for late 2025 and into 2026 center on AI and enterprise compliance, but still face headwinds from established competitors and a complex regulatory environment. Opportunities Risks AI-Native DevSecOps: Monetizing GitLab Duo (AI orchestration platform) to accelerate development by an early-reported 50\%. AI Competition \& Pricing Pressure: Aggressive AI product launches from Microsoft (GitHub Copilot) and other cloud vendors. Enterprise Consolidation: Driving adoption of the Ultimate tier, which focuses on security and compliance, to increase the Dollar-Based Net Retention Rate (DBNRR), which was 121\% in Q2 FY2026. Macroeconomic Spending Slowdown: Enterprise customers optimizing cloud and software budgets, which can delay platform migration decisions. Regulated/Sovereign Cloud: Expanding the GitLab Dedicated offering via the partnership with Amazon Web Services Inc. (AWS) to capture highly regulated industries requiring data residency. Leadership Transition: CFO Brian Robins' departure in September 2025 introduces a minor, but real, operational risk during a critical growth phase. Industry Position GitLab is a clear leader in the DevSecOps platform category, often recognized for its completeness over competitors who rely on assembling toolchains. The company's unique all-remote structure also gives it an edge in talent acquisition and operational efficiency. Win the Platform War: The strategy is to win on platform completeness, offering a single data model for the entire SDLC, which eliminates context switching and tool sprawl friction. Ultimate Tier Focus: Continued investment in security, compliance, and governance features drives higher average selling prices (ASPs) and targets the large enterprise market. Investor Confidence: The company's guidance for Fiscal Year 2026 revenue of \$936 million to \$942 million suggests strong confidence in sustaining momentum. This aggressive push into AI and compliance is why you should be watching their customer adoption metrics closely. You can find more details on institutional holdings and investment theses here: Exploring GitLab Inc. (GTLB) Investor Profile: Who's Buying and Why?},
|
|
langid = {english},
|
|
file = {C:\Users\Roman\Zotero\storage\GEFBWV3L\gtlb-history-mission-ownership.html}
|
|
}
|
|
|
|
@book{wolff_microservices_2018,
|
|
title = {Microservices: {{Grundlagen}} Flexibler Softwarearchitekturen},
|
|
shorttitle = {Microservices},
|
|
author = {Wolff, Eberhard},
|
|
year = 2018,
|
|
edition = {2.},
|
|
pages = {374},
|
|
publisher = {dpunkt.verlag},
|
|
address = {Heidelberg},
|
|
isbn = {978-3-86490-555-1}
|
|
}
|
|
|
|
@article{zampetti_empirical_2020,
|
|
title = {An Empirical Characterization of Bad Practices in Continuous Integration},
|
|
author = {Zampetti, Fiorella and Vassallo, Carmine and Panichella, Sebastiano and Canfora, Gerardo and Gall, Harald and Di Penta, Massimiliano},
|
|
year = 2020,
|
|
journal = {Empirical Software Engineering},
|
|
volume = {25},
|
|
number = {2},
|
|
pages = {1095--1135},
|
|
doi = {10.1007/s10664-019-09785-8}
|
|
}
|