A couple of days ago Microsoft announced about the first RC of Azure DevOps Server 2019. The news is quite exciting, and I decided to dedicate one of the evenings to my review and dig a bit deeper using an empirical approach. The first reasonable question you may ask, what’s the point in having Azure DevOps if we still have TFS for the on-premise deployments that has roughly the same capabilities,
If you’re still using TFS, there are some benefits and reasons why you may need to migrate to Azure DevOps (formerly VSTS), which is a cloud version of TFS with the most recent features. One of the benefits you may consider is global availability, easy access for the external users, and the other benefits are access to the most recent features and potential savings on the infrastructure and
You may wonder, how Gulp tasks runner is related to DevOps? Well, the relation is direct. You may work on the Node application deployment that uses this framework. For such cases, you need to know whether the issue you face is related to deployment or development process. This topic is grounded on the issue I faced with the app deployment recently. We heavily use build agents and our build
This topic is all about .NET Core installation on Ubuntu Linux. If you need this framework to be installed on Linux for development or CI/CD automation (like me), keep reading :)
The trick is that installation steps are a bit different from what Microsoft suggests. It can't be installed using 'apt-get' and you'll have numerous errors during the process. More about the issue here. So, to make it
Intro
If you already know what Continuous Integration (CI) is, you might know the benefits of it as well. CI involves producing a clean build of the system several times a day, usually using CI/CD tools like Jenkins/VSTS/TFS/AppVeyor etc., and various source-control systems (GitHub/GitLab/BitBucket). Agile teams typically configure CI to include automated compilation, unit test execution, and
This topic is not supposed to explain CI/CD concepts; in reverse, it assumes you already know what these practices are. Visual Studio Team Services (VSTS) is a collection of hosted DevOps services for application developers. It helps to automate CI/CD processes, project tracking, store source code, etc. One of its essential functionalities is the build and release processes. To build your
Before talking about new stuff in C# and .NET Framework overall, it would be good to see how the platform evolved over the time (e.g. since the first release in 2002). A lot has been changed since, meaning that .NET became platform-agnostic and very mature platform for Enterprise-grade software development.
Figure 1. C# Language evolution
As you see from the scheme, every version brought
The beauty of Azure is that it has multiple ways to do the same thing. Imagine the scenario; you need to copy the database between subscriptions. Considering the SQL Server Import/Export procedure, you can do that either from the UI or use command line tools (like SQLPackage).
The way it works with Azure UI, you go to the SQL Server database you want to export, and you have an option available (
Imagine a situation where you have to manage multiple Azure subscriptions (that belong to different tenants), not only for your organization but also for your company’s clients. In the software development process, you can host VSTS (Visual Studio Team Services) on your organization’s Azure account and deploy to customers’ subscriptions (which is quite a widespread use case). Subscription
Containers galore
As you may see from the first part of this topic, a lot of stuff is going on around containers, containerization, and everything that relates to it. Fortunately, it wasn’t the only topic of the conference and continuing the story, and I’m going to talk about the other areas worth attention.
Microservices!
Yes, I know what you think – heard about/use it already, so what’s new?