Environments and Deployments
Part of the GitLab CI course
Your deploy job works. It runs scp or kubectl apply or an Ansible playbook, it goes green, and the new version is live. Then someone asks a question you cannot answer from the pipeline page: what is actually running on staging right now? Who put it there? Was it before or after Tuesday's change?
A pipeline records that a job ran. It does not record what state that job left the world in. GitLab's environment: keyword closes that gap: it turns a successful job into a deployment, a tracked record that a specific commit is now live in a specific place. ...
Want to learn GitLab CI Environments and Deployments in a real environment?
Click below, get a fresh Linux box with GitLab CI ready to go, and work through Environments and Deployments hands-on with an AI tutor that knows your code.
Start this lessonEnvironments and DeploymentsWhat you'll learn
- Environment keyword
- Environment name
- Environment url
- Deployment tracking
- Manual production deploy
- Dynamic environments
- Review apps concept
Read this lesson in your language
All lessons in this course
11 lessons- 1What Is CI/CD20 min
- 2Your First Pipeline25 min
- 3Jobs and Stages30 min
- 4Variables and Secrets30 min
- 5Artifacts and Caches30 min
- 6Rules and Conditional Jobs30 min
- 7Docker Jobs and Services35 min
- 8Environments and Deployments30 min
- 9Includes and Templates30 min
- 10Runners30 min
- 11Capstone: Build, Test, Deploy60 min
