Hi, is it possible to trigger stage and prod stages from some other branch e.g. rel/ or prod/ created from the main branch. Also, within these rel/ or prod/ directory would like to have a version number specific branch.. so whatever version is higher in prod/ should trigger production stage deployment. Those version branches within prod/ would help do quick fixes in production while dev deployment has many broken features in the master branch. So branch hierarchy would be prod/v1.0 prod/v1.1 prod/v2.0 etc.
Thank you for the awesome video. It would have been mind blowing if you could pay attention to your speed of speech and take some pause on each step and explain what is being done. Otherwise the approach and understanding delivers the message fine.
Rohit can you please answer that how the users are listed over there in the Org. setting in users tab? Did you integrate AAD with Azure Devops that's how you were able to add in the list or it is not mandatory to link AAD with Azure Devops
Hi , Is it possible to start triggers for UAT and PROD? in our case we have Dev, UAT and PROD instances, we are not running triggers on dev but we want triggers to be active in UAT and prod, when we push stuff dev to UAT and prod the triggers are set to pause because they were pause in dev, so is there any way to solve this issue?
@@RohitSharma6, if we create triggers only on uat and prod, then every time we create a release from dev to Uat and prod, it's gonna delete those triggers because those teiggers are not present in dev.
Simply Amazing! Thank you so much! Very well detailed and explained!👌👌
very nice explanation and understood very well !!
Thank You Very Much
cool, thank you
Very nice explanation
Hi, is it possible to trigger stage and prod stages from some other branch e.g. rel/ or prod/ created from the main branch. Also, within these rel/ or prod/ directory would like to have a version number specific branch.. so whatever version is higher in prod/ should trigger production stage deployment. Those version branches within prod/ would help do quick fixes in production while dev deployment has many broken features in the master branch. So branch hierarchy would be prod/v1.0 prod/v1.1 prod/v2.0 etc.
Looking for the same sort of solution, did you find anything on it further?
Thank you for the awesome video. It would have been mind blowing if you could pay attention to your speed of speech and take some pause on each step and explain what is being done. Otherwise the approach and understanding delivers the message fine.
Thank you for the suggestion Sandeep.
Thank you very much for this training, it really helped me. Is it possible to also make us a tutorial with Docker? Please please
It is possible
Rohit can you please answer that how the users are listed over there in the Org. setting in users tab? Did you integrate AAD with Azure Devops that's how you were able to add in the list or it is not mandatory to link AAD with Azure Devops
Adding from AAD is good way.
Hi , Is it possible to start triggers for UAT and PROD? in our case we have Dev, UAT and PROD instances, we are not running triggers on dev but we want triggers to be active in UAT and prod, when we push stuff dev to UAT and prod the triggers are set to pause because they were pause in dev, so is there any way to solve this issue?
If my understanding is correct you dont need any trigger for Dev. Just have it for UAT and Prod.
@@RohitSharma6, if we create triggers only on uat and prod, then every time we create a release from dev to Uat and prod, it's gonna delete those triggers because those teiggers are not present in dev.