sampler-migration

To migrate a legacy PowerShell module to Sampler, inspect the existing project, restructure sources under the source/ directory, and configure build artifacts like build.ps1, GitVersion.yml, and azure-pipelines.yml. The process provides phased guidance for adapting your module to the Sampler build framework end-to-end.

Moving from AppVeyor, PSDepend, and PSDeploy to Sampler involves replacing them with ModuleBuilder, InvokeBuild, and GitVersion. This migration transitions your pipeline to Sampler's build framework, configuring build scripts and release pipelines for an end-to-end workflow.

Upgrading from Pester 4 to Pester 5 during a Sampler migration involves configuring your test setup within the new Sampler-based project structure. The migration provides best practices for setting up tests using Pester 5 alongside ModuleBuilder and InvokeBuild in your build pipeline.

Yes, the Sampler migration process is adaptable to teams setting up new Sampler-based modules. You can initialize a Sampler-based project structure, run the bootstrap script, and configure build.ps1, GitVersion.yml, and azure-pipelines.yml to establish a complete CI/CD pipeline.

Source restructuring for Sampler requires moving your existing module files under the source/ directory. This reorganization aligns with Sampler's expected project layout, enabling proper packaging, automated testing, and release pipeline configuration.

Yes, Sampler supports end-to-end pipeline configuration including GitHub releases and changelog generation. The migration guidance covers best practices for setting up packaging, changelog updates, and GitHub release automation within your azure-pipelines.yml workflow.