GitLab CI
5 articles from official documentation
Mastering GitLab CI Runners: Timeout Configurations You Need
Configuring GitLab CI runners effectively can make or break your CI/CD pipeline. Learn how to set maximum job timeouts and script timeouts to keep your builds efficient and under control. This article dives into practical configurations that matter in production.
- →Set `maximum_timeout` to prevent long-running jobs from monopolizing runners.
- →Use `RUNNER_SCRIPT_TIMEOUT` to enforce strict limits on script execution time.
Mastering Environments in GitLab CI/CD: Static vs. Dynamic
Understanding environments in GitLab CI/CD is crucial for effective deployment strategies. You can create both static and dynamic environments, each serving distinct roles in your deployment pipeline. This article dives into how to leverage these environments for maximum efficiency.
- →Utilize static environments for consistent deployments across staging and production.
- →Leverage dynamic environments for temporary review apps that are created and destroyed per deployment.
Maximizing GitLab CI Pipeline Efficiency: Key Strategies
Pipeline efficiency can make or break your CI/CD process. Understanding the critical path and leveraging caching can significantly reduce your pipeline duration. Dive in to discover actionable strategies that improve performance.
- →Analyze the critical path to identify the minimum and maximum pipeline duration.
- →Use the `needs` keyword to visualize dependencies and find potential blockers.
Mastering GitLab CI/CD YAML: Key Syntax for Success
Get your CI/CD pipelines running smoothly with GitLab's YAML syntax. Learn how to effectively use global keywords and include external configurations to streamline your processes. This article dives into the specifics that can make or break your pipeline setup.
- →Utilize global keywords to configure pipeline behavior effectively.
- →Include external YAML files to modularize and simplify your CI/CD configuration.
Securing Your Git Push Pipeline Against CVE-2026-3854
A critical remote code execution vulnerability has been identified in the git push pipeline, and it’s crucial to act fast. This vulnerability exploits how user-supplied git push options are handled, allowing attackers to inject malicious metadata. Here’s what you need to know to secure your pipeline.
- →Upgrade to GitHub Enterprise Server 3.14.25 or later to mitigate CVE-2026-3854.
- →Understand how git push options can be exploited through insufficient metadata sanitization.
Deploy any app in seconds — no infrastructure config, no DevOps overhead. Instant deployments from GitHub, built-in databases, and automatic scaling.
Start deploying free →Get the daily digest
One email. 5 articles. Every morning.
No spam. Unsubscribe anytime.