build: stage: build-image image: docker:20.10.16 services: - docker:20.10.16-dind script: - docker login -u $CI_REGISTRY_USER -p $CI_REGISTRY_PASSWORD $CI_REGISTRY - docker build -t $IMAGE_TAG . - docker push $IMAGE_TAG only: - main
deploy: stage: deploy trigger: project: backend/infra branch: main strategy: depend You can trigger a pipeline via API with a token: automating devops with gitlab ci/cd pipelines read online
DevOps emerged to bridge the gap between development and operations. Its core philosophy is — automating builds, tests, deployments, and monitoring. Among the many CI/CD tools available today (Jenkins, CircleCI, GitHub Actions), GitLab CI/CD has emerged as a powerful, integrated, and scalable solution. Why? Because GitLab isn't just a Git repository manager. It's a complete DevOps platform with CI/CD built directly into the same application that hosts your code. build: stage: build-image image: docker:20
GitLab then shows a dashboard of deployments, and you can roll back from the UI. For secure cluster access, use the GitLab Agent instead of storing kubeconfig . Among the many CI/CD tools available today (Jenkins,
variables: DOCKER_REGISTRY: registry.gitlab.com APP_NAME: myapp job: script: - docker build -t $DOCKER_REGISTRY/$APP_NAME .