Skip to content

Latest commit

 

History

History
33 lines (24 loc) · 2.43 KB

demo.md

File metadata and controls

33 lines (24 loc) · 2.43 KB
Raw

Demo

Azure DevOps demo plan

  • Create a project.
  • Create a repo as a clone of public one (2 repos: infa and code).
  • Configure Variable Group (for Az connection info).
  • Deploy Infrastructure.
  • Build code.
  • Deploy code.

Comments

Prerequisites

The demo requires an organization to be already created in Azure DevOps. There should also be a personal access token configured. After that you should run the Connect-AzDOProject to initiate connection to the organization.

Create project

Project creation can be done with New-AzDOProject cmdlet (project functions page) or with configuration files (configuration files page). In the case of configuration file usage, repositories and variable groups are created from the same input file.

As soon as a project is created, context is switched to it. All of the cmdlets that are used further do not require (and do not accept) project reference and operate on current Azure DevOps context. To switch context use the Connect-AzDOProject cmdlet.

Create repository

Repository creation is done using New-AzDoRepository cmdlet. In the case of the demo, repositories are created from public repos source (cloned).

Full details can be found on repository functions page.

Configure Variable Group

Variable group should be created to store Azure connection information in secret variables. When you create a variable with the New-AzDOVariable -VariableGroupsName 'vargroupname' -Name 'var' -Value 'value' the var variable is added to the vargroupname variable group if it exists; a new variable group is created in the other case.

Full details can be found on variable groups functions page.

Deploy infrastructure

Multi-stage YAML declarative pipelines are used in the demo. As API capability for managing this kind of pipelines is limited at the moment of module creation, pipeline definition creation is done manually through the portal. It just requires to select the recently created repository and agree to use the pipeline declaration stored in it.

Build and deploy code

Multi-stage pipelines are used in the demo. Both build and deploy activities are configured as separate stages of a single pipeline, as well as promotin from one environment to another.