Open
Conversation
Allows you to run New-PEBuild in an automated pipeline with no user interaction
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
New-PEBuild currently has no way of being run in an automated pipeline due to the way it uses Out-GridView to have the user select the PE Task.
We have a use case where we would like to automate the building of our PE image within a CI/CD pipeline.
This PR adds 2 optional params to New-PEBuild that solves this.
I've tried to stick with the style of the existing function and modelled the usage of TaskName and SkipGrid around how they are implemented in Import-OSMedia.