If you’re working in a regulated industry or have privacy concerns, keeping your code on your own servers might be the best choice. Luckily, Azure DevOps Server makes this possible, offering many of the same features as the cloud version but hosted locally on your hardware.

What Is Azure DevOps Server and Why Use It?

Azure DevOps Server is Microsoft’s on-premises version of its popular DevOps platform. It used to be called Team Foundation Server (TFS), but now it’s rebranded and aligned with the cloud service, Azure DevOps. If you’re already using TFS 2015 or later, upgrading to the latest Azure DevOps Server might be a smart move, especially since older versions aren’t supported anymore and won’t get security updates.

This server supports continuous integration and continuous delivery (CI/CD), just like the cloud platform. It works seamlessly with Visual Studio, letting developers build, test, and deploy code without needing to connect to the internet constantly. The main idea is to give teams full control over their development environment while staying current with modern development practices.

Choosing and Setting Up Azure DevOps Server

There are two main ways to set up Azure DevOps Server: as a single server or across multiple servers in a cluster. The single-server setup is best for small projects or solo developers. For larger teams or organizations that need a more reliable, scalable system, a multi-server cluster is recommended. Microsoft suggests at least 8 cores, 16GB of RAM, and SSD storage for a basic setup. If you want to add Elastic Search for better code search, you’ll need an extra CPU and 8GB more RAM.

The server relies on SQL Server for its database. You can start with the free Express edition if you’re working alone or with a small team. Larger organizations should plan to upgrade to SQL Server Standard or Enterprise editions. The latest Azure DevOps Server requires Windows Server 2022, ensuring compatibility with modern hardware and security features.

Installing and Managing Your On-Premises DevOps Environment

Installing Azure DevOps Server is straightforward, thanks to a wizard-driven setup process. It guides you step-by-step, checking that all services are correctly configured. You can choose between different setup options: Basic for quick installs, Advanced for more control, or Azure if you want to connect to cloud services. Once installed, you set up user accounts, groups, and roles, especially if you’re using Active Directory to manage access.

It’s best to create dedicated groups for different roles: one for most users with broad access, another for project managers and architects, and a restricted group for contractors or staff who only need limited access. This setup helps keep your development environment secure and well-organized.

Projects are at the core of Azure DevOps Server. They act as hubs where teams plan work, collaborate on code, and track progress. Similar to GitHub, projects feature Kanban boards for task management and a central code repository. The server also hosts CI/CD pipelines, which automate building, testing, and deploying your code, making software delivery faster and more reliable.

Managing Pipelines with YAML and Local Editors

Pipeline definitions are now mostly created using YAML files, which are stored alongside your code. This makes it easy to version control your build and deployment processes. Microsoft has introduced a new YAML editor, replacing the older visual designer, with features like code completion and validation to help you create error-free pipelines.

This editor is browser-based and based on the same engine as Visual Studio Code, offering a familiar experience. You can also download your YAML files and edit them locally if you prefer. Pipelines can be cloned to reuse configurations across different projects, saving time and ensuring consistency. However, secrets and variables won’t carry over and need to be set up again for each pipeline.

Overall, Azure DevOps Server provides a robust way to keep your development pipeline on your own terms. It bridges the gap between cloud convenience and the security and control of on-premises infrastructure. Whether you’re a small team or a large organization, it offers flexible options to fit your needs while supporting modern DevOps practices.

Inspired by

• https://www.infoworld.com/article/4081313/run-azure-devops-on-premises.html

Sources

• gmpg.org
• csoonline.com
• podigee.com
• podigee.com