Tool / Module Name
BuildHelpers
Source Repository URL
https://github.com/RamblingCookieMonster/BuildHelpers
PowerShell Gallery URL
https://www.powershellgallery.com/packages/BuildHelpers
Current License
MIT
Your relationship to this tool
I am a contributor (not current maintainer)
What does this tool do?
PowerShell helper functions that normalize CI/CD build variables (branch name, build number, commit hash, etc.) across build systems — AppVeyor, TeamCity, Azure Pipelines, GitHub Actions, Jenkins — so build scripts don't need system-specific conditional logic. It also includes utilities for module manifest management (Set-ModuleFunction, Update-Metadata), semantic version stepping (Step-Version, Step-ModuleVersion), git helpers (Invoke-Git, Get-GitChangedFile), and release helpers (Publish-GithubRelease, Set-ShieldsIoBadge). It's commonly used as a building block inside other PowerShell build/CI frameworks rather than as a standalone end-user tool.
Current state of the project
- Last GitHub commit: 2023-08-11 (repo is not archived)
- Last PSGallery release: v2.0.16, published 2020-12-18 — 89 versions released total since the first in 2016, but release cadence stopped in Dec 2020 even though GitHub commits continued for roughly three more years
- Open issues: 30
- Open PRs: 11, including several straightforward, already-written bugfixes awaiting merge/release (e.g. #130 deadlock fix when the last commit message exceeds 4096 bytes, #131 greedy-replace fix in
Set-ShieldsIoBadge)
- Known bugs: I checked open issue titles/bodies for security-related reports and found none. There are ordinary functional bugs in the backlog (e.g.
Get-ProjectName fails when a git alias exists, Set-BuildEnvironment fails when git isn't installed)
- Tests/CI: a Pester test suite exists (
Tests/BuildHelpers.Tests.ps1); CI is configured via AppVeyor only, no GitHub Actions workflow. I have not verified current build/pass status — that should be confirmed during onboarding
- Original author reachable and aware: yes — see Original Author Status below
Evidence of real-world use
866,833 all-time PSGallery downloads, 221 GitHub stars, 48 forks. It's used as a declared RequiredModules dependency by other established PowerShell community projects, including psake/PowerShellBuild, AtlassianPS/JiraAgilePS, KevinMarquette/KMT.ModuleBuilder, and devblackops/Stucco, among 20+ repos requiring it directly in their module manifests and 30+ repos referencing it in CI pipelines (AppVeyor, Azure Pipelines).
Original author status
Yes — author has been contacted and is supportive
Post-adoption maintainer commitment
Yes — I commit to at least 6 months of active maintenance
Who will serve as Steward for this project?
I will be the Steward
Named Steward details
N/A — I'm serving as Steward myself.
Additional notes
GitHub activity (commits, issue/PR engagement) continued for years after the last PSGallery release, suggesting the stall is about maintainer bandwidth rather than the tool being obsolete or unwanted. Migrating CI from AppVeyor to GitHub Actions is likely one of the first tasks post-adoption. Happy to assist with onboarding/knowledge transfer as Steward.
cc @HeyItsGilbert — flagging you here since you're familiar with this request.
Tool / Module Name
BuildHelpers
Source Repository URL
https://github.com/RamblingCookieMonster/BuildHelpers
PowerShell Gallery URL
https://www.powershellgallery.com/packages/BuildHelpers
Current License
MIT
Your relationship to this tool
I am a contributor (not current maintainer)
What does this tool do?
PowerShell helper functions that normalize CI/CD build variables (branch name, build number, commit hash, etc.) across build systems — AppVeyor, TeamCity, Azure Pipelines, GitHub Actions, Jenkins — so build scripts don't need system-specific conditional logic. It also includes utilities for module manifest management (
Set-ModuleFunction,Update-Metadata), semantic version stepping (Step-Version,Step-ModuleVersion), git helpers (Invoke-Git,Get-GitChangedFile), and release helpers (Publish-GithubRelease,Set-ShieldsIoBadge). It's commonly used as a building block inside other PowerShell build/CI frameworks rather than as a standalone end-user tool.Current state of the project
Set-ShieldsIoBadge)Get-ProjectNamefails when agitalias exists,Set-BuildEnvironmentfails when git isn't installed)Tests/BuildHelpers.Tests.ps1); CI is configured via AppVeyor only, no GitHub Actions workflow. I have not verified current build/pass status — that should be confirmed during onboardingEvidence of real-world use
866,833 all-time PSGallery downloads, 221 GitHub stars, 48 forks. It's used as a declared
RequiredModulesdependency by other established PowerShell community projects, includingpsake/PowerShellBuild,AtlassianPS/JiraAgilePS,KevinMarquette/KMT.ModuleBuilder, anddevblackops/Stucco, among 20+ repos requiring it directly in their module manifests and 30+ repos referencing it in CI pipelines (AppVeyor, Azure Pipelines).Original author status
Yes — author has been contacted and is supportive
Post-adoption maintainer commitment
Yes — I commit to at least 6 months of active maintenance
Who will serve as Steward for this project?
I will be the Steward
Named Steward details
N/A — I'm serving as Steward myself.
Additional notes
GitHub activity (commits, issue/PR engagement) continued for years after the last PSGallery release, suggesting the stall is about maintainer bandwidth rather than the tool being obsolete or unwanted. Migrating CI from AppVeyor to GitHub Actions is likely one of the first tasks post-adoption. Happy to assist with onboarding/knowledge transfer as Steward.
cc @HeyItsGilbert — flagging you here since you're familiar with this request.