Found no applicable tools

Open
#17 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
azure, typescript
Domain
ci-cd, cloud, devops, security

Research direction

Start by reproducing the Security DevOps task with the self-hosted Azure DevOps Agent and inspect the MSDO CLI invocation and its tool/configuration options. The missing command and configuration details need to be clarified; done means determining whether omitting a tool should select all tools or whether installation/configuration is required, then documenting the resulting behavior.

Written by the indexing model from the issue text.

Description

Hi,

We use a self-hosted Agent in Azure to support our Azure DevOps CI/CD.

When I run the security devops task as such:

The task fails, I get this result:

Tools Applicability Infomation:
Found no applicable tools.

##[error]RunCommandNoOptionsException: No applicable tools were detected. Run requires at least one configuration to run. Provide at least one Guardian config or tool with --config or --tool.
##[error]MSDO CLI exited with an error exit code: 2

I understood that when passing no tool, all of them should be used?
Do we need to install these tools ourselves?

Dominant language
TypeScript
Stars
86
Forks
22
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/security-devops-azdevops

All issues in microsoft/security-devops-azdevops

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.