Don’t Stop at the PowerShell Pipeline. Build a CI/CD Pipeline for your PowerShell
summary
Builds a real CI/CD pipeline that takes a PowerShell module from a local repo to the PowerShell Gallery using GitHub Actions, running ScriptAnalyzer linting, Pester unit and module tests, and an automated publish step wired to a repo secret (PowerShell Gallery API key). Demo shows renaming the Source folder to the module name, bumping the version (example goes to 1.0.3), and successful publish with a 5–10 minute gallery delay.
AI-written summary · about
chapters (11)
- 0:00PowerShell CI/CD pipelines
- 1:50Prerequisites and setup
- 4:42Module structure best practices
- 13:30GitHub repository setup
- 17:44API keys for PowerShell Gallery
- 21:14GitHub Actions workflows
- 28:06Setting up GitHub Actions for validation
- 30:14Validation on feature branch
- 33:46Merge and deploy
- 36:14Deploy to PowerShell Gallery
- 39:50Q&A
related talks
01h 11mFree Continuous Delivery to the PowerShell Gallery with Azure DevOps
45mGitHub Actions for Fun and Profit
51mPowerShell module toolbox and templates for Continuous Delivery
01h 27mEverything On-Prem: From Git to Gallery with Open Source
50mGet control of you Git: Managing PS module binaries using VSTS CI/CD and...
49mPowerShell in CI/CD Pipelines: A Practical...
01h 29mModularizing PowerShell: Making Code Portable
44mSipping psake: Creating a Build and Release Pipeline for ...