Suggestion: Configure Jenkins URL in workspace settings

[ilkka]

When deciding on putting the config into a .jenkins file, did you consider adding custom plugin-specific config into the VS Code workspace settings file instead? My first thought is that since this configuration is both project and VS Code specific, that would be the natural place. Or does some other tool use .jenkins files also? Don't get me wrong, I don't think it's bad, this is just me thinking aloud really :)

[alefragnani]

Hi @ilkka ,

The main reason is because I created the extension based on the idea of the Travis. It needs to have the configuration file in the root folder because is how the Travis integration works (of course, its file has much more info than mine 😄 ). It was my base model. Also, because the VSCode activation based on file existence only works for files in root folder.

Sure, it could be moved/selected another location for the file . The only downside would be the activation (overall performance), but it's no a big deal.