Add MicrobotsLogAnalyzer custom ADO task support#141
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #141 +/- ##
==========================================
+ Coverage 64.95% 64.99% +0.04%
==========================================
Files 34 34
Lines 2374 2374
==========================================
+ Hits 1542 1543 +1
+ Misses 832 831 -1
Flags with carried forward coverage won't be shown. Click here to find out more. 🚀 New features to boost your workflow:
|
|
You shouldn't be running from a fork for the tests to pass |
| codebasePath: tl.getPathInput("codebasePath", true, true), | ||
| logFilePath: input("logFilePath", true), | ||
| timeoutSeconds: input("timeoutSeconds", false) || DEFAULT_TIMEOUT_SECONDS, | ||
| }; |
There was a problem hiding this comment.
As we publish to open-source, we should support key-based authentication too. Update the PR if it is trivial otherwise, we can take it in the next iteration.
There was a problem hiding this comment.
Sure, this would be a useful addition.
However, key-based auth would require handling multiple Pipeline input-groupings and some changes + testing required for the new auth flow (currently the task uses AzureRM for login). It might be better to first publish & test the current custom task and take up additional LLM auth methods in subsequent iteration.
|
|
||
| ## Use It In A Pipeline | ||
|
|
||
| See the complete sample pipeline at [docs/examples/azure-pipelines/microbots-log-analyzer.yml](examples/azure-pipelines/microbots-log-analyzer.yml). |
There was a problem hiding this comment.
Just want to confirm will the reference work correct in blog post
MadhurAggarwal
force-pushed
the
madagg/log-analyzer-ado-task
branch
from
cce98a7 to
b12284e
Compare
MadhurAggarwal
force-pushed
the
madagg/log-analyzer-ado-task
branch
from
b12284e to
dc7143a
Compare
|
Hi, I've resolved the comments
Kindly re-review the PR. |
|
Moved branch from Forked repo to Main Repo for running Github Tests. |
5 participants
Adds a custom Azure DevOps task,
MicrobotsLogAnalyzer@0, for running MicrobotsLogAnalysisBotagainst log files using Azure OpenAI models, with authentication through an Azure Resource Manager Service Connection.Overview
MicrobotsLogAnalyzerTaskAzure Pipelines task.Change Details
.gitignore: Ignores generatednode_modulesfolders used while packaging the ADO task.README.md: Added a brief guide for the new MicrobotsLogAnalyzerTask.azure-pipelines/vss-extension.json: Defines the ADO extension that contributes the custom pipeline task. This file is needed for publishing the task.azure-pipelines/MicrobotsLogAnalyzerTask/task.json: Defines theMicrobotsLogAnalyzer@0task metadata, inputs, Node 20 handler, and task restrictions (restrictions ensure that LLM Outputs don't setup unwanted ENVs in ADO Pipeline, for example printing##vso[task.setvariableas part of Log RCA)azure-pipelines/MicrobotsLogAnalyzerTask/index.js: Implements Main Workflow: validates inputs, logs into Azure Service Connection, prepares Python venv, runsLogAnalysisBot, and prints the analysis.azure-pipelines/MicrobotsLogAnalyzerTask/package.json: Declares the Node dependencies required by the task.azure-pipelines/MicrobotsLogAnalyzerTask/package-lock.json: Locks task Node dependency versions for reproducible packaging.docs/azure-pipelines-log-analyzer.md: Documents prerequisites, packaging, publishing, usage, inputs, and task behavior.docs/examples/azure-pipelines/microbots-log-analyzer.yml: Provides a sample ADO YAML for usingMicrobotsLogAnalyzer@0.mkdocs.yml: Adds the new Azure Pipelines Log Analyzer guide to the docs navigation.Added 12 Unit tests:
