Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Build on PowerShell 7 #1328
Open
Build on PowerShell 7 #1328
Labels
Comments
|
There's no reason you could not add a task in sideload v7 in either build service using the release zip deployment method and invoking pwsh from the extracted directory. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It would be nice to start building Pester on PowerShell 7 as well to see if it is compatible and keep it that way. To achieve that we need to research on which build servers v7 is already available. Right now we are building on TravisCI (Linux and MacOS), on AppVeyor (PowerShell 4+) and AzureDevOps (PowerShell 2&3).
Not sure if the build task needs to run on all three platforms, but it would be nice.
The change should apply to Pester v4, and then be adopted for v5 as well.