ci: remove stage level pool field, isCustom, from e2e job templates #3898
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 removes deprecated stage-level pool configurations from Azure DevOps pipeline templates. The changes clean up multiple e2e job templates by removing the pool field that specified isCustom: true, type: linux, and name: $(BUILD_POOL_NAME_DEFAULT) at the stage level.
- Removes stage-level pool configuration from 9 e2e pipeline templates
- Eliminates the deprecated
isCustomfield from pool specifications - Streamlines pipeline configuration by removing redundant pool settings
Reviewed Changes
Copilot reviewed 9 out of 9 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
.pipelines/singletenancy/dualstack-overlay/dualstackoverlay-e2e.stages.yaml | Removes stage-level pool configuration |
.pipelines/singletenancy/cilium-overlay/cilium-overlay-e2e.stages.yaml | Removes stage-level pool configuration |
.pipelines/singletenancy/cilium-overlay-withhubble/cilium-overlay-e2e.stages.yaml | Removes stage-level pool configuration |
.pipelines/singletenancy/cilium-nodesubnet/cilium-nodesubnet-e2e.stages.yaml | Removes stage-level pool configuration |
.pipelines/singletenancy/cilium-dualstack-overlay/cilium-dualstackoverlay-e2e.stages.yaml | Removes stage-level pool configuration |
.pipelines/singletenancy/azure-cni-overlay/azure-cni-overlay-e2e.stages.yaml | Removes stage-level pool configuration |
.pipelines/singletenancy/azure-cni-overlay-stateless/azure-cni-overlay-stateless-e2e.stages.yaml | Removes stage-level pool configuration |
.pipelines/singletenancy/aks/e2e.stages.yaml | Removes stage-level pool configuration |
.pipelines/singletenancy/aks-swift/e2e.stages.yaml | Removes stage-level pool configuration |
jpayne3506 added release/latest | /azp run Azure Container Networking PR |
| Azure Pipelines successfully started running 1 pipeline(s). |
rbtr approved these changes Aug 7, 2025
NihaNallappagari pushed a commit to NihaNallappagari/azure-container-networking that referenced this pull request Sep 4, 2025
…zure#3898) ci: remove stage level custompool field from e2e templates
sivakami-projects pushed a commit that referenced this pull request Oct 23, 2025
…3898) ci: remove stage level custompool field from e2e templates
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:
Upstream validation changes now capture for these fields
Issue Fixed:
Requirements:
Notes: