Tim Jacomb
Tim Jacomb
Makes sense, thanks
> (a?) pre-installed NodeJS Be careful here, you don't want projects to be locked into a specific version of node.js and can't be updated without updating infra. The native Jenkins...
I don't understand how PR's would use a different version to the main one, unless you mean the updatecli PR will try revert it back if you upgrade it before...
> If I understand correctly, it's related to the 2 missing days as per [#4285 (comment)](https://github.com/jenkins-infra/helpdesk/issues/4285#issuecomment-2462829657). > > Let's see the November update which should fix this (no ETA yet)...
Finally managed to get the tool (https://github.com/jenkins-infra/jenkins-usage-stats) to work and I get the same broken results locally. I'll try debug some more when I get more time.
I suspect the report command may have been run with the wrong month and data for that month wasn't in the database. The docs say: ``` ❯ ./build/jenkins-usage-stats report Error:...
Yes its been not performed since October.
Its @jenkinsci/credentials-plugin-developers most likely @jtnord From my memory remote credentials themselves aren't supposed to be cached. You can cache the metadata e.g. the results of a list credentials call (without...
Yes but most plugins won't call it on every step they'll only call it once...
> for something specific to one piece of code a Secret used in plugins (global) configuration should be used. Maybe once, these days credentials API is used for most secrets....