Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
No schema for pool.vmImage
See original GitHub issueUsing hosted agent pools is the most common use case I see for using Azure Pipelines. This extension doesn’t recognize the following
pool:
vmImage: ubuntu-16.04
There are no errors, but there’s no autocomplete, etc for vmImage - it’s just seen as an unrecognized extra property.
It seems like at one point there was a commit to add this functionality: https://github.com/microsoft/azure-pipelines-vscode/commit/20cb16d2bbbb79084d8f54bfdde0cfc728a18c5f
And it was lost with the latest schema update: https://github.com/microsoft/azure-pipelines-vscode/commit/71521de3616d7d0ecaed9a5a766b95b008f941bd#diff-e19d8a26e2287aa3875f1181a6c39773
@vtbassmatt Would you be open to me opening a PR to add this back in?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:3
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
The schema is generated by the server, so adding it manually here will just get clobbered again in the future. I’ll see if @damccorm can get a proper fix on the server, then I’ll regenerate the schema here.
@vtbassmatt yes it works at the root and also documentation states:
You can specify a pool at the pipeline, stage, or job level. The pool specified at the lowest level of the hierarchy is used to run the job.https://docs.microsoft.com/en-us/azure/devops/pipelines/yaml-schema?view=azure-devops&tabs=schema