Mohamed Radwan is a Developer Technologies MVP formerly known as (ALM MVP), Mohamed is working as Principal DevOps and Agile Coach; his work focuses on providing solutions for the various roles involved in software development and delivery through Agile Methodologies and utilization of Azure DevOps/Cloud Tools & Technologies. He has huge passion for automation with 15+ years of professional experience spanning the different stages and phases of Software Development Lifecycle. he has helped various customers around the globe in the UK, Denmark, USA, France, Egypt, Oman, KSA, Kuwait, and Libya, amongst others.
31:29 You see everything is great in this video but I am not understanding one thing. I would really appreciate if you could please explain. My question is why did you merge the code from feature branch to master without first testing it in the UAT environment. This is opposite for me. I was thinking you will show the automated mechanism to first merge the dev code to "UAT" branch, then deploy it in UAT env for testing purposes. Once the testing is successful, the code from UAT branch will be merged into Master branch and from there it will be deployed into production. But you first merged the Dev code into master without verification (UAT). Now if the UAT fails your master is no more good and is not representative of the prod. Can you please explain why my thought process is wrong? Thank you!
Hello, I was looking at your video channel. We may be helping a company that uses secure images to increase supply chain security and help cloud native development. Would you be willing to help try their software, make a video, and help show devs how to use their tools? This is not an offer, but just to start a conversation about your willingness to take on sponsorship. Please provide me with your email if you are interested. You'd have a chance to look at their technology and decide if it's the type of software that you'd be interested in covering in your channel.
This information is very informative and has been incredibly helpful, especially due to its hands-on nature. Instead of creating a single resource group for all three environments (dev, UAT, and prod), I believe it is more practical to create separate resource groups for each environment. This approach better separates the environments. What do you think?
Thankyou @Mohamed. However, during these steps after updating the webapp.yml when i go to pipelines i am only seeing Ansible-CI-YAML not Ansible-CI and if I run that "release" option in pipeline is not showing. Can you help in this regard?
I have a problem with this tool. I need migrate only specific Feature and all childs, but I don't know how. Its possible? In azure devops Server 2022 between 2 collections
شكرا جزيلا بشمهندس محمد على المقابلة الرائعة دي، نصائح ذهبية لا تقدر بثمن ❤❤❤ انا شوفت الفيديو على فيسبوك لكن في جملة بسيطة مكنتش عارف أسمعها كويس وجيت أشوفها هنا من خلال ال Subtitles زعلان إني ماعرفتش وتابعت حضرتك من زمان، لكن الحمد لله على كل حال، كل شئ بميعاد 🙏
Fantastic walkthrough, helped a lot, thank you so much!! One thing I did need to do for the ci-cd.ps1 to run was under Use Latest PowerShell Version, was to choose Use PowerShell Core under the advanced option below. Otherwise it didn't like the format of the script.
Thank you for the detailed steps. I was able to follow and deploy an app. However mhc-front pod is going into Crashloopback off state. Is the MHC application code still up to date or need any changes..
Hi Mohamed, I have follwed the same setps which you explied in the video. I'm getting below error while running the pipeline. Please help me out in this. Error: 2023-11-03T06:31:42.8563878Z ##[error]Could not find the modules: 'Az.Accounts' with Version: ''. If the module was recently installed, retry after restarting the Azure Pipelines task agent. 2023-11-03T06:31:42.9672510Z ##[error]PowerShell exited with code '1'. 2023-11-03T06:31:45.6177222Z ##[command]Disconnect-AzureRmAccount -Scope Process -ErrorAction Stop 2023-11-03T06:31:45.7413326Z ##[warning]Run Connect-AzureRmAccount to login.
Thank you so much for this video! I cant find many tutorials on how to migrate work items using vsts so your video is truly a life saver. Again many many thanks!
i execute again and i get a problems in publish job in 2023, i thing the problemas is image agent, in the inital presentation is win17 now the minimal is win19
Hi Radwan, very nice and wonderful walkthrough of the topics. I have one query, It may be related to access/integration of ms excel. I configured azure pipeline agent on my machine to run in Interactive mode. I am running a UI Test to edit and save excel file. The test will mimic the same steps we do manually to save excel file. The steps are: open excel, enter some value in cell in the worksheet, click on file tab-->browse-->enter file name in save as window and click on save. I have Excel 2016 Desktop App installed and activated on agent machine. The excel is saving the file as Book1 (The default Name) instead of the name I provided in save as window.. Not sure why the issue. I can save the excel file manually with the same user. All folder and remote access permissions for excel app are configured in Component Services ( DCOM Config) for the user. Am i missing something over here or in the agent configuration. Thanks
This session was highly informative, focusing on maximizing productivity with Azure DevOps and Logic Apps. It included an introduction to Logic Apps, a live demonstration, and a Q&A session. Introduction to Logic App: (1:45) The session began with an introduction to Logic Apps, a platform that automates workflows and integrates with various systems. Some key points covered: Logic Apps come with pre-built connectors for seamless integration with different applications. Key terms were explained: Workflow, Trigger, and Action. Demo Workflow with Animation: (4:39) Demo: (7:30) The demonstration showcased a real-world scenario where Logic Apps facilitated a two-way integration between an email support system and a private community support team. Here's how it worked: A community member sent an email to the support email, which triggered a Logic App workflow. This workflow created a ticket in Azure DevOps, filled with information from the email. An automatic reply with the ticket number was sent to the email sender. The support team received a notification in Microsoft Teams with ticket details. After resolving the ticket, the Logic App updated its status and notified the community member. The session also explained key Logic Apps terms and how it can integrate with various systems. Testing Logic Apps: (33:33) DevOps CoP and CoE: (45:15) Q & A: (48:09) As someone in technical support, I found this session valuable. It provided insights into the behind-the-scenes processes when handling support tickets. While my workplace uses a different environment and workflow, the core concepts remain applicable. Thanks to Eng. Rehab and Eng. Radwan for their informative presentation.
There's a slight mistake in the values for Start and Stop Trigger. In the Video Mohamed sets the delete deployment flag to true for clean Resources and Start Trigger. But you also need to set the predeployment flag to false for it to start the triggers again as this is the flag to distinguish between pre and post deployment.
