special character in secret text

Hi, I am attempting to mask passwords in config files by creating secret text credentials and using them to search and replace the values in the files. It is working as expected except for when there is a dollar sign '$' special character in the secret text. With the '$' in the secret text,

Re: Enable Auto refresh Button

Refer to the Jenkins 2.223 changelog for the retirement of Auto Refresh. That links to the pull request that removed the code. Replacement techniques are available for Google Chrome and Firefox using browser

Enable Auto refresh Button

Hi together, does anybody know where the "enable auto refresh" button is gone or is there a workaround existing? Since the last update to version 2.225 this button is not available anymore... [cid:image001.png@01D5FE14.E288B9F0] Best regards, Thomas H. -- You received this message because

Re: Security concern for Gitlab webhook token to Jenkins

Am Mittwoch, den 18.03.2020, 17:10 -0700 schrieb Jheison Rodriguez: I'd like to know if someone has experienced this and had managed this kind of set up in another way? We use Smee (https://smee.io/) for this. HTH... Dirk -- Dirk Heinrichs Senior Systems Engineer, Delivery Pipeline

Re: Security concern for Gitlab webhook token to Jenkins

I haven't tried it so I don't know if it works, but have you tried passing the Authorization header in the request rather than setting username & password as part of the URL? e.g. `Authorization:Basic username:apiToken` where the whole `username:apiToken` is base-64 encoded Richard. On Thu, 19

Re: Cancel Job aborts Agent Connection (JNLP)

Yes, we upgraded it. I know how to check this in the UI as well as scripted on the master. We tested this not only one year later but with different intermediate releases. I've also created a bug report last year in summer (https://issues.jenkins-ci.org/browse/JENKINS-58764), but it has been

Re: Security concern for Gitlab webhook token to Jenkins

In our case, we are using GitHub but we had similar concerns. Our solution was to create a little server with NGINX configured to forward the webhooks to our Jenkins masters. In this way, we could achieve the following: 1) Jenkins masters are not exposed at all to internet 2) The configuration