diff --git a/.gitignore b/.gitignore index f98146e..538f378 100644 --- a/.gitignore +++ b/.gitignore @@ -9,3 +9,5 @@ latex/temp/ *.run.xml *.synctex.gz *.toc +*.dvi +*.out diff --git a/DMS_paper15_gitlab.tex b/DMS_paper15_gitlab.tex index d726e01..a810fe5 100644 --- a/DMS_paper15_gitlab.tex +++ b/DMS_paper15_gitlab.tex @@ -6,14 +6,19 @@ \usepackage[ngerman]{babel} \usepackage{multicol}[] \usepackage{blindtext} +\usepackage{float} \usepackage{fancyhdr} \usepackage{geometry} \usepackage{abstract} +\usepackage{graphicx} \usepackage{acronym} +\usepackage{hyperref} \usepackage{biblatex} +\graphicspath{ {./bilder/} } + \geometry{ a4paper,margin=25mm } @@ -49,20 +54,49 @@ + \begin{multicols}{2} \tableofcontents - \section{Einführung} + \section{Einleitung} \subsection{Softwarelösung} + Gitlab ist eine mit Git kompatible Plattform für Code-Hosting. Der Code von Gitlab ist in Ruby verfasst \cite{degeler_gitlab_2014}. Unter der Haube verwendet Git die relationale Datenbank PostgreSQL. Auf Gitlab kann mithilfe einer Weboberfläche zugegriffen werden \cite{gitlab_about}: + Gitlab kann in folgenden unterschiedlichen Formen genutzt werden: + \begin{itemize} + \item \textbf{\ac{SaaS}} Die Plattform wird innerhalb der Cloud von Gitlab gehostet. + \item \textbf{Selbst gehostet} Gitlab kann auf linux-basierten Servern selbst betrieben werden. + \item \textbf{Dediziertes \ac{SaaS}} Für Unternehmen und Regierungen kann Gitlab in eigenen isolierten Instanzen verwendet werden, um hohe Sicherheitsstandards zu gewährleisten. + \end{itemize} + + + \subsection{Geschichte} - \subsection{Funktionalitäten} + + Gitlab wurde von Sytse Sijbrandij und von Dmitriy Zaporozhets gegründet. Zaporozhets entwickelte Gitlab 2011 als Hilfsmittel für seine eigenen Projekte. Gitlab war zu dem Zeitpunkt eine private und freie Plattform zum eigenen Code-Hosting, entwickelt von Zaporozhets. Nachdem Zaporozhets sich entschied den Quellcode von Gitlab frei zugänglich zu machen, entstand die Partnerschaft mit Sijbrandij. Um den Einstieg in die Nutzung von Gitlab zu erleichtern entschieden sich Sijbrandij GitLab als \ac{SaaS} unter der Domain \url{https://gitlab.com/} anzubieten. Der Quellcode von Gitlab ist frei unter \url{https://gitlab.com/gitlab-org/gitlab} verfügbar \cite{degeler_gitlab_2014}. 2014 wurde Gitlab erstmalig als Unternehmen eingetragen und erfuhr seitdem einen grossen Zuwachs an Mitarbeitern. Aktuell zählt Gitlab mehr als 2600 Mitarbeiter, die über 65 Länder verteilt leben \cite{gitlab_about}. Gitlab selbst besitzt keinen ausgebauten Firmenhauptsitz, da Mitarbeiter hauptsächlich remote arbeiten und freie Verfügung über ihre Arbeitszeit haben \cite{choudhuryGitLabWorkWhere2020}. Gitlab finanziert sich durch Spenden um neue Funktionalitäten zu realisieren. Ein weiterer Teil der Einnahmen kommt durch den Abschluss von Abonnements der Enterprise-Edition \cite{degeler_gitlab_2014}. + Abbildung \ref{fig:gitlab-logo} zeigt das Logo von Gitlab. Es besteht aus einem Tanuki, einem in Japan heimischen Waschbärhund, und dem Gitlab Schriftzug. + \begin{figure}[H] + \centering + \includegraphics[width=0.8\linewidth]{./bilder/gitlab-logo-100-rgb.png} + \label{fig:gitlab-logo} + \caption{Logo Gitlab} + \end{figure} + Gitlab erregte in mehreren Fällen mediale Aufmerksamkeit auf sich. 2017 verlor die \ac{SaaS}-Lösung von Gitlab sechs Stunden an Nutzerdaten, aufgrund von einer menschlichen Fehlreaktion, ausgelöst durch Spamanfragen die in Problemen mit der Datenbank resultierten \cite{GitLabcomDatabaseIncident}. Ebenso bestanden 2022 Pläne inaktive Repositories löschen. Nach starker Kritik wurde sich dazu entschieden, anstatt zu löschen, zu archivieren \cite{onlineVersionsverwaltungGitLabRudert2022}. + \subsection{Aufbau} + Zusammenarbeit in Gitlab ist in Form von Gruppen organisiert. Diese können in Subgruppen unterteilt werden. Gruppen und Subgruppen können Projekte und Mitarbeiter zugeordnet werden. + Jedes Projekt besteht aus einer Issue-Seite, einem Wiki und einem Code-Repository. \cite{gitlab_gitlab_nodate} + % Vergleich von Features mit Github möglich + \subsection{Funktionalitäten} + + + \section{CI/CD} %https://docs.gitlab.com/topics/build_your_application/ + \subsection{Einführung} \subsection{Gitlab Runner} \subsection{Pipelines} \subsection{Jobs} @@ -94,6 +128,8 @@ \section{Ausblick} + \section{Zusammenfassung} + Hallo Welt \cite{arefeen_continuous_2019} \subsection{Geschichte} @@ -101,6 +137,7 @@ \section*{Abkürzungsverzeichnis} \begin{acronym}[Abkürzungsverzeichnis] \acro{CI/CD}{Continuous Integration/Continous Delivery} + \acro{SaaS}{Software as a Service} \end{acronym} \printbibliography diff --git a/bilder/gitlab-logo-100-rgb.png b/bilder/gitlab-logo-100-rgb.png new file mode 100644 index 0000000..206528b Binary files /dev/null and b/bilder/gitlab-logo-100-rgb.png differ diff --git a/bilder/gitlab-logo-150-cmyk.jpg b/bilder/gitlab-logo-150-cmyk.jpg new file mode 100644 index 0000000..c1442c8 Binary files /dev/null and b/bilder/gitlab-logo-150-cmyk.jpg differ diff --git a/literatur/dms.bib b/literatur/dms.bib index d7a2763..5ecf9a0 100644 --- a/literatur/dms.bib +++ b/literatur/dms.bib @@ -1,4 +1,24 @@ +@article{choudhuryGitLabWorkWhere2020, + title = {{GitLab}: work where you want, when you want}, + volume = {9}, + issn = {2245-408X}, + shorttitle = {{GitLab}}, + url = {https://doi.org/10.1186/s41469-020-00087-8}, + doi = {10.1186/s41469-020-00087-8}, + 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.}, + language = {en}, + number = {1}, + urldate = {2026-04-15}, + journal = {Journal of Organization Design}, + author = {Choudhury, Prithwiraj and Crowston, Kevin and Dahlander, Linus and Minervini, Marco S. and Raghuram, Sumita}, + month = nov, + year = {2020}, + keywords = {All remote, COVID-19, New forms of organizing, Organizational design, Remote work, Virtual organizations}, + pages = {23}, + file = {Full Text PDF:C\:\\Users\\Roman\\Zotero\\storage\\IT677T3E\\Choudhury et al. - 2020 - GitLab work where you want, when you want.pdf:application/pdf}, +} + @article{arefeen_continuous_2019, title = {Continuous {Integration} {Using} {Gitlab}}, volume = {3}, @@ -14,5 +34,58 @@ year = {2019}, keywords = {agile, continuous integration, GitLab, software testing}, pages = {1--6}, - file = {Full Text PDF:C\:\\Users\\Roman\\Zotero\\storage\\6BZWIRLI\\Arefeen und Schiller - 2019 - Continuous Integration Using Gitlab.pdf:application/pdf}, +} + +@misc{gitlab_gitlab_nodate, + title = {{GitLab} {Docs}}, + url = {https://docs.gitlab.com/}, + urldate = {2026-04-16}, + author = {{Gitlab}}, +} + +@misc{degeler_gitlab_2014, + title = {{GitLab} is building a business with 0.1\% of paying customers}, + url = {https://thenextweb.com/news/github-rival-gitlab-building-business-just-0-1-paying-customers}, + 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.}, + language = {en}, + urldate = {2026-04-16}, + author = {Degeler, Andrii}, + month = jun, + year = {2014}, + annote = {Section: Insider}, +} + +@misc{gitlab_about, + title = {About {Gitlab}}, + url = {https://about.gitlab.com/}, + abstract = {Your intelligent orchestration platform for DevSecOps}, + language = {en-US}, + urldate = {2026-04-17}, + journal = {about.gitlab.com}, + author = {Gitlab}, + file = {Snapshot:C\:\\Users\\Roman\\Zotero\\storage\\T886BE4A\\about.gitlab.com.html:text/html}, +} + +@misc{GitLabcomDatabaseIncident, + title = {{GitLab}.com database incident}, + url = {https://about.gitlab.com/blog/gitlab-dot-com-database-incident/}, + 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.}, + language = {en-US}, + urldate = {2026-04-17}, + journal = {about.gitlab.com}, + file = {Snapshot:C\:\\Users\\Roman\\Zotero\\storage\\LBYJ7RZX\\gitlab-dot-com-database-incident.html:text/html}, +} + +@misc{onlineVersionsverwaltungGitLabRudert2022, + title = {Versionsverwaltung: {GitLab} rudert beim {Löschen} inaktiver {Repositories} zurück}, + shorttitle = {Versionsverwaltung}, + url = {https://www.heise.de/news/Versionsverwaltung-GitLab-rudert-beim-Loeschen-inaktiver-Repositories-zurueck-7203006.html}, + abstract = {Die Pläne, brach liegende Repositories komplett zu löschen, sind laut einem Tweet von GitLab vorerst auf Eis gelegt. Stattdessen sollen sie archiviert werden.}, + language = {de}, + urldate = {2026-04-17}, + journal = {Developer}, + author = {online, heise}, + month = aug, + year = {2022}, + file = {Snapshot:C\:\\Users\\Roman\\Zotero\\storage\\3N8Y75DY\\Versionsverwaltung-GitLab-rudert-beim-Loeschen-inaktiver-Repositories-zurueck-7203006.html:text/html}, } diff --git a/literatur/dms.rdf b/literatur/dms.rdf index 9d926d2..9283f52 100644 --- a/literatur/dms.rdf +++ b/literatur/dms.rdf @@ -7,6 +7,103 @@ xmlns:link="http://purl.org/rss/1.0/modules/link/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:prism="http://prismstandard.org/namespaces/1.2/basic/"> + + journalArticle + + + + + + Choudhury + Prithwiraj + + + + + Crowston + Kevin + + + + + Dahlander + Linus + + + + + Minervini + Marco S. + + + + + Raghuram + Sumita + + + + + + + All remote + + + COVID-19 + + + + New forms of organizing + + + + + Organizational design + + + + Remote work + + + + Virtual organizations + + + GitLab: work where you want, when you want + 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. + 2020-11-16 + en + GitLab + Springer Link + + + https://doi.org/10.1186/s41469-020-00087-8 + + + 2026-04-15 16:57:19 + 23 + choudhuryGitLabWorkWhere2020 + + + 9 + Journal of Organization Design + DOI 10.1186/s41469-020-00087-8 + 1 + J Org Design + ISSN 2245-408X + + + attachment + Full Text PDF + + + https://link.springer.com/content/pdf/10.1186%2Fs41469-020-00087-8.pdf + + + 2026-04-15 16:57:19 + 1 + application/pdf + journalArticle @@ -26,35 +123,23 @@ - - - agile - - - - continuous integration - - - - GitLab - - - - software testing - - + agile + continuous integration + GitLab + software testing Continuous Integration Using Gitlab 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. - 2019-09-11 + 2019-09 en - www.urncst.com https://www.urncst.com/index.php/urncst/article/view/152 - 2026-04-15 15:15:21 - 1-6 + 2026-04-15 + Citation Key: arefeen_continuous_2019 + 1–6 + arefeen_continuous_2019 3 @@ -62,15 +147,259 @@ DOI 10.26685/urncst.152 ISSN 2561-5637 - + + document + + + + Gitlab + + + + GitLab Docs + + + https://docs.gitlab.com/ + + + 2026-04-16 + Citation Key: gitlab_gitlab_nodate + gitlab_gitlab_nodate + + + document + + + + + Degeler + Andrii + + + + + + GitLab is building a business with 0.1% of paying customers + 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. + 2014-06 + en + + + https://thenextweb.com/news/github-rival-gitlab-building-business-just-0-1-paying-customers + + + 2026-04-16 + Citation Key: degeler_gitlab_2014 + degeler_gitlab_2014 + + + Section: Insider + + + webpage + + about.gitlab.com + + + + + Gitlab + + + + + About Gitlab + Your intelligent orchestration platform for DevSecOps + en-US + + + https://about.gitlab.com/ + + + 2026-04-17 15:41:17 + gitlab_about + + + attachment + Snapshot + + + https://about.gitlab.com/ + + + 2026-04-17 15:41:23 + 1 + text/html + + + webpage + + about.gitlab.com + + + GitLab.com database incident + 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. + en-US + + + https://about.gitlab.com/blog/gitlab-dot-com-database-incident/ + + + 2026-04-17 16:46:23 + GitLabcomDatabaseIncident + + + attachment + Snapshot + + + https://about.gitlab.com/blog/gitlab-dot-com-database-incident/ + + + 2026-04-17 16:46:27 + 1 + text/html + + + webpage + + Developer + + + + + + online + heise + + + + + + Versionsverwaltung: GitLab rudert beim Löschen inaktiver Repositories zurück + Die Pläne, brach liegende Repositories komplett zu löschen, sind laut einem Tweet von GitLab vorerst auf Eis gelegt. Stattdessen sollen sie archiviert werden. + 2022-08-05 + de + Versionsverwaltung + + + https://www.heise.de/news/Versionsverwaltung-GitLab-rudert-beim-Loeschen-inaktiver-Repositories-zurueck-7203006.html + + + 2026-04-17 16:57:10 + onlineVersionsverwaltungGitLabRudert2022 + + + attachment + Snapshot + + + https://www.heise.de/news/Versionsverwaltung-GitLab-rudert-beim-Loeschen-inaktiver-Repositories-zurueck-7203006.html + + + 2026-04-17 16:57:16 + 1 + text/html + + + conferencePaper + + + + + + Fairbanks + Jeffrey + + + + + Tharigonda + Akshharaa + + + + + Eisty + Nasir U. + + + + + + + Software + + + CI/CD + + + Codes + + + + Mining Repositories + + + + + Open-Source Software + + + + Pipelines + + + Recording + + + + Software development management + + + + + Software engineering + + + + + Software Engineering + + + Analyzing the Effects of CI/CD on Open Source Repositories in GitHub and GitLab + 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%. + 2023-05 + IEEE Xplore + + + https://ieeexplore.ieee.org/document/10197778/ + + + 2026-04-17 17:10:14 + ISSN: 2770-8209 + 176-181 + + + 2023 IEEE/ACIS 21st International Conference on Software Engineering Research, Management and Applications (SERA) + + + fairbanksAnalyzingEffectsCI2023 + + + 2023 IEEE/ACIS 21st International Conference on Software Engineering Research, Management and Applications (SERA) + DOI 10.1109/SERA57763.2023.10197778 + ISSN 2770-8209 + + attachment Full Text PDF - https://www.urncst.com/index.php/urncst/article/download/152/35 + https://ieeexplore.ieee.org/stampPDF/getPDF.jsp?tp=&arnumber=10197778&ref= - 2026-04-15 15:15:22 + 2026-04-17 17:10:17 1 application/pdf