[Concourse] VSCode extension doesn't understand glob patterns in group config
See original GitHub issueDescribe the bug
The Concourse extension in VSCode complains on glob patterns in groups
configuration.
https://concourse-ci.org/pipelines.html#schema.group_config
To Reproduce
Use the sample from below. Although incomplete to be used in a real Concourse setup, it shows the error being reported clearly:
On top of that, the reverse problem of a job not being part of a group is also reported:
Sample
groups:
- name: build
jobs:
- "ci-*"
jobs:
- name: ci-project-one
plan:
- task: gradle-build
file: gradle-build-dcind.yml
Issue Analytics
- State:
- Created 2 years ago
- Comments:7 (6 by maintainers)
Top Results From Across the Web
Contribution Points | Visual Studio Code Extension API
To extend Visual Studio Code, your extension (plug-in) declares which of the various Contribution Points it is using in its package.json Extension Manifest ......
Read more >How to make VS Code treat a file extensions as a certain ...
Choose Preferences: Open User Settings (JSON) to open your settings. json . To find the proper language ID, use Ctrl + Shift +...
Read more >Debugging with Visual Studio Code | by Sam Lindstrom
After a year of using Visual Studio Code (VS Code) I've finally ... that were passed in the config object had outdated glob...
Read more >The Basics of Visual Studio Code - vscode-docs
VS Code gives you many options to configure the editor. You can set options globally through user settings or per project/folder through workspace...
Read more >Understanding the glob pattern in Node.js - LogRocket Blog
js installed on your machine; A code editor, preferably VS Code. Table of contents. What is glob matching? Common glob patterns; Setting up...
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
Yeah I did click there (I think) and a few other places but somehow I still cannot find any hint anywhere of using glob patterns in job names. No matter, I think I know enough from the issue ticket I dug out to make sense of it.
And about VUB… yes indeed. What a small world! 😃
This should now be fixed in latest snapshot. If you want to try it out it can be downloaded from here: http://dist.springsource.com/snapshot/STS4/nightly-distributions.html
I implemented my own simple glob pattern matcher which only supports the use of ‘*’. As it wasn’t too hard to do, it actually does support the use of multiple stars in a single pattern. Any other types of patterns are not supported. When the validation sees them it basically just assumes that it is a ‘complex’ pattern which it doesn’t know how to match. So it conservatively assumes the pattern could match anything. The effect of that is that all validation checks around these patterns will automatically pass and there will be no false errors (but also any real errors will be supressed).
More patterns could be supported in the future either by making the implementation of the glob matcher more complete or by finding some ‘good enough’ Java library that can be used to replace the simple matcher and is considered as ‘close enoungh’ in terms of supporting similar syntax as concourse’s library does.
Note: Java actually has a built-in glob matcher (https://docs.oracle.com/javase/8/docs/api/java/nio/file/PathMatcher.html). I didn’t like to use it because it seems to be intended specifically for matching file names and paths, and job names are not file names.