Skip to content
New issue

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

Found no applicable tools #17

Open
janvanuytrecht opened this issue Oct 28, 2022 · 3 comments
Open

Found no applicable tools #17

janvanuytrecht opened this issue Oct 28, 2022 · 3 comments

Comments

@janvanuytrecht
Copy link

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?

@lohithgn
Copy link

lohithgn commented Apr 6, 2023

@janvanuytrecht hello. yes - you are responsible to make sure that the tools that extension supports should be installed on your agents. Since its self hosted agent - you are responsible to meet the pre-requisites. The MS hosted agents already have the tools required pre-installed.

If you read the extension document here: https://marketplace.visualstudio.com/items?itemName=ms-securitydevops.microsoft-security-devops-azdevops - it is already mentioned.

image

hope this helps.

@janvanuytrecht
Copy link
Author

janvanuytrecht commented Apr 6, 2023 via email

@boAndron
Copy link
Contributor

boAndron commented May 9, 2023

Hey, sorry for the delay. The action should be installing the tools by itself, so I don't think that's the problem.
The auto-applicability detection is supposed to look at your repo and determine what tools it should run based of file types found. Are you by any chance running on an empty repo?
Otherwise, are you setting the policy to 'none'? The policy can also affect which tools are chosen for auto-applicability.
Can you run tools by specifying them (via a config, or the 'tools' input)?
Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants