GitLab for complex CI/CD: Robust, visible pipelines - Evening Session

In this webcast, GitLab Solutions Architect Manager, Joel Krooswyk goes over how you can uplevel your CI/CD experience with improved pipeline visibility, local package registries, and enhanced Kubernetes interaction.
Register for part 3 of this series: about.gitlab.com/webcast/gitl...
Watch part 1 of this series: about.gitlab.com/webcast/gitl...
Subscribe to hear about upcoming webcasts: bit.ly/2LtnePY
Read more about our product vision: bit.ly/2IyXDOX
Learn about FOSS & GitLab: bit.ly/2KegFjx
Get in touch with Sales: bit.ly/2IygR7z

[@user-vz8bd3gx4g]

Awesome! Thank you for the video, so authentic with professional input

[@ayencoscolfield3312]

Awesome! content just stumbled on your channel and i love and appreciate what am seen this is a good tutorial video that talks a lot about Gitlab used most in most companies at the enterprise level unlike Git and GIthub that open source and not popular in most companies

[@kavacham222]

Hi , when we build and push it to Acr evrytime a new tag must me added ,other than ci_pipeline_iid, wat is the other way to get a new tag everytime we build and push image.

[@balan7442]

Hello Joel, Thanks for your video, here i would like check with you that, how do we handle the pipeline execution based on branch names like release-1.1.0 or hotfix-1.0.0 along with develop and master branches. For these branches it may vary the deployment to different environments (SIT-develop, UAT-release, PROD-master and hotfix-emergency). how the .gitlab-ci.yml file look like. Pls suggest. Appreciate your support. only: variables: - $CI_COMMIT_REF_NAME == 'develop' - $DEPLOY_SANDBOX_ON_EVERY_COMMIT == 'true'