PowerShell module build helper functions.

Minimum PowerShell version


Installation Options

Copy and Paste the following command to install this package using PowerShellGet More Info

Install-Module -Name PSModuleBuildHelper -RequiredVersion 0.2.0

You can deploy this package directly to Azure Automation. Note that deploying packages with dependencies will deploy all the dependencies to Azure Automation. Learn More

Manually download the .nupkg file to your system's default download location. Note that the file won't be unpacked, and won't include any dependencies. Learn More


Paul Broadwith


(c) 2018 Paul Broadwith

Package Details



build invoke-build module helper testing


Get-BuildEnvironment Get-BuildItem Get-BuildOperatingSystemDetail Get-BuildPowerShellDetail Get-BuildReleaseNote Get-BuildScript Get-BuildSystem Get-BuildSystemEnvironment Get-ChangelogVersion Get-FunctionParameter Get-GitBranchName Get-GitChange Get-GitLastCommitHash Get-GitLastCommitMessage Get-ManifestVersion Get-NextReleaseVersion Get-PowerShellGalleryVersion Get-ProjectEnvironment Get-ProjectRoot Get-ReleaseType Get-SourcePath Get-TestEnvironment Hide-SensitiveData Initialize-BuildDependency Initialize-TestEnvironment Install-ChocolateyPackage Install-DependentModule New-GitHubRelease


This module has no dependencies.

Release Notes

v0.2.0 21 April 2018
* Changed the logic of release notes being used - only use them if nothing is in the ReleaseNotes field of the manifest and then use the release notes from the changelog or if we can't extract them use the URL to the changelog itself;
* The Initialize-TestEnvironment function now loads the module being tested into the Global scope. This was to get around the issue of it being loaded inside this modules' scope;
* Removed required module 'Configuration';
* Added required module 'PowerShellGet';
* Renamed 'buildoutput' folder to 'releases';
* Fixed issue with Initialize-TestEnvironment function which was showing errors trying to remove the module being tested when it hadn't been loaded;
* Added option to add content to the top and bottom of the module script. This is done using the ModuleScript.Header and ModuleScript.Footer properties in the build configuration file. These values must be strings but can be a multi-line script (ie. @"<CONTENT>"@);
* Rewrote Get-BuildReleaseNote function as the regular expression didn't always work as I wanted. The function now looks a bit clunky but it works;


Version History

Version Downloads Last updated
0.3.1 566 7/9/2018
0.3.0 41 4/23/2018
0.2.0 (current version) 19 4/21/2018
0.1.0 21 4/8/2018
0.0.2 15 4/5/2018
0.0.1 16 4/5/2018
Show more