We recently shed a light on how you can easily use additional build tools on MyGet Build Services. However, there is more. A lot more!
We always say how much we love our users and this blog post is yet another illustration why we do. One of our users, Peter Rekdal Sunde, created an awesome PowerShell utility pack to make it even easier to customize your MyGet Build Services experience. The result is a complete build suite for creating NuGet packages and interacting with the MyGet Build Services environment. The scripts not only work on MyGet but also on your local development computer (you do need to have msysgit installed though). The entire code base was generously opensourced (MIT license) and is available on GitHub: https://github.com/peters/myget.
How does it work?
Simply include the myget.include.ps1 script in your build.ps1 on MyGet and use the provided functions.
Where do I begin?
To illustrate its purpose, we provide you a glimpse at some of the functionality provided by these scripts:
Build agent communication
- MyGet-Write-Diagnostic - writes a diagnostic message to the standard output
- MyGet-Build-Success - report build success
- MyGet-Die - report build failure
NuGet utility functions
- MyGet-NuGetExe-Path - path to NuGet.exe
- MyGet-NuGet-Get-PackagesPath - returns the value of the repositoryPath attribute in nuget.config for a given project folder
- MyGet-Build-Bootstrap - starts a build (including NuGet package restore)
- MyGet-Build-Solution - starts a build of a solution file
- MyGet-Build-Project - starts a build of a project file
- MyGet-Build-Nupkg - creates a NuGet package based on a specified .nuspec file. The .nuspec can contain additional replacement tokens, taking benefit from some of the variables provided by default by MyGet Build Services. More information at https://github.com/peters/myget#nuspec-substitutions.
- MyGet-TestRunner-Nunit - invoke NUnit
- MyGet-TestRunner-Xunit - invoke XUnit