Security concern for Gitlab webhook token to Jenkins

currently I'm using a webhooks token for trigger Jobs from GitLab to Jenkins, I have a global user so a token set up for all project something like this: https://USERID:APITOKEN@JENKINS_URL/project/YOUR_JOB Additionally, when I create a

Jenkins pipeline Testing

Hello Everyone, I'd like to know some thoughts about your experience with Jenkins pipelines testing (Jenkinsfile, Shared libraries, CPS, declarative pipeline). We want to start implementing it in our Company. Whatever help will be appreciate  -- You received this message because you are

RE: Re: Jenkins pipeline Testing

plugin for plugins to consume the plugins on our Jenkins instance as dependencies for our gradle build.   On Tue, Mar 24, 2020 at 12:32 Jheison Rodriguez <jasonll...@gmail.com> wrote:Hello Everyone, I'd like to know some thoughts about your experience with Jenkins pipelines testing (Jenki

readJson, JsonSlurper or JQ

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

RE: Environment variable - shell

Correct if I’m wrong guys, but I think you should skip the $ for \$   Jheison Rodriguez From: Elango ThiagarajanSent: Tuesday, February 2, 2021 10:58 AMTo: Jenkins UsersSubject: Environment variable - shell Hi folks, I am very new to Jenkins. Kindly help me through. I have few parameters declared