The purpose of this library is to provide Azure DevOps pipeline administrators with a way to define and maintain both Build and Release Definitions with YML files for configuration/infrastructure as code.
- PowerShellGet
- Microsoft Account
- Azure DevOps Account
- Azure DevOps Project
2 Guides Available: Module Only or Full Project)
These instructions will get you an updated copy of the module downloaded to your local machine and walk you through creating your first YML Build and Release Definitions!
Install the latest version of the module from the PowerShell Gallery:
Install-Module PipelinesAsCode
Once you've installed this module to your local system you should be able to use the functions and commandlets provided:
Import-Module PipelinesAsCode
Get-Command -Module PipelinesAsCode
These instructions will get you a copy of the project up and running on your local machine for development and testing purposes. See Module Only section for notes on how to use the module on a live system.
Step by step instructions for how to install this project and the required dependencies to your local machine
Install the latest version of the module from the PowerShell Gallery:
Install-Module PipelinesAsCode
Install Pester for running PowerShell unit tests from the PowerShell Gallery:
Install-Module Pester
Once you've installed these modules to your local system you should be able to use the functions and commandlets provided:
Import-Module Pester, PipelinesAsCode
Get-Command -Module Pester, PipelinesAsCode
Once you have the project and Pester module installed, open PowerShell and navigate to the project directory:
Set-Location $HOME/source/repos/PipelinesAsCode
Once you have the test scripts pointed at your AzureDevOps instance you can go ahead and run the tests using Pester:
Invoke-Pester .\PipelinesAsCode.Tests.ps1
- Codecov.io - Code Coverage
- Codacy - Code Quality
- YamlDotNet - .NET library to help convert YML to PowerShell objects
Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us.
We use SemVer for versioning. For the versions available, see the tags on this repository.
- Nathan Duff - NateDuff