How boskod/adomonitor works
Project type and purpose
• This is a .NET console application (“Azure DevOps console client”) whose sole responsibility is to call the Azure DevOps Services REST API, deserialize responses into C# models, and print or process information in the console.
• It retrieves build information, release information, and service‐health status from Azure DevOps using the REST API endpoints.
File structure
• Top level contains:
• ADOMonitor.sln – the Visual Studio solution
• .github/workflows/dotnet.yml – CI pipeline definition
• ADOMonitor/ADOMonitor.csproj – project file
• README.md
• Inside ADOMonitor/:
• Program.cs – the entry point with Main(), orchestrating calls
• Models/ – namespaces broken out by API area:
– ADOBuilds (all types under Builds endpoints)
– ADOReleases (all types under Releases endpoints)
– ADOServiceHealth (types under Service Health endpoints)
README for additional insights
• The README confirms it’s purely a REST‐API client with no UI; it’s intended to demonstrate or automate Azure DevOps data retrieval.
• It links to the official REST API docs, implying the code wraps those endpoints.
Elements
• From CLI → API Connector → HTTP Client → Azure DevOps REST API
• Responses return in reverse direction through the same path
• CI/CD → builds/tests project