Re: SSH agent uses username 'jenkins' instead of the one configured in the credential

Thank you for your response. I'm afraid I'm using the latest Git client plugin: 2.8.6, and also the right protocol (ssh): the SCM checkout went well when running the pipeline on the parent repo. Out test database is a submodule of the repository and we only clone it if the build is OK, hence

Re: Restrict credential retrieval to a specific slave

On Thu, Sep 19, 2019 at 4:21 AM Jhonny Oliveira wrote: > Hi! > > is it possible to limit the usage of a credential to a specific slave? > Not with Jenkins as far as I know. Credentials can be defined on the Jenkins master, on folders, and on multibranch Pipelines. They can't be defined on

Re: Restrict credential retrieval to a specific slave

On Thu, Sep 19, 2019 at 6:30 AM Jhonny Oliveira wrote: > The idea is to have a self contained application (as in source repo), > where you have everything you need to maintain its SDLC: source, build, > tests (unit, regression, ...), continuous integration/automation > (Jenkinsfile). > > The

Re: Enable "Post Build Action" in Jenkins

Hi, You may refer to here: https://jenkins.io/doc/book/pipeline/syntax/#post In general, you will code all the post build in pipeline post() block, such as email-ext, archive-artifacts, etc. Hope this helps. Best regards, KH On Thu, Sep 19, 2019 at 12:04 AM Binay Jena wrote: > Thank you

Restrict credential retrieval to a specific slave

Hi! is it possible to limit the usage of a credential to a specific slave? With this restriction, I could fully empower developers to create their own Pipelines (Jenkinsfile) while avoiding passwords to be leaked in the wrong slaves/environments. Just for further context, in my scenario and

Re: Restrict credential retrieval to a specific slave

What do you mean with agents? The idea is to have a self contained application (as in source repo), where you have everything you need to maintain its SDLC: source, build, tests (unit, regression, ...), continuous integration/automation (Jenkinsfile). The Jenkinsfile should be part of the

Match multiple branches with Git plugin

Hi, I'm trying to use the Git plugin (with the GitHub plugin) to trigger builds on multiple branches with a single branch specifier rule. However, the job only appears to trigger when there are changes to on the "first" matching branch. I've tried wildcards (i.e. origin/dev/*) and regexes

Re: Restrict credential retrieval to a specific slave

Am Donnerstag, den 19.09.2019, 05:26 -0700 schrieb Jhonny Oliveira: What do you mean with agents? Jenkins people have stopped using the word "slave" some time ago. Bye... Dirk -- Dirk Heinrichs Senior Systems Engineer, Delivery Pipeline OpenText ™ Discovery | Recommind Phone: +49 2226 15966

Match multiple branches with Git plugin

Hi, I'm trying to use the Git plugin (with the GitHub plugin) to trigger builds on multiple branches with a single branch specifier rule. However, the job only appears to trigger when there are changes to on the "first" matching branch. I've tried wildcards (i.e. origin/dev/*) and regexes

Re: Jenkins Docker Image and extended Linux executables

On Thu, Sep 19, 2019 at 8:10 AM 'Carsten' via Jenkins Users < jenkinsci-users@googlegroups.com> wrote: > Hi, > we are running Jenkins in a docker environment. > Jenkins Version 2.192 > running in a docker container version 19.03.2, build 6a30dfc > Running on an Ubuntu Xenial 16.04 > We are

Re: Restrict credential retrieval to a specific slave

Dear Mark, I agree with you, I'm relying on long-lived agents. I read your answer, but I'm not understanding your suggestion to use folders, I do not comprehend how they can help. I mean, with folders I can avoid cross application credential usage and that is great, but I can't prevent cross

Re: Restrict credential retrieval to a specific slave

On Thu, Sep 19, 2019 at 8:41 AM Jhonny Oliveira wrote: > Dear Mark, > > I agree with you, I'm relying on long-lived agents. I read your answer, > but I'm not understanding your suggestion to use folders, I do not > comprehend how they can help. I mean, with folders I can avoid cross >

Amazon EC2 plugin issues with Windows agents

Hi All, I have been trying to get windows agents spun up in Amazon EC2 via Jenkins using the Amazon EC2 plugin. The agents are getting launched fine, but, Jenkins is not able to connect to them at all. No matter whatever settings I try, like, I have this in my userdata section:

Re: Restrict credential retrieval to a specific slave

The idea is to have a self contained application (as in source repo), where you have everything you need to maintain its SDLC: source, build, tests (unit, regression, ...), continuous integration/automation (Jenkinsfile). The Jenkinsfile should be part of the source code and cover the entire

Jenkins Docker Image and extended Linux executables

Hi, we are running Jenkins in a docker environment. Jenkins Version 2.192 running in a docker container version 19.03.2, build 6a30dfc Running on an Ubuntu Xenial 16.04 We are deploying by Linux shell scripts using multiple extended Linux commands like "netcat" or "nslookup". Unfortunately the