Answering my own question, I did an experiment and tried adding a new user
(while working) and upgrading and could still log in. Based on that, I
updated my user password while working and upgraded, and it worked. So
maybe something about how the old passwords were stored/encrypted.
Anyways,
I asked about this a couple months ago but did not have time to really dig
into it then.
I am currently on Jenkins version 2.265 with the latest version of all
plugins (that I can update). When I upgrade to 2.266+ (have tried with
latest), the server restarts but my user login no longer works
Hi there
Does anyone know if there is any advantage between using Jenkins
pipeline Step 'readJSON' and 'JsonSlurper'. I'm asking because in best
practices page the suggestion is to avoid JsonSlurper but they don't
mention nothing about readJson step. I want to figure out what way
should I go
Sorry, Björn, but I think I didn’t get it:
* Is your suggestion to use?
*
withEnv([“http_proxy=https://${PROXY_CREDENTIALS}@proxy-endpoint.com:3128”]) {
* But isn’t that what kelvSYC also tried and “gets flagged as unsafe by
Jenkins”
*
