Learn how to use GitLab's Pipelines and Release Management tools to create a release from your normal development processes. See example code here: gitlab.com/Chr...
Absolute gold, buddy!!! Thanks Can you make a video on tagging docker containers appropriately. As of now, my cicd pipeline always makes an image with :latest tag. I would love it to match the relese tag on gitlab. How would you tackle it?
great video, but question about gitlab repos. is there a way youve found to automate the setup of your repos so that it is configured with all or at least some of the settings you have here? in the case you have multiple repos with similar apps/services/libraries you are developing on and want them to all follow the same release strategy, is there a way to automate so part of this process? thanks!
Hello, the release pipeline process didn't work for us because our developers not following the release process/they don't create a release branch. Else they created tags directly via console based on the latest commit id they pushed in the master branch. Any thoughts?
@@blackdiamondlearning Got it. Thank you! By the way, I like the idea of creating a release branch because it allows us to run force deploy, and then we can enforce developers to use semantic versioning for releases.
You said: "It should be main". I have to disagree here. It should not, it CAN be main or master. There's no technical reason to call it main other than just being a trend. My opinion as software engineer. Thank you for the video, everything else is a nice approach for automatic versioning.
I think he meant "it should be main" as new repository are created by default with main instead of master if I am not wrong. He meant more like, "you should be seeing main instead of master". That's my interpretation.
I have just implemented this as the release process - many thanks for this wonderful solution!
Absolutely brilliant…thank you
Thanks a lot buddy!
I would like to make some adjustments on our actual gitlab pipelines.
This is great!
Absolute gold, buddy!!! Thanks
Can you make a video on tagging docker containers appropriately. As of now, my cicd pipeline always makes an image with :latest tag. I would love it to match the relese tag on gitlab. How would you tackle it?
great video, but question about gitlab repos. is there a way youve found to automate the setup of your repos so that it is configured with all or at least some of the settings you have here? in the case you have multiple repos with similar apps/services/libraries you are developing on and want them to all follow the same release strategy, is there a way to automate so part of this process?
thanks!
Great Video. Many thanks
Thanks, bro !!!😀
Hello, the release pipeline process didn't work for us because our developers not following the release process/they don't create a release branch. Else they created tags directly via console based on the latest commit id they pushed in the master branch. Any thoughts?
This should be fine; You'll just need to change your pipeline triggers to trigger based on tags as opposed to branching!
@@blackdiamondlearning Got it. Thank you! By the way, I like the idea of creating a release branch because it allows us to run force deploy, and then we can enforce developers to use semantic versioning for releases.
You said: "It should be main". I have to disagree here. It should not, it CAN be main or master. There's no technical reason to call it main other than just being a trend. My opinion as software engineer. Thank you for the video, everything else is a nice approach for automatic versioning.
I think he meant "it should be main" as new repository are created by default with main instead of master if I am not wrong. He meant more like, "you should be seeing main instead of master". That's my interpretation.