[azure-pipelines].customSchemaFile use relative path
See original GitHub issueI’m trying to modify a workspace-shared .vscode/settings.json
to share the custom schema for the YAML pipelines with my team using the [azure-pipelines].customSchemaFile
configuration setting, but using a relative path doesn’t seem to work.
Using the full path is not a good solution for a shared workspace config since the project might be cloned to a different path.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:8
- Comments:5
Top Results From Across the Web
Templates - Azure Pipelines | Microsoft Learn
Templates let you define reusable content, logic, and parameters. Templates function in two ways. You can insert reusable content with a ...
Read more >azure-pipelines-vscode/service-schema.json at main - GitHub
VS Code extension for working with Azure Pipelines YAML files - azure-pipelines-vscode/service-schema.json at main · microsoft/azure-pipelines-vscode.
Read more >Configuring the Build Step in YAML — SpecFlow+ LivingDoc ...
For information on the YAML schema, see the Microsoft reference guide for Azure Pipelines YAML schema. SpecFlow+LivingDoc custom build step YAML snippet¶. - ......
Read more >How to load file locally with path vs path in Azure Devops build
So, you can't directly use the absolute (or relative) paths in the scripts to access the local machines. In Azure Pipelines, if we...
Read more >In-Depth Guide to Building a PowerShell Pipeline in Azure ...
Here you can specify either filePath providing the path to the script to run or use inline which indicates that you'll be adding...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Wouldn’t it be a good idea to support online uri
https://dev.azure.com/YOU-ORG-HERE/_apis/distributedtask/yamlschema
too?With proper caching and http cache headers to only update when there is a new version, network delays to fetch the schema online should not be a problem. I love the idea.