-
Notifications
You must be signed in to change notification settings - Fork 7.7k
Convert powershell/PowerShell-Windows-CI to GitHub Actions #24899
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
Merged
TravisEz13
merged 64 commits into
master
from
convert-powershell-convert-forconversion-windows-ci-to-actions-20250129-195141
Jan 31, 2025
Merged
Convert powershell/PowerShell-Windows-CI to GitHub Actions #24899
TravisEz13
merged 64 commits into
master
from
convert-powershell-convert-forconversion-windows-ci-to-actions-20250129-195141
Jan 31, 2025
Conversation
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
…nuget_config_azfeed
TravisEz13
commented
Jan 29, 2025
TravisEz13
commented
Jan 29, 2025
TravisEz13
commented
Jan 29, 2025
.github/actions/tools_releasebuild_azuredevops_templates_insert_nuget_config_azfeed/action.yml
Outdated
Show resolved
Hide resolved
…t_nuget_config_azfeed/action.yml
TravisEz13
commented
Jan 29, 2025
.github/actions/pipelines_templates_insert_nuget_config_azfeed/action.yml
Outdated
Show resolved
Hide resolved
TravisEz13
commented
Jan 29, 2025
TravisEz13
commented
Jan 29, 2025
…t_nuget_config_azfeed/action.yml
TravisEz13
commented
Jan 31, 2025
TravisEz13
commented
Jan 31, 2025
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
…indows-ci-to-actions-20250129-195141
/azp run PowerShell-CI-macos, PowerShell-CI-Linux, PowerShell-CI-Windows, PowerShell-Windows-Packaging-CI |
Azure Pipelines successfully started running 4 pipeline(s). |
adityapatwardhan
approved these changes
Jan 31, 2025
Contributor
📣 Hey @TravisEz13, how did we do? We would love to hear your feedback with the link below! 🗣️ 🔗 https://aka.ms/PSRepoFeedback |
TravisEz13
added a commit
that referenced
this pull request
Feb 3, 2025
TravisEz13
added a commit
that referenced
this pull request
Feb 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
BackPort-7.4.x-Done
BackPort-7.5.x-Done
CL-BuildPackaging
Indicates that a PR should be marked as a build or packaging change in the Change Log
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.
Pipeline migrated from Azure DevOps
Tested this at: https://github.com/TravisEz13/PowerShell/actions/runs/13077820229
This pull request includes significant updates to the CI/CD pipeline configuration and testing processes, primarily focusing on PowerShell builds and tests. The changes introduce new workflows, modify existing ones, and enhance logging and artifact handling.
CI/CD Pipeline Enhancements:
New CI Build Workflow:
.github/actions/build/ci/action.yml
, which includes steps for capturing the environment, setting build names, bootstrapping, building, running xUnit tests, and uploading build artifacts.New Test Verification Workflow:
.github/actions/test/verify_xunit/action.yml
, which downloads build artifacts, captures the artifacts directory, and tests xUnit results.New Windows Test Workflow:
.github/actions/test/windows/action.yml
, which includes steps for capturing the environment, downloading build artifacts, bootstrapping, running tests, converting JUnit to CTRF, and publishing test reports.Workflow Modifications:
Auto Assign PR Maintainer:
.github/workflows/AssignPrs.yml
to trigger on issues instead of pull requests and added a condition to check if the event issue is a pull request. [1] [2]Windows CI Workflow:
.github/workflows/windows-ci.yml
to handle build, unelevated and elevated tests, and xUnit test result verification.Logging and Artifact Handling Enhancements:
Enhanced Verbose Logging:
tools/ci.psm1
by adding detailed logs for importing modules and starting Pester tests with specific output formats. [1] [2] [3] [4] [5] [6]Artifact Handling in GitHub Actions:
build.psm1
andtools/ci.psm1
to handle artifact uploading and copying in GitHub Actions environments. [1] [2]These changes collectively enhance the CI/CD pipeline's robustness, improve logging for better debugging, and ensure seamless artifact handling across different environments.