In this article, I will be explaining more about continuous integration and how to apply it to your .NET Core projects using Azure Pipelines.
Related Articles
What is continuous integration?
Continuous Integration is a development practice that integrates the code into a shared repository each time a commit is pushed by any member of the development team. It makes an automated build and you may use tools to check your code, presenting problems as soon as they appear.
Why use continuous integration?
- Quicker integrations
- To have a solid repository
- Use unit tests to validate your business rules
- Catch problems as soon as they begin to be problems
- Increase project status visibility
- Make use of tools to check your code quality
What is Azure Pipelines?
"Azure Pipelines is a cloud service that you can use to build and test your code project automatically and make it available to other users. It works with just about any language or project type.
Azure Pipelines combines continuous integration (CI) and continuous delivery (CD) to constantly and consistently test and build your code and ship it to any target."
Why use Azure Pipelines?
- Accepted languages: Python, Java, PHP, Ruby, C#, and Go.
- Accepted application types: Java, JavaScript, Python, .NET, PHP, Go, XCode, and C++.
- Integrates with: GitHub, Azure Repos, Bitbucket, and Subversion.
- Accepted targets to deploy the code: container registries, virtual machines, Azure services, any on-premises or cloud target.
- Type of packages produced: NuGet, npm, Maven packages or you can use any other package management repository of your choice.
How to apply continuous integration to your .NET Core projects using Azure Pipelines?
Saravanakumar SekaranPosted Jan 1, 2019, 11:47 PM
Wow very nice article !!!!