Az400 v8 - GitVERSION | Microsoft Certification AZ400 | git SEMANTIC Version |
Вставка
- Опубліковано 20 жов 2024
- Are you studying for Microsoft Certification AZ400? This is a must learn subject to clear the git questions.
What is semantic versioning and why should you care about GitVersion SEMANTIC versioning?
Calling the first version v1 and incrementing the number each time there is a code change works okay (v2, v3, v4, etc.). But there’s a better way that gives users and other developers more information about what to expect from the version. Exam Prep AZ-400: Microsoft Azure DevOps Solutions
Should you put thought into version numbering? What’s the best system for versioning? How to implement git version? In this video we'll cover git semantic versioning and how you can get git automatic version increment working with Azure DevOps?
Semantic Versioning, or SemVer, is a relatively new specification for how to number software releases, which uses three numbers (e.g. 1.2.6) instead of two (e.g. 1.2). It is being used by more and more open source projects and now in enterprises. This video walks you through the numbering system so you can understand how to read and apply the version numbers correctly, along with understanding why more projects are adopting it. We'll cover how to use the GitVersion utility that automatically injects version information as part of the build process.
We'll go deeper into how to tag your Git Releases and automate the end to end prorcess using the free open source utility called GitVersion with Azure DevOps CICD Pipelines.
Being a DevOps Engineer on the Microsoft platform is a trending role that encompasses managing development teams, managing source code, automating builds, tests, packaging, versioning, and deployments. Typically a DevOps engineer is concerned with two pipelines: a continuous integration (CI) and a continuous delivery (CD). These two pipelines encompass code planning building and test for CI, and release, deploy, operations and monitoring for CD. Becoming certified verifies and validates these skills, and indicates a certain level of expertise in this technology. To pass this exam there are many Azure capabilities and tools that must be mastered. Come find out which ones they are.
=================
AzureDevOpsTv: bit.ly/azurede...
Instagram: / iworldtrave. .
Twitter: / arora_tarun
==================
AZ-400 Study Areas Weights
Implement DevOps Development Processes 20-25%
Implement Continuous Integration 10-15%
Implement Continuous Delivery 10-15%
Implement Dependency Management 5 -10%
Implement Application Infrastructure 15-20%
Implement Continuous Feedback 10-15%
Design a DevOps Strategy 20-25%
==================
Video Tags
#FreeDevOpsTraining #LearnDevOps #Az400Training #Az400Cours #AzureDevOps #CICD #MicrosoftCertification #Git #AzureDevOps #GitHub #DevOpsTools #DevOpsTraining #DevOpsTutorial #DevOpsGit #Git #GitHub #GitTutorial #GitTutorialforBeginners #GitRebase #GitAdd #GitBranching #GitMerge #GitBash #GitCommit #GitClone #GitCommands #GitCheckout #GitConfig #SourceControl #VersionControl #gitterminal #git #gitcommands #gitcommandline #gitdotnetcli #gittutuorial
==================
Keywords
how do git branches work, how git branches work, what is git branch, what is git branching strategy, git branch behind master, git branch strategy for agile, devops gitlab, devops github, devops gitlab tutorial, devops git tutorial, devops git tutorial for beginners, devops git branching strategy, devops gitflow, devops git jenkins, devops git interview questions, devops git training, devops git repository, devops git tutorial point, azure devops git branching strategy, devops git commands, edureka devops git,
devops and git workflow explained crash course, azure devops git flow,
git for devops, git flow devops, azure devops git pull request, azure devops git repo tutorial, azure devops git repo, devops - git session, azure devops git visual studio, devopsschool git, azure devops git tutorial, git devops in telugu, git devops tool tutorial, devops git visual studio, vscode azure devops git, git with azure devops, microsoft azure devops certification, microsoft devops certification, microsoft certification 2020, microsoft certification path, microsoft certification training, microsoft certification exam, microsoft certification path 2020, microsoft certification azure, microsoft certification at home, microsoft azure certification az-900,
microsoft certification courses 2020, microsoft developer certification, microsoft azure developer certification, microsoft certification for developers, evops certification training, devops complete training videos, devops certification training edureka, cisco devops training, devops chef training videos, durgasoft devops training, devops training edureka, devops training for free, devops training free online, python for devops training, devops hands on training, devops training in telugu
![[UA] NAVI vs MOUZ | BO5 | IEM Rio 2024](http://i.ytimg.com/vi/CMBYk0cbGoA/mqdefault.jpg)
Checkout the full playlist of Azure Certification videos here, bit.ly/azuredevopstv
There is a lot of confusion in his video. He prepared for release 1.1. But got an error saying 1.1 tags exist. So he jumps directly into 1.2 tags. Why did you do tag in the release branch?(tag strategy). One more question why are you using develop branch as a feature branch? The final version which is produced on the master build is wrong. Kindly let me know your thought on these.
Why was your last version number 1.0.1 when the entire time you were targeting making a 1.1.0 from release? To me it looks like this didn't work, that was not the version number we expected.
Yes Colin I agree with you. I would expect the Version of the last tag 1.2.0!
Thanks for flagging this, I’ll review it and come back
Yea after releasing and merging to master, the tag shouldve been 1.1.0
Time to find and fix the mistake in the video. This is good information, but we can't follow it if it is wrong.
Thanks Steven, appreciate the feedback. I'll review this shortly.
At first I was a little confused but in the end I was even more confused, I think it is not the best approach to explain GitVersion
Very good !! Waiting for part 2 to publish the packages.
Thanks, I am glad you like it. Will be uploading the next videos in the series shortly
The way you started your video is clear and nice but the way you ended it was not clear. The release tag & the build of master was 1.0.2 after merging the release with the master. Your video would have been of high importance if you have fixed that last issue. I don't see you posted any clarification on this! Anyways, thanks.
does it work only with .NET applications?
niceeeeee!
What recording tool you used for these sessions? Audio and Video quality is really good. Loved your presentation.
I use camtesia for the video recording. I use apple pods for the audio. I use Mac Book pro to record my demos. The background music is the free beats from UA-cam. I am glad you like the setup.
I like your video a lot clear and concise, However, It seems to me you are mixing Git flow with Github Flow.? As you are not creating features off of master?, you are confusing develop with a feature branch .. git flow uses master as production the branch and develop for continuous integration. With git flow I understood it to be feature branch development off of the develop branch and then using a release branch/tag of combined completed features from a point in time from develop branch? Once the release is successful this get merges into your "source of truth " master branch.Please correct me if that is wrong though.
How the build got created in the development branch automatically when you create a release branch from the development branch ?? its in 8:23 minute