Thanks. Many years ago I used Jenkins but I didn't want to install it on my Azure VM so I started writing a PowerShell script on my VM to: - connect to my repo - pull code - move the built files to IIS directory Problem is I had to build my projects locally first and include them in source so I started thinking I can install MSBuild and Node on my VM and use the PowerShell to build my dotnet and Node project. Then I remembered Azure DevOps and found this... Thanks a lot. This worked first time for me.
my problem with pipelines is the stages and tasks , there is no stable rules , everyone reference to projects like they want , put them in variables or references to everything that contains .csproj for example , i will say that the problem is more with configurations standards than understanding what are pipelines used for , i hope some of you will get what i’m saying , btw thank you your courses are incredible
Amazing. Can you also do the same for Golang, Python, nodejs applications nobody did those by one RU-vidr if you can awaiting and useful content. Thank a lot Sir
@@RoundTheCode can you show us a Yaml pipeline from scratch for building a .net app and delivery of the app Yaml pipeline. And using docker file to build the image and push to acr
Thanks for the video. I see that you had put the trigger to none. What would be the code for trigger if we have any check in each and every time in our code ? The build pipelines will be created each and every time dynamically and executes it ?
learn.microsoft.com/en-us/azure/devops/pipelines/process/pipeline-triggers?view=azure-devops - This has some info. You can specify which branches to trigger against.
Okay so I followed this to the letter. The only thing I changed was the vmImage is ubuntu-latest in my case. I also updated the variables to match my .sln and .csproj files, however I am not seeing any artifacts being created. When it gets to the "Publish build artifacts" step I see an error stating ##[warning]Directory '/home/vsts/work/1/a' is empty. Nothing will be added to build artifact 'AzureTestProject'. I have been banging my head against a wall trying to get this to work every day all week now. Any tips would be super appreciated. I will buy you a beer right now
They are set in the YAML file under the variables. There is also a place to do it in Azure DevOps which is benefical if you are inputting sensitive information that you don't want in your repo.
Hi Being Random, Publish goes ahead and publishes the .NET application. Whereas, Publish Build Artifacts publishes the files to an Azure Artifacts file that can be used later on for deployment.
Hi there, I've been trying to recreate and run this pipeline but am facing errors. The one error I keep getting is: Dotnet command failed with non-zero exit code on the following projects : D:\a\1\s\RoundTheCode.AzureTestProject.sln. This error pops up in the Test task. I've emulated what you've done and also referred to the updated changes on Github. Are you able to help?
Yes, the solution filepath is incorrect. It should be this if you are using my example as it is: D:\a\1\s\RoundTheCode.AzureTestProject\RoundTheCode.AzureTestProject.csproj. When running the tests, check that inputs:projects is referencing the correct solution path.
Hi kubritish, The publish task builds the app before publishing it, so there is no need to add a separate build task. If the build fails, the publish task fails. Hope that answers your question.
