We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Azure DevOps (may include Kubernetes or public cloud instances)
Task Ideas from a Platform Admin and User context
Persona 1 - Platform Owner of Azure DevOps Verify Agent Pool Status:
Are all Azure DevOps agent pools operational, and do they have sufficient capacity for pipeline execution? Inspect Service Connections:
Are service connections (e.g., Azure, AWS, Kubernetes) configured correctly and active? Audit Pipeline Execution Logs:
Are there recurring errors or failures in pipelines due to platform-level configurations? Check Access Controls:
Are Azure DevOps project and repository access permissions aligned with organizational policies? Monitor Azure DevOps Billing and Usage:
Is the organization staying within its Azure DevOps license limits for users, pipelines, and artifacts? Ensure Integration Health:
Are integrations with third-party tools (e.g., GitHub, Slack, JIRA) working as expected? Troubleshoot Pipeline Performance:
Are pipeline execution times unusually high, and is it due to agent performance or resource contention? Evaluate Repository Settings:
Are repository settings (branch policies, merge restrictions) configured as per company standards? Inspect Artifact Management:
Are artifact storage limits being approached, and are older artifacts being cleaned up? Review Azure DevOps Security Settings:
Are personal access tokens (PATs), OAuth tokens, and SSH keys being managed securely?
Persona #2 - Consumer of Azure DevOps Resolve Pipeline Failures:
Why is a specific pipeline failing, and is it due to a configuration or code issue? Validate YAML Pipeline Configurations:
Are pipeline YAML configurations correct, and do they reflect the intended build and deployment logic? Check Build Artifact Availability:
Are the build artifacts from a previous pipeline run available and accessible? Investigate Permissions Issues:
Is lack of permissions causing problems with pipeline execution or repository access? Debug Variable Issues:
Are pipeline variables, including secret variables, resolving correctly during pipeline runs? Ensure Agent Allocation:
Are the correct agents being used for pipeline tasks, and are they meeting the requirements? Analyze Deployment Failures:
Are release pipelines deploying applications to the correct environments without errors? Monitor CI/CD Triggers:
Are pipelines triggering correctly based on repository changes or schedule settings? Review Test Results:
Are test results from pipeline runs consistent, and do they match expected outcomes? Handle Git Integration Problems:
Are branch policies, pull requests, or Git-related operations functioning as expected in Azure DevOps?
No response
None
The text was updated successfully, but these errors were encountered:
stewartshea
No branches or pull requests
What cloud platform(s) should this support?
Azure DevOps (may include Kubernetes or public cloud instances)
What are some key tasks that should be performed?
Task Ideas from a Platform Admin and User context
Persona 1 - Platform Owner of Azure DevOps
Verify Agent Pool Status:
Are all Azure DevOps agent pools operational, and do they have sufficient capacity for pipeline execution?
Inspect Service Connections:
Are service connections (e.g., Azure, AWS, Kubernetes) configured correctly and active?
Audit Pipeline Execution Logs:
Are there recurring errors or failures in pipelines due to platform-level configurations?
Check Access Controls:
Are Azure DevOps project and repository access permissions aligned with organizational policies?
Monitor Azure DevOps Billing and Usage:
Is the organization staying within its Azure DevOps license limits for users, pipelines, and artifacts?
Ensure Integration Health:
Are integrations with third-party tools (e.g., GitHub, Slack, JIRA) working as expected?
Troubleshoot Pipeline Performance:
Are pipeline execution times unusually high, and is it due to agent performance or resource contention?
Evaluate Repository Settings:
Are repository settings (branch policies, merge restrictions) configured as per company standards?
Inspect Artifact Management:
Are artifact storage limits being approached, and are older artifacts being cleaned up?
Review Azure DevOps Security Settings:
Are personal access tokens (PATs), OAuth tokens, and SSH keys being managed securely?
Persona #2 - Consumer of Azure DevOps
Resolve Pipeline Failures:
Why is a specific pipeline failing, and is it due to a configuration or code issue?
Validate YAML Pipeline Configurations:
Are pipeline YAML configurations correct, and do they reflect the intended build and deployment logic?
Check Build Artifact Availability:
Are the build artifacts from a previous pipeline run available and accessible?
Investigate Permissions Issues:
Is lack of permissions causing problems with pipeline execution or repository access?
Debug Variable Issues:
Are pipeline variables, including secret variables, resolving correctly during pipeline runs?
Ensure Agent Allocation:
Are the correct agents being used for pipeline tasks, and are they meeting the requirements?
Analyze Deployment Failures:
Are release pipelines deploying applications to the correct environments without errors?
Monitor CI/CD Triggers:
Are pipelines triggering correctly based on repository changes or schedule settings?
Review Test Results:
Are test results from pipeline runs consistent, and do they match expected outcomes?
Handle Git Integration Problems:
Are branch policies, pull requests, or Git-related operations functioning as expected in Azure DevOps?
Any other helpful context?
No response
Contact
None
The text was updated successfully, but these errors were encountered: