Join us

ContentUpdates and recent posts about GitLab CI/CD..
 Activity
@shrikantshire started using GitLab CI/CD , 4 years ago.
 Activity
@vsk1t started using GitLab CI/CD , 4 years, 1 month ago.
 Activity
@ibrahim started using GitLab CI/CD , 4 years, 1 month ago.
 Activity
@mr_khetwal started using GitLab CI/CD , 4 years, 1 month ago.
Story
@corewide shared a post, 4 years, 1 month ago
Marketing Team Lead, Corewide

Securing a Container: How to Clean Up Docker Images and Why Limit Runtimes

Docker GitLab CI/CD

Containers have rocked the software engineering world not less than DevOps practices. Containers are fantastic — deployable everywhere, they let you run previously incompatible setups on the same servers and move projects between servers smoothly. However, there’s always a price to pay — container environments require an understanding of core fundamentals to run containers securely.

1_Ay1lCjSiFYUR7gGjYxeQYg.png
 Activity
@floraaviss started using GitLab CI/CD , 4 years, 1 month ago.
 Activity
@manishvenkat16 started using GitLab CI/CD , 4 years, 2 months ago.
 Activity
@siri143mahi started using GitLab CI/CD , 4 years, 2 months ago.
 Activity
@sudhagar started using GitLab CI/CD , 4 years, 2 months ago.
 Activity
@anirban_das started using GitLab CI/CD , 4 years, 2 months ago.
GitLab CI/CD is a native CI/CD system that runs directly within the GitLab platform to automate building, testing, and deploying software. Pipelines are defined declaratively using a .gitlab-ci.yml file stored alongside the source code, enabling versioned and reproducible workflows. It supports runners executed on shared or self-managed infrastructure, parallel jobs, caching, artifacts, environments, and deployment strategies. GitLab CI/CD is used by development and DevOps teams to implement end-to-end automation tightly coupled with source control, issues, and security features.