ci: release test skip npm k8s e2e linux podsubnet #3525
Merged
+66
−66
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
There was a problem hiding this comment.
Pull Request Overview
This PR updates the CI pipeline configuration to skip the npm k8s E2E tests in release testing when running on a Linux cluster with a pod subnet by refining the job condition.
- Updated the condition logic in the npm k8s E2E job to check for a Linux cluster that does not contain 'linux-podsub' in its name.
- Adjusted the logical combination of expressions to ensure the intended tests are skipped.
vipul-21
reviewed
Mar 21, 2025
vipul-21
approved these changes
Mar 21, 2025
|
/azp run Azure Container Networking PR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
QxBytes
approved these changes
Mar 24, 2025
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Reason for Change:
Skipping npm k8s e2e in release test pipeline
Issue Fixed:
Requirements:
Notes: