DevOps Articles

DevOps practices for PowerShell programming

Powershell is a powerful scripting language and I have seen a lot of developers and administrators miss out on all the goodness of DevOps practices such as versioning, test automation, artifact versioning, CI/CD, etc. In this blog, I’ll try to explain with a working example on how to program PowerShell (not just scripting) with a predetermined module structure, ensuring quality with unit tests and deliver code in a reliable and repeatable way using continuous integration and continuous delivery pipelines.

Standardization of Module design: When multiple people in a team work with PowerShell, it is paramount to have standards on how to develop PowerShell modules.

The release pipeline is responsible for promoting artifact (PowerShell module) from Dev to Test and then to Prod.

The release pipeline is responsible for promoting the view based on quality gates defined in the Dev and Test stage to the next view.