gitlab

GitLab combines Git hosting with an integrated CI/CD pipeline system where .gitlab-ci.yml defines stages, jobs, runners, artifacts and environments; using GitLab CI involves pipeline optimization, caching, containerized jobs, and integration with the GitLab registry and deploy environments.

gitlab

12-Month Skill Trend

Momentum and market value over time
Trending
Score
+20 in 12 mo
96
12 mo agoNow
Career
Value
+$12K in 12 mo
$42K/year
12 mo agoNow

Recommended Survey Paper

Quick overview of the field
View more

Must-Read Papers

Most classic and influential ideas
View more

This study addresses the widespread yet underrecognized issue of cache-related code smells in GitLab CI/CD pipelines, which significantly degrade pipeline performance and reliability. The authors present the first systematic characterization of ten distinct cache smells and introduce CROSSER, a novel automated detection tool that combines static analysis with rule-based matching. The effectiveness of CROSSER is rigorously evaluated through grey literature validation and a large-scale empirical study across 228 open-source projects, revealing that 89% of these projects exhibit at least one type of cache smell. When applied to 82 projects, CROSSER achieves an F1 score of 0.98, demonstrating substantial improvements in both detection accuracy and scalability over existing approaches.

cache-related smellsCI/CDGitLab

Controller-Light CI/CD with Jenkins: Remote Container Builds and Automated Artifact Delivery

Nov 07, 2025
KK
Kawshik Kumar Paul
🏛️ Bangladesh University of Engineering and Technology | Chittagong University of Engineering and Technology

Traditional Jenkins controllers suffer from resource overloading and reduced reliability due to direct execution of build tasks. To address this, we propose a lightweight CI/CD architecture that containerizes the Jenkins controller and offloads all build execution to remote Docker hosts via secure SSH connections—effectively decoupling orchestration from build execution. The architecture incorporates atomic deployments, timestamped artifact backups, immutable artifact packaging, and automated notification mechanisms. Technically, it integrates persistent volumes, containerized build environments, and declarative pipelines. Experimental evaluation demonstrates a significant reduction in controller CPU and memory utilization, a 32% increase in build throughput, and a 41% decrease in artifact delivery latency. The solution delivers high stability, scalability, and low operational overhead, making it particularly suitable for small- to medium-scale DevOps environments.

Delegates intensive build operations to remote Docker hostsProvides scalable automation with simplified orchestration for DevOpsReduces resource overload on Jenkins controller by offloading builds

This study addresses the lack of systematic understanding in the configuration and maintenance of CI/CD caching, which imposes a significant burden on developers despite its benefits for build efficiency. Through a large-scale empirical analysis of 952 repositories on GitHub Actions—encompassing 1,556 workflow files and over ten thousand cache-related changes—the authors employ code mining, configuration analysis, commit tracing, and statistical modeling to uncover real-world caching practices, evolutionary patterns, and human-bot collaboration in maintenance. The findings reveal that cache adopters are more active, caching strategies are diverse and frequently adjusted, and build- and test-related tasks evolve rapidly. Manual interventions primarily address misconfigurations, whereas version upgrades are predominantly automated by bots. The work quantifies the maintenance overhead of caching and provides empirical foundations for improving developer tooling.

cache maintenanceCI/CD cachingempirical study

Automatic Pipeline Provisioning

Nov 18, 2025
AL
Alexandre-Xavier Labonté-Lamoureux
🏛️ École de Technologie Supérieure

To address the challenges of prolonged CI pipeline deployment cycles, error-prone manual configuration, and poor cross-project consistency, this paper proposes an automated pipeline configuration framework grounded in Infrastructure-as-Code (IaC) principles and templated configuration. The framework enables declarative definition and one-click generation of CI/CD pipelines via reusable YAML templates, a parameterized pipeline engine, and an integrated automation toolchain. Compared to conventional manual approaches, our method reduces average pipeline deployment time by 72% and decreases human configuration errors by 91%, while substantially improving consistency in build logic and execution environments across projects. Empirical validation across six open-source projects demonstrates the framework’s engineering practicality and methodological generality. It provides a reusable implementation model and actionable methodology for CI/CD automation, advancing scalable, maintainable, and reproducible software delivery practices.

Applying automatic deployment for software engineering projectsExploring benefits of automatic pipeline provisioningFocusing on CI pipelines with similar CD implications

This work addresses the challenge developers face in efficiently authoring CI/CD configurations due to limited DevOps expertise by proposing a large language model (LLM)-based, context-aware generation approach. The method leverages both natural language descriptions and repository structure to automatically produce accurate and executable pipeline configurations for platforms such as GitHub Actions and GitLab CI/CD. Integrated with automated validation and human-in-the-loop feedback mechanisms, this framework is the first to combine repository context understanding with natural language-driven configuration synthesis. Experimental results demonstrate that the approach significantly lowers the barrier to DevOps adoption, markedly improves the accuracy and validity of generated configurations, and substantially reduces manual configuration effort.

CI/CD pipeline configurationconfiguration errorsdeveloper productivity

Latest Papers

What's happening recently
View more

This work addresses the fragility, inefficiency, and strong platform coupling commonly found in CI/CD pipelines for legacy COBOL systems, which often result in high maintenance costs and vendor lock-in. To overcome these challenges, the authors propose a portable CI/CD architecture tailored for highly secure and compliance-driven environments. The approach leverages OCI-compliant container images preloaded with COBOL toolchains, introduces a platform abstraction layer, integrates multiple repositories, and employs Groovy script refactoring to achieve platform-agnostic continuous integration and delivery. Empirical evaluation demonstrates that the proposed solution significantly enhances efficiency—reducing pipeline execution time by 82%—while simultaneously improving system portability, security, and maintainability. This architecture offers a reusable paradigm for modernizing legacy COBOL applications within regulated domains.

CI/CDCOBOLlegacy systems

This work addresses the lack of quantified energy-efficiency feedback in current CI/CD pipelines for containerized microservices, which hinders the evaluation of code changes’ energy impact. We propose an integrated approach that seamlessly embeds hardware-level power measurements into GitLab CI by orchestrating workload generation, container monitoring, and power probing to automatically collect comparable performance and energy metrics on every code commit. To our knowledge, this is the first method to incorporate hardware-grade energy monitoring directly into containerized continuous delivery workflows, enabling cross-version energy-efficiency comparisons and trend analysis. The feasibility and measurement validity of the proposed architecture were successfully demonstrated through four consecutive commits to a JWT authentication API, effectively bridging the gap in energy-aware feedback within CI/CD systems.

CI/CD pipelinecontainer-based applicationsenergy consumption

This study addresses the impact of continuous integration (CI) build duration on developer productivity and investigates the underexplored adoption and efficacy of caching as a build acceleration technique. Through a large-scale empirical analysis of 513,384 builds across 1,279 GitHub projects on Travis CI—combining log analysis, pull request intervention experiments, and developer feedback—the work reveals that CI caching is adopted by only 30% of projects, largely due to developers’ limited awareness and the perceived maintenance complexity. Notably, nearly half of previously non-adopting projects accepted caching configurations when proposed via pull requests, with approximately one-third achieving significant speedups. However, widespread issues of cache redundancy and staleness were also observed, underscoring both the feasibility and necessity of optimizing CI caching practices.

Build PerformanceCache MaintenanceCaching

This work addresses the absence of Git-like data versioning in existing lakehouse architectures, which hinders collaborative development among multiple agents and human-in-the-loop review workflows. To bridge this gap, the paper introduces Git semantics into lakehouse systems by extending Apache Iceberg to support lakehouse-wide commits, branches, and merges—elevating single-table snapshots to a unified versioning model. This enables agents to operate on isolated branches while ensuring atomic, cross-table changes during release. The core abstractions are formally modeled and verified using Alloy to guarantee semantic correctness. The proposed system has been deployed in production, demonstrating the feasibility and effectiveness of the collaborative workflow it enables.

agent-first lakehouseatomic publishingbranching and merging

This work addresses the limitations of existing CI/CD workflow analyses, which often focus narrowly on stage identification and struggle to assess reliability, maintainability, and optimization priorities. To overcome this, we propose a large language model–based CI/CD analysis pipeline that integrates repository context enhancement, anti-pattern detection, stage mining, and actionable recommendation generation. Our approach uniquely combines diagnostic reasoning, context awareness, and human-in-the-loop review to deliver observability tailored to cybersecurity engineering. Leveraging few-shot prompting, YAML parsing, and statistical tests (chi-square and Cramér’s V), the method identifies 434,769 anti-patterns across 75,201 workflows and generates an average of 8.25 syntactically valid optimization suggestions per repository, achieving a 96.1% compliance rate with YAML syntax standards.

anti-pattern detectionCI/CD workflowcyber systems engineering

Hot Scholars

FB

Francis Bordeleau

École de Technologie Supérieure (ETS)
Software engineeringmodel-based engineeringopen source
UZ

Uwe Zdun

University of Vienna
Software EngineeringSoftware ArchitectureDistributed SystemsService Computing
YT

Yuan Tian

Associate Professor, School of Computing, Queen's University, Canada
Data MiningSoftware EngineeringLLM for SEMachine Learning