1. Introduction
Azure DevOps Server 2019 is an upgraded version of Microsoft's original TFS. It is also a version that supports local offline development. It corresponds to an online cloud hosting version of Azure DevOps Service 2019.
Azure DevOps provides developer services to support teams to plan work, collaborate on code development, and build and deploy applications. Azure DevOps supports a culture and a set of processes that bring together developers, project managers, and contributors to complete software development. It allows organizations to create and improve products faster than traditional software development methods.
Its content management organization method is to first create a team project collection in the Azure DevOps Server management console, and then create multiple projects in the project collection and manage them separately
2. Create a project collection
Create a team project collection in the server-side Azure DevOps Server management console
After clicking Create Collection, follow the wizard prompts to complete the settings step by step. After the collection is created, the administrator who can manage this collection in the group membership can be added after adding the corresponding user. The default is administrator.
3. Create project and initialize repos
Access the URL of Azure DevOps Server, log in as a collection administrator to create a project, use git for version control by default, or choose TFS. You can also select a work item process.
After the project is created, enter Repos, click Initialize, and initialize the code base.
After the project initialization is completed, you can clone this library in VisualStudio, and you can submit and push after adding files. The basic usage is similar to the git command.
4. Use Pipelines
1. Generate
The work of generating code needs to be completed by a specific machine, and the machine for generating code needs to be registered in the project agent pool first.
Multiple agent pools on multiple machines can be registered for the generation of multiple branch versions.
Then create a new generation pipeline. According to the wizard, select the code source, proxy source, and generated job in order to complete the generation configuration.
Turn on continuous integration in the trigger, and the generation job can be automatically triggered after the completion is submitted.
2. Release
In order to publish the generated code to the target server, the deployment server needs to be registered first.
Click the deployment group under Pipelines, select New Deployment Group, and register the target machine.
You can register a windows machine or a Linux one.
After the deployment group is registered, you can create a new release. According to the type of application, select the corresponding template, or start from an empty job and create it manually.
Turn on the continuous deployment trigger, then you can automatically and continuously publish
Depending on your network and hardware environment, the changes submitted by members will be automatically deployed to the target server or even the production environment in a few minutes. The real one-button triple! As coders, we only need to build our own parts on the assembly line.
5. Assign work to members
1. In the project overview, invite project members
2. Create work items in the work items or boards under Borads and assign them to specific members
In the query, you can query the statistical work results, and easily manage many small partners.
6. Reference documents
https://docs.microsoft.com/en-us/azure/devops/organizations/projects/create-project?view=azure-devops-2019&tabs=preview-page
https://docs.microsoft.com/en-us/azure/devops/pipelines/create-first-pipeline?view=azure-devops-2019&tabs=net%2Ctfs-2018-2%2Cbrowser