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.
Refactor build to use PSPackageProject #273
Conversation
|
There's already a build file in src, can we merge the two files (either getting rid of that build file or the one in this repo)? |
|
@sdwheeler had opened a PR adding all the documentation files into 'docs'. Do these files explicitly need to be in a folder called 'docs' or is moving them to 'help' okay? |
Nevermind, just saw that you removed the other build script |
| pr: | ||
| branches: | ||
| include: | ||
| - master |
alerickson
Oct 5, 2020
Member
Is this setting up CI explicitly for the master branch? If so can we change this to development?
Is this setting up CI explicitly for the master branch? If so can we change this to development?
PaulHigin
Oct 5, 2020
Author
Collaborator
CI is not running yet, but when it does it will run on any selected branch. I am still working to get a project set up.
CI is not running yet, but when it does it will run on any selected branch. I am still working to get a project set up.
|
I updated the tests to work with Pester 4.x. I think we should standardize on this version as the rest of PowerShell/Module tests already do. There are a number of breaking changes in 5.x that make CI difficult. Also I temporarily disabled the older tests since they are not running successfully and also change machine state. I think they need to be reviewed. |
|
messed Paul about the one question I had and got a better understanding. The rest of the PR looks good to me :) |
This is the first build refactoring that arranges PowerShellGet to use PSPackageProject module for build/test/compliance/signing/publishing.
Files have been moved to their needed locations
The build script has been refactored to conform to PSPackageProject
CI yml files have been added but not fully changed for PowerShellGet and not yet tested
Cmldet help files have been moved to location that conforms with PSPackageProject