feat(azuredevops): add environment_pattern for extracting environment… #8671
+250
−10
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
… names from job/stage names This enhancement addresses the issue where the Azure DevOps plugin was unable to correctly detect production deployments when the environment name is embedded in job/stage names rather than being in a standard format. Changes: - Add `environment_pattern` scope config field that supports regex capture groups to extract environment names from job/stage names - Collect both Job and Stage records from the timeline API (previously only Job) - Add `identifier`, `type`, and `parent_id` fields to the Job model - Update environment detection logic: - If environment_pattern is configured, extract the environment name first - Apply production_pattern to the extracted environment name - Fall back to matching production_pattern against job name if no extraction - Fix default environment behavior: only default to PRODUCTION when production_pattern is not configured (was defaulting PRODUCTION always) - Add comprehensive tests for the new functionality Example configuration for pipelines with jobs like 'deploy_xxxx-prod_helm': - deployment_pattern: deploy - production_pattern: prod - environment_pattern: (?:deploy|predeploy)[_-](.+?)(?:[_-](?:helm|terraform))?$ This extracts 'xxxx-prod' from the job name and then applies production_pattern to correctly identify it as a production deployment. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <[email protected]>
dosubot
bot
added
size:L
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
… names from job/stage names
This enhancement addresses the issue where the Azure DevOps plugin was unable to correctly detect production deployments when the environment name is embedded in job/stage names rather than being in a standard format.
Changes:
environment_patternscope config field that supports regex capture groups to extract environment names from job/stage namesidentifier,type, andparent_idfields to the Job modelExample configuration for pipelines with jobs like 'deploy_xxxx-prod_helm':
This extracts 'xxxx-prod' from the job name and then applies production_pattern to correctly identify it as a production deployment.
🤖 Generated with Claude Code
pr-type/bug-fix,pr-type/feature-development, etc.Summary
What does this PR do?
Does this close any open issues?
Closes 8869
Screenshots
Include any relevant screenshots here.
Other Information
Any other information that is important to this PR.