-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
BREAKING CHANGE: xHyper-V renamed to HyperVDsc: Renamed all DSCResources, Examples, Modules and Tests where applicable #194
Conversation
@johlju while I've got your attention, idk if you saw this! |
Will look at it when I have some time. 😊 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 3 of 7 files at r1, 84 of 85 files at r2, 4 of 4 files at r3, all commit messages.
Reviewable status: all files reviewed, 3 unresolved discussions (waiting on @nickgw)
azure-pipelines.yml
line 178 at r3 (raw file):
pwsh: false - powershell: |
Just curious, is this necessary? It is not run for Win2022 integration tests. 🤔
Code quote:
- powershell: |
Set-Service -Name wuauserv -StartupType Manual -Verbose
Start-Service -name wuauserv -Verbose
build.yaml
line 54 at r3 (raw file):
- Publish_Release_To_GitHub - Publish_GitHub_Wiki_Content - Create_ChangeLog_GitHub_PR
This can be removed here there is a task in azure-pipelines.yml Deploy stage that runs this.
Code quote:
Create_ChangeLog_GitHub_PR
tests/Integration/DSC_VMDvdDrive_remove.config.ps1
line 1 at r3 (raw file):
configuration MSFT_VMDvdDrive_Remove_Config {
We should change to:
Suggestion:
DSC_
@nickgw just a few tiny comments. 🙂 |
I've updated the other two comments though. |
Okey then I think you can safely remove the task in azure-pipelines.yml in this repo as it was not used prior. Guessing that was needed in the other repo to run a certain test. |
Removed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 2 of 2 files at r4, 1 of 1 files at r5, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @nickgw)
build.yaml
line 51 at r3 (raw file):
publish: - publish_module_to_gallery
It was only the task Create_ChangeLog_GitHub_PR
that needed to be removed, it should look like this.
Suggestion:
publish:
- publish_module_to_gallery
- Publish_Release_To_GitHub
- Publish_GitHub_Wiki_Content
I updated pipeline files and added resource README files to enable Wiki documentation. |
@nickgw suggest you take |
You currently have the code coverage steps twice in the one in this PR. 🤔 So above suggestion might just be the easiest to fix it.. 🙂 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Reviewed 20 of 21 files at r6, 1 of 1 files at r8.
Reviewable status: all files reviewed (commit messages unreviewed), all discussions resolved (waiting on @nickgw)
@nickgw awesome work on this, thank you! I waiting for the API key then I merge this. |
Pull Request (PR) description
BREAKING CHANGE: xHyper-V renamed to HyperVDsc: Renamed all DSCResources, Examples, Modules and Tests where applicable
This Pull Request (PR) fixes the following issues
Task list
file CHANGELOG.md. Entry should say what was changed and how that
affects users (if applicable), and reference the issue being resolved
(if applicable).
and comment-based help.
This change is![Reviewable](https://camo.githubusercontent.com/23b05f5fb48215c989e92cc44cf6512512d083132bd3daf689867c8d9d386888/68747470733a2f2f72657669657761626c652e696f2f7265766965775f627574746f6e2e737667)