User-level config

[pzelnip]

Right now I have many repos that I interact with (microservices architecture). As well, the Jenkins that builds each of those projects requires authentication for getting build status. This means that with the extension I currently have to duplicate my name & password in a .jenkins file for each repo I have checked out, which isn't great from a security POV, as well as from a DRY perspective (if my password changes I now have to update multiple .jenkins files).

It'd be great if the name/password could be defined in one place (maybe like ~/.jenkins) and that used as the default config for repos (I'd still want the ability to on a project-by-project basis be able to override those creds for when I interact with a different repo).

[alefragnani]

Hi @pzelnip ,

I'm sorry for taking so long to answer you. I saw your post but wasn't near a workable computer and ended up forgetting to answer you 😢 .

Anyway, I think that instead of another file to store your authentication keys, why not store them on User Settings, like other VS Code settings?

[pzelnip]

The only hesitation I have about throwing them in User Settings is I use the Settings Sync extension which throws all my settings into a gist on Github.

[alefragnani]

That's a good point 😄

Ok then, an external file to store Jenkins credentials 👍

[webratz]

has this ever been implemented?

[alefragnani]

Hi @webratz ,

No, not yet. Do you have plans in contribute, or are willing to use?

[webratz]

in this case i would be more interested from a users point of view :)