|
May 12, 2021 - 11:36 PM OrangeWeaf - i.ng.a.ga.g.a.2.2.2@gmail.com <b>Eduard Kabrinskiy - Vsts continuous integration - Кабринский Рдуард <h1>Vsts continuous integration</h1> <p><youtube></p> Vsts continuous integration <a href="http://remmont.com">Top news stories</a> Vsts continuous integration <h1>VSTS for Beginners: Improve Quality With Continuous Integration in 3 Easy Steps</h1> <h3>Take a look at how to make use of VSTS to easily set up a continuous integration pipeline for your next ASP.NET Core project.</h3> <p>Join the DZone community and get the full member experience.</p> <p>In this blog post, we're going to configure a <strong>build process</strong> in <strong>VSTS</strong> to enable continuous integration for our ASP.Net Core example web-app.</p> <p><strong>Continuous integration</strong> is a powerful technique to prevent merge-hell and improve quality on the "left" stages of our software production process. In the fast-paced world of development, we want to merge into the main line of development the new developed features as soon as possible to avoid open branches that will cause painful merges. If we keep our unit of work small and focused we'll have great benefits.</p> <p>In this tutorial, we'll start from scratch creating a new .NET core 2 web app and then we configure VSTS.</p> <p>(If you have a working project, you can jump to the second step.)</p> <h2>1. Create a .NET Core Web App</h2> <p>We open a PowerShell command line and create a new folder for our project. For this example I'll use the name <em>Parrish</em> (the shoes company from the movie Jumanji).</p> <p>And then we turn this into a git repository:</p> <p>We add a <em>gitignore</em> file into the root of the repository to commit into git only the meaningful files. We can use this one.</p> <p>Now we create a standard .NET Core MVC project with the PowerShell command line:</p> <p>Then we open the project with Visual Studio and hit F5. We can see the web app up and running.</p> <p sty... IP : 134.249.209.60 |