testing empty release test#29864
Conversation
|
Azure Pipelines: Successfully started running 1 pipeline(s). There may be pipelines that require an authorized user to comment /azp run to run. |
|
|
There was a problem hiding this comment.
Pull request overview
This PR modifies the Azure Pipelines release-test definition by removing the Windows and Linux smoke-test job templates, leaving only the job that checks for the latest PowerShell version.
Changes:
- Removed the Win/Linux
util/smoke-test-steps.ymltemplate job entries fromrelease-test.yml. - Kept the
CheckLatestPowerShellVersionjob as the only active job in the pipeline.
Comments suppressed due to low confidence (1)
.azure-pipelines/release-test.yml:55
- Removing all Win/Linux smoke-test template jobs leaves this pipeline only checking the latest PowerShell version, so it no longer performs the release smoke testing implied by
release-test.yml. This significantly reduces release validation coverage; if this was only for an experiment, it should not be merged as-is. Consider restoring the removed smoke-test jobs, or guarding them behind a parameter (defaulting to enabled) so release validation remains intact.
jobs:
- job: CheckLatestPowerShellVersion
displayName: Check for latest PowerShell version
pool:
name: ${{ variables.linuxAgentPoolName }}
steps:
- task: PowerShell@2
displayName: Check for latest PowerShell version
inputs:
pwsh: true
targetType: filePath
filePath: ./tools/TestFx/Live/CheckLatestPowerShellVersion.ps1
|
🤖 Auto-trigger: queued 2 pipeline(s) for commit |
|
🤖 Auto-trigger: queued 2 pipeline(s) for commit |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
Comments suppressed due to low confidence (1)
.azure-pipelines/release-test.yml:55
- This PR appears to remove all Windows/Linux smoke test jobs from the release-test pipeline, leaving only the version-check job. That effectively disables the release validation this pipeline is meant to provide and can allow regressions to ship undetected. If the intent is to temporarily reduce coverage, consider gating smoke tests behind a parameter/variable or commenting them out (like the MacOS entries) rather than deleting them; otherwise, please restore the removed smoke test templates.
jobs:
- job: CheckLatestPowerShellVersion
displayName: Check for latest PowerShell version
pool:
name: ${{ variables.linuxAgentPoolName }}
steps:
- task: PowerShell@2
displayName: Check for latest PowerShell version
inputs:
pwsh: true
targetType: filePath
filePath: ./tools/TestFx/Live/CheckLatestPowerShellVersion.ps1
| @@ -0,0 +1 @@ | |||
| Temp change | |||
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
Comments suppressed due to low confidence (1)
temp.txt:2
temp.txtis introduced but appears unused (no references found in the repo). Committing a temporary/placeholder file adds noise and can confuse future contributors; please remove it or replace it with a file that’s part of the intended feature/change.
Temp change
More changes
| jobs: | ||
| - template: util/smoke-test-steps.yml | ||
| parameters: | ||
| name: 'Win_PS5_1_14_SmokeTest' | ||
| agentPoolName: ${{ variables.winAgentPoolName }} | ||
| psVersion: ${{ parameters.win_ps }} | ||
| dotnetVersion: ${{ parameters.dotnet_sdk_8 }} | ||
|
|
||
| - template: util/smoke-test-steps.yml | ||
| parameters: | ||
| name: 'Win_PS7_4_X_SmokeTest' | ||
| agentPoolName: ${{ variables.winAgentPoolName }} | ||
| psVersion: ${{ parameters.ps7_4 }} | ||
| dotnetVersion: ${{ parameters.dotnet_sdk_8 }} | ||
|
|
||
| - template: util/smoke-test-steps.yml | ||
| parameters: | ||
| name: 'Win_PS7_5_X_SmokeTest' | ||
| agentPoolName: ${{ variables.winAgentPoolName }} | ||
| psVersion: ${{ parameters.ps7_5 }} | ||
| dotnetVersion: ${{ parameters.dotnet_sdk_9 }} | ||
|
|
||
| - template: util/smoke-test-steps.yml | ||
| parameters: | ||
| name: 'Win_PS7_6_X_SmokeTest' | ||
| agentPoolName: ${{ variables.winAgentPoolName }} | ||
| psVersion: ${{ parameters.ps7_6 }} | ||
| dotnetVersion: ${{ parameters.dotnet_sdk_10 }} | ||
|
|
||
| - template: util/smoke-test-steps.yml | ||
| parameters: | ||
| name: 'Win_Preview_PS_SmokeTest' | ||
| agentPoolName: ${{ variables.winAgentPoolName }} | ||
| psVersion: ${{ parameters.preview_ps }} | ||
| dotnetVersion: ${{ parameters.dotnet_sdk_9 }} | ||
|
|
||
| - template: util/smoke-test-steps.yml | ||
| parameters: | ||
| name: 'Linux_PS7_4_X_SmokeTest' | ||
| agentPoolName: ${{ variables.linuxAgentPoolName }} | ||
| psVersion: ${{ parameters.ps7_4 }} | ||
| dotnetVersion: ${{ parameters.dotnet_sdk_8 }} | ||
|
|
||
| - template: util/smoke-test-steps.yml | ||
| parameters: | ||
| name: 'Linux_PS7_5_X_SmokeTest' | ||
| agentPoolName: ${{ variables.linuxAgentPoolName }} | ||
| psVersion: ${{ parameters.ps7_5 }} | ||
| dotnetVersion: ${{ parameters.dotnet_sdk_9 }} | ||
|
|
||
| - template: util/smoke-test-steps.yml | ||
| parameters: | ||
| name: 'Linux_PS7_6_X_SmokeTest' | ||
| agentPoolName: ${{ variables.linuxAgentPoolName }} | ||
| psVersion: ${{ parameters.ps7_6 }} | ||
| dotnetVersion: ${{ parameters.dotnet_sdk_10 }} | ||
|
|
||
| - template: util/smoke-test-steps.yml | ||
| parameters: | ||
| name: 'Linux_Preview_PS_SmokeTest' | ||
| agentPoolName: ${{ variables.linuxAgentPoolName }} | ||
| psVersion: ${{ parameters.preview_ps }} | ||
| dotnetVersion: ${{ parameters.dotnet_sdk_9 }} | ||
|
|
||
| - job: CheckLatestPowerShellVersion | ||
| displayName: Check for latest PowerShell version |
|
/azp run azure-powershell - powershell-core |
|
/azp run azure-powershell - windows-powershell |
|
Commenter does not have sufficient privileges for PR 29864 in repo Azure/azure-powershell |
1 similar comment
|
Commenter does not have sufficient privileges for PR 29864 in repo Azure/azure-powershell |
|
/azp run |
|
Azure Pipelines: Successfully started running 3 pipeline(s). |
|
🤖 Auto-trigger: queued 2 pipeline(s) for commit |
Description
Mandatory Checklist
Please choose the target release of Azure PowerShell. (⚠️ Target release is a different concept from API readiness. Please click below links for details.)
Check this box to confirm: I have read the Submitting Changes section of
CONTRIBUTING.mdand reviewed the following information:ChangeLog.mdfile(s) appropriatelysrc/{{SERVICE}}/{{SERVICE}}/ChangeLog.md.## Upcoming Releaseheader in the past tense.ChangeLog.mdif no new release is required, such as fixing test case only.