We’ve recently been discussing the possibility of hosting a build environment for the PowerShell community. For those who are unfamiliar with the benefits, such an environment allows you to do things like:
- Automatically run a suite of tests when new code is checked into source control. These tests can be run on multiple operating systems or versions of PowerShell concurrently.
- Publish pass/fail information back to your source control repository for each tested commit.
- Automatically release code which passes your tests to repositories such as Chocolatey or PowerShellGet, etc.
However, such an environment would require some amount of cloud resources, and those cost money. The exact amount would depend on how often a build needs to run, but we’re estimating the costs will likely be somewhere in the range of two to six thousand dollars (US) per year. So, at this point, we’re looking for contributions to help us make this idea a reality. These contributions can come from companies or from individuals. We can accept payments via the PayPal “Donate Now!” button on this page, or if you prefer, we can accept payments by check as well. If desired, we can provide invoices for the donations. Unfortunately, for legal reasons, we’re not a non-profit entity (because we are in support of PowerShell, a commercial product). This means that donations for the community build server are not tax deductible.
In an upcoming article, I’ll go into more details about how this environment will work. What I can tell you right away is that it will be freely available for any open-source, PowerShell-related project, and that we will have build agents running PowerShell 2.0 through 5.0. Pester will be available for running tests on all of these agents, and we will also have the PowerShellGet module available if you want to automatically publish modules to that environment.