Invoking AWS lambda from Jenkins Pipeline Stage

[Kai]

Hi,

Is there a plugin available to invoke AWS lambda from Jenkins Pipeline 
Stage ? 

Thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/5afe490a-99ff-4480-b79b-65f26e664c6f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins pipeline script params not recognized, bad substitution error

[Kai]

I have a similar issue, I have a build job that is parameterized and am Not 
able to successfully use that parameter to pass as an argument to my python 
script in my pipeline stage

On Monday, July 10, 2017 at 2:46:17 PM UTC-7, Justin Khoo wrote:
>
> how can I read in the params from jenkins script shell sh? 
>
> pipeline {
>   stages{
>stage('Deploy') {
> steps {
> sh 'python deploy.py ${params.version}'
> }
> }
>   }
> }
>
> I have tried several ways, but still not able to read in params.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/52bb8118-5eb1-4e43-88d3-f91fff1f6311%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

jenkins pipeline script params not recognized, bad substitution error

[Justin Khoo]

how can I read in the params from jenkins script shell sh? 

pipeline {
  stages{
   stage('Deploy') {
steps {
sh 'python deploy.py ${params.version}'
}
}
  }
}

I have tried several ways, but still not able to read in params.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/79457e00-4858-4fb5-825d-91e3a2976e13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

possible to have jenkins job pass in parameter to next stage in pipeline

[Kai]

Hi,

We have a stage in Jenkins pipeline where we invoke a Jenkins Job. (e.g. 
 build job: ... )

Is there a way for that Jenkins job that is invoked to pass in a 
value/parameter to the next stage in the pipeline ?

thanks

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a3c66f3b-44f6-4542-a1f8-b419afd67bd4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Permissions & Github Status API

[Dave Cadwallader]

I'm looking to use the Github Org plugin to post pass/fail results to the
Github status API on pull requests.

It looks like the user that owns the OAuth token needs to have write access
to the repo.

I'm wondering if there is a way to allow this user to post to the status
API without actually having access to commit code.  There should be no
reason for the system user to ever change code.  Want to avoid a security
hole.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAKHfr%3Dpxak6VjqkbW2YhPDx2%3DifuWSdQea%2BRVLKxsUDf7afmVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Distributed Builds: Software required to build only installed on build node?

[Simon Richter]

Hi,

On 10.07.2017 21:27, Jason LeMauk wrote:

> Am I correct in assuming that when the project is built, the ioncube
> encoder will not need to be installed on the Jenkins Master machine but
> will need to be installed on the Jenkins Agent / Slave machine?

The master also has two executors, so jobs can be scheduled there.

To avoid this, use a tag on the hosts where the software is installed,
and require that tag inside the project config using "Restrict where
this build can be run".

This also allows you to install the software on a subset of the slave
machines only.

   Simon

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1eba1bb1-0c4b-58df-f007-679a65c45d1a%40hogyros.de.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

Distributed Builds: Software required to build only installed on build node?

[Jason LeMauk]

I have a distributed build system in place (1 Jenkins Master and several build 
nodes).

I have a piece of software required for a project's build whose licensing is 
tied to the MAC address of the machine which has the software installed 
(ioncube encoder).

Am I correct in assuming that when the project is built, the ioncube encoder 
will not need to be installed on the Jenkins Master machine but will need to be 
installed on the Jenkins Agent / Slave machine?

Thanks in advance for any advice / help!

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/BY2PR12MB059919A486D766B247F188ED89A90%40BY2PR12MB0599.namprd12.prod.outlook.com.
For more options, visit https://groups.google.com/d/optout.

Change build status when input step aborted

[Thiago Carvalho Davila]

Hello,

I want to set the status in my declarative pipeline to success if the input 
step is aborted OR reached it's timeout.

steps {
    timeout(time: 30, unit: 'MINUTES') {
    input(id: 'userInput', message: 'Promote build?') 
    }
}

If I don't promote the build or it expires 30 minutes of timeout, I assume the 
pipeline succeeded.

I tried the input step documentation 
(https://jenkins.io/doc/pipeline/steps/pipeline-input-step/), but it is very 
confusing.

Tks,

Thiago

-


"Esta mensagem do SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO), empresa 
pública federal regida pelo disposto na Lei Federal nº 5.615, é enviada 
exclusivamente a seu destinatário e pode conter informações confidenciais, 
protegidas por sigilo profissional. Sua utilização desautorizada é ilegal e 
sujeita o infrator às penas da lei. Se você a recebeu indevidamente, queira, 
por gentileza, reenviá-la ao emitente, esclarecendo o equívoco."

"This message from SERVIÇO FEDERAL DE PROCESSAMENTO DE DADOS (SERPRO) -- a 
government company established under Brazilian law (5.615/70) -- is directed 
exclusively to its addressee and may contain confidential data, protected under 
professional secrecy rules. Its unauthorized use is illegal and may subject the 
transgressor to the law's penalties. If you're not the addressee, please send 
it back, elucidating the failure."

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/bdc50cffafab88d0049011edc885c867c1c982d8%40serpro.gov.br.
For more options, visit https://groups.google.com/d/optout.

Set/change Branch description in multibranch pipelines

[Michael Lasevich]

I would like to set "description" field in automatically generated branches 
in Multibranch Pipeline to add some information like links to latest 
artifacts, links to latest generated documentation, etc. While I would 
settle for one standard default description for all the branches, ideally 
it would be nice to be able to set it from Jenkinsfile - similar to how 
other branch job properties can be set via "properties" command.  As far as 
I can tell, you cannot currently do this via "properties" - but I could be 
wrong. Is there a way to do this using just the pipeline code in 
Jenkinsfile?

I have tried getting the item from Jenkins directly to manipulate it, but 
sandboxing (rightfully) blocked me from doing that. I suppose I could write 
a shared lib function to do that, which would bypass the sandboxing, but I 
was wondering if there is a more proper way of doing this? I can't imagine 
I am the only one who wants to do that.

Thanks, 

-M

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1e2137fe-8142-4db7-8a7e-1c2dfe0ba090%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins running docker container slaves that run builds using docker

[Jake Bishop]

Yes, that makes sense. I think this is acceptable in our scenario.
Thanks for the pointer. 

If you (or anyone else here) has any links to examples it would be greatly 
appreciated 


> On 10. Jul 2017, at 17:48, nicolas de loof  wrote:
> 
> it means a build with some "malicious code" (sic) could access all other 
> builds, secrets injected into a build environment by jenkins, all host 
> ressources, etc. It could as well create by intent or because of some buggy 
> script create thousands containers and exhaust host resources. 
> 
> consider docker.sock as some super-root access to your build node.
> 
> 2017-07-10 17:45 GMT+02:00 Yakobe  >:
> The security of these jenkins builds are not critical since they are just for 
> testing. Therefore it sounds perhaps a simpler approach.
> However, i'm interested in what the issues are with build isolation. Does 
> that mean that build could fail, and under what sort of circumstance?
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to jenkinsci-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/6fadf55e-ccff-4e9a-951b-8e9731e8c01a%40googlegroups.com
>  
> .
> 
> For more options, visit https://groups.google.com/d/optout 
> .
> 
> 
> -- 
> You received this message because you are subscribed to a topic in the Google 
> Groups "Jenkins Users" group.
> To unsubscribe from this topic, visit 
> https://groups.google.com/d/topic/jenkinsci-users/GgLlUPWRLcQ/unsubscribe 
> .
> To unsubscribe from this group and all its topics, send an email to 
> jenkinsci-users+unsubscr...@googlegroups.com 
> .
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzkm%2BJFqFKROs-0%2BgNM9ovo-ThT0zSF%3DrtRxe9PS5D51uQ%40mail.gmail.com
>  
> .
> For more options, visit https://groups.google.com/d/optout 
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/3ED55313-39B8-420A-88B2-4EA2F017FD54%40gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins running docker container slaves that run builds using docker

[nicolas de loof]

it means a build with some "malicious code" (sic) could access all other
builds, secrets injected into a build environment by jenkins, all host
ressources, etc. It could as well create by intent or because of some buggy
script create thousands containers and exhaust host resources.

consider docker.sock as some super-root access to your build node.

2017-07-10 17:45 GMT+02:00 Yakobe :

> The security of these jenkins builds are not critical since they are just
> for testing. Therefore it sounds perhaps a simpler approach.
> However, i'm interested in what the issues are with build isolation. Does
> that mean that build could fail, and under what sort of circumstance?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/6fadf55e-ccff-4e9a-951b-8e9731e8c01a%40googlegroups.
> com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzkm%2BJFqFKROs-0%2BgNM9ovo-ThT0zSF%3DrtRxe9PS5D51uQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins running docker container slaves that run builds using docker

[Yakobe]

The security of these jenkins builds are not critical since they are just 
for testing. Therefore it sounds perhaps a simpler approach.
However, i'm interested in what the issues are with build isolation. Does 
that mean that build could fail, and under what sort of circumstance?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6fadf55e-ccff-4e9a-951b-8e9731e8c01a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins running docker container slaves that run builds using docker

[nicolas de loof]

Not so simple

bind mounting docker.sock means you give access to anything on host, so you
just give up with security and isolation between builds.
Docker in Docker require some adequate combination for the docker daemon
setup to be nested, especially on how it stores containers layers on disk
(and then, nested layers for second level docker daemon). play-with-docker
uses device mapper + overlay2 with success.


2017-07-10 17:36 GMT+02:00 Yakobe :

> Then it sounds like this i achievable. Thanks so much for the response. At
> least i know that this is something worth looking in to.
>
> I read somewhere about this Docker in Docker approach (i think it is
> sometimes referred to as DinD?). Some people where saying it is not a good
> idea.
> Am i right in understanding that it is better to bind mount
> /var/run/docker.sock?
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/a65338f8-a2da-4a3a-93dd-224d8b3fb74b%40googlegroups.
> com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzmcX%3D-ZGixBJprfXUSqWWXeTr9WcWZnJp-%3D2%2BC%3DJE9doQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins running docker container slaves that run builds using docker

[Yakobe]

Then it sounds like this i achievable. Thanks so much for the response. At 
least i know that this is something worth looking in to.

I read somewhere about this Docker in Docker approach (i think it is 
sometimes referred to as DinD?). Some people where saying it is not a good 
idea.
Am i right in understanding that it is better to bind mount 
/var/run/docker.sock?

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/a65338f8-a2da-4a3a-93dd-224d8b3fb74b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins running docker container slaves that run builds using docker

[nicolas de loof]

You have two options :

1. use a Docker in Docker image (play-with-docker.com for sample is using
this approach)
2. bind mount /var/run/docker.sock into your build container so you can
interact with the host's docker daemon

Both of them involve some security consideration, so you might need to
double check your infrastructure requirements.

2017-07-10 15:11 GMT+02:00 Yakobe :

> The main aim behind this post is to find out if this is even possible
> before losing too much time. So if anyone could any insight at all it would
> be greatly appreciated.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/jenkinsci-users/fa88594b-1780-48d5-aad6-c4a960e8dae1%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CANMVJz%3D_5tZTEnCyk_DWZqmAxwjambWP1yyYtr6v0A_5baLyeQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is pipeline timeout suppose to work?

[jerome]

When trying the 45 minutes units into the syntax helper (pipeline-syntax/ 
of the project) it display the following code:
timeout(45) {
// some block
}

If I change the unit the syntax change like follow:
timeout(time: 45, unit: 'SECONDS') {
// some block
}

So I will try with the following too see if it change something:
timeout(time: 45, unit: 'MINUTES') {
// some block
}

The document seem to specify the timeout goes into the options block when 
using declarative pipeline (which I don't), but for normal pipeline I guess 
the* //some block* above is for any code block or is a block a specific 
type (stage, node...) ? This is unclear.
If this is any code block, it doesn't seem to work with either bat or steps 
warning publisher, which I cannot interrupt by cancelling the build into 
the GUI, so I guess the timeout may not cancel them either.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/1ff554c4-b80e-4224-85cd-10f5da6e1d16%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins running docker container slaves that run builds using docker

[Yakobe]

The main aim behind this post is to find out if this is even possible 
before losing too much time. So if anyone could any insight at all it would 
be greatly appreciated.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/fa88594b-1780-48d5-aad6-c4a960e8dae1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

git fetch returns 143 error code

[jaroskrzek]

Hi,

 

I'm facing the problem with Jenkins Git authentication. I attach a 
screenshot of the stack trace. I have SSH gitlab connection configured with 
a private key and a passphrase. The configuration is made in 
Credentials/System/Global credentials (unrestricted). The path to the 
private key is /home/jenkins/.jenkins/secrets/my_private_key.pub. Owner and 
a group: jenkins:jenkins, where jenkins is the user making the 
installation. Permissions: 600.

The private key has been checked with the passphrase using ssh from the 
command line. The git fetch command used by jenkins has also been checked 
with command line. Both works.

Repository URL format is like 


   -g...@github.com:org-name/project.git (short notation for ssh 
   protocol)
   
Environment:·


   -  CentOS 7 64 bit
   - openjdk version "1.8.0_131" 64 bit
   -Jenkins ver. 2.67
   - Git client plugin 2.4.6
   - Git plugin 3.3.0 (3.3.1 is not helping too)
   - GIT server Plugin 1.7
   - GitLab Plugin 1.4.5 (1.4.6 is not helping too)
   - SCM API Plugin 2.1.1
   - Credentials Plugin 2.1.14
   -Jenkins is run directly
   -   Jenkins was installed with yum installer
   -Browser: Google Chrome 59
   -   GitLab Community Edition 9.3.5
   -git version 1.8.3.1
   
 

Regards,

Jaroslaw Skrzek

Software Engineer

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/c8739de4-c0c6-45eb-90e5-0c8f5c77a19f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Pipeline Docker Permissions

[Richard Bywater]

Took me a while to come back but just wanted to point out the group
approach is what is "recommended" by Docker in the docs @
https://docs.docker.com/engine/installation/linux/linux-postinstall/ So
definitely the least hacky of all the solutions :)

Richard.

On Sun, 9 Jul 2017 at 06:55 Dan Kinon  wrote:

> I'm running centos7 and installing pre-packaged docker 1.12.6 from epel7.
> I did see the suggestion out in the wild to add the jenkins user to the
> "docker" (specifically "dockerroot" on my installation) group.  I tried
> this early on and it had no effect.  I noticed that the unix socket
> (/var/run/docker.sock) was owned user root and group root with 660
> permissions so that is why adding the jenkins user to the dockerroot group
> had no effect.  To solve this issue, I had to change the group ownership on
> the socket by modifying /etc/sysconfig/docker and adding
> `--group=dockerroot` to the OPTIONS variable:
>
>> OPTIONS='--selinux-enabled --log-driver=journald
>> --signature-verification=false --group=dockerroot'
>>
>
> Once I did this (in combination with adding the jenkins user to the
> dockerroot group) and restarted docker everything worked.  This still feels
> a little hacky but at least it doesn't carry the negative security
> implications of some of the other solutions I mentioned.
>
> It would still be nice to have some semblance of control over how jenkins
> pipeline accesses/calls docker but this will do for now.  Thanks for
> pointing me back in the docker group direction.
>
> On Friday, July 7, 2017 at 3:10:12 PM UTC-7, Richard Bywater wrote:
>
>> I haven't checked for a while but it used to be that if you add a user to
>> the "docker" group they'll be able to access docker commands.
>>
>> Richard
>>
>> On Sat, 8 Jul 2017, 9:27 AM Dan Kinon  wrote:
>>
> Hello,
>>>I'm running jenkins as a non-root user and am attempting to use a
>>> docker agent in my jenkinsfile.  When I run the job, I get the following
>>> error:
>>> 
>>> [VA_Build_containers_develop-NJECFMY5Y6Z5OKTQVWTCSYEZEVQKAXGGRGECV2LSFA2YZ2ALBWQQ]
>>> Running shell script
>>> + docker inspect -f . docker:1.12.6
>>> .
>>> Failed to run image 'docker:1.12.6'. Error: /usr/bin/docker-current:
>>> Cannot connect to the Docker daemon. Is the docker daemon running on this
>>> host?.
>>> See '/usr/bin/docker-current run --help'.
>>> ~~~
>>>
>>>The root cause of course is that docker is running as root and
>>> jenkins is not.  The "solution" I've found on the internet is to open up
>>> permissions to the world on the docker.sock or to add a tcp connecter to
>>> docker.  While that may functionally get me what I want that is a hack not
>>> a best practice solution IMHO.
>>>
>>>I want to tell Jenkins docker agent to execute docker via sudo (as
>>> I've given the jenkins user all required permissions via sudoers) but I
>>> can't figure out how.  Is there any way to currently do this or is this a
>>> feature request.
>>>
>>> Thanks in advance,
>>> -Dan
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "Jenkins Users" group.
>>>
>> To unsubscribe from this group and stop receiving emails from it, send an
>>> email to jenkinsci-use...@googlegroups.com.
>>
>>
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/jenkinsci-users/CAErRXL-EUOsLn9OAZ3xq8zQgmAZcXSpZWRSqzEBScecgwkoEDA%40mail.gmail.com
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/c3035dda-a79c-4dde-8bdf-d21908cd9866%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CAMui946m8LmmM%2B8scNYywpgjarB5JbxQJY9v81%3Dsj0RTrSNiVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is it possible to pause a pipeline, via an input, and then only allow a privileged user to progression it???

[paul b]

That seems to be working fine.  Guess, when I read it the first time, it 
threw me with the field named 'submitter'! Thanks

On Friday, 7 July 2017 13:59:44 UTC+1, Richard Ginga wrote:
>
> if you look at the "input" pipeline step documentation, use:
>
> submitter (optional)
> User IDs and/or *external* group names of person or people permitted to 
> respond to the input, separated by ','. If you configure "alice, bob", will 
> match with "alice" but not with "bob". You need to remove all the white 
> spaces.
>
> Type: String
>
> On Fri, Jul 7, 2017 at 4:13 AM, paul b  
> wrote:
>
>> As above but possibly with a set of users.  I have checked the 
>> documentation and cant seem to see anything...
>>
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Jenkins Users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to jenkinsci-use...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/jenkinsci-users/cce685a2-8553-4457-9fcb-ace099be9d92%40googlegroups.com
>>  
>> 
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> Dick Ginga
> Build Engineer
> rgi...@disruptorbeam.com 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/6cb5b243-f082-45e2-b900-4ed0cb8fccca%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Issue with RegEx for project roles in Matrix Authorization Strategy Plugin

[Raj Kiran Neerukonda]

Hello,

I am having similar problem. Right now i am having multiple directories, i 
need to control access to sub directories. For example, i have component 
specific jenkins jobs in 

parent/project/component/* 

How can i configure this pattern in role base authentication?

I tried giving parent/project/component|parent/project/component/* 

it dint worked. Please help me. 

Thank you,

Raj Kiran.

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/b2514fd7-d0d7-4e8e-97e3-58e4099eadf2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Amazon EC2 Container Service Plugin Waiting for Executor

[Stephen Connolly]

On Mon 10 Jul 2017 at 03:44, Douglas Manley  wrote:

> Update: I believe that I have fixed the problem within the
> "amazon-ecs-plugin".  The short story is that it's possible to tell Jenkins
> that the automatically-created nodes, once they start a job, will never run
> another job again, causing Jenkins to spin up more nodes to handle the
> remaining items in the queue.  The responsiveness is reasonably good, and
> it totally meets my needs at work.
>
> The pull request is here; it has not been merged in yet (as of
> 2017-07-09): https://github.com/jenkinsci/amazon-ecs-plugin/pull/48
>

Oh so close sadly looks like the cigar is missing.

Durable tasks are not going to work as they cannot be accepted so when they
requeue they will run on a different agent, and think the shell step died.

If it were not for the fun of durable tasks you'd be totally on the money
here.

There is a retention strategy that does what you want in durable tasks
plugin. Try reworking the PR to use that.

Excellent work in perhaps the trickiest API of Jenkins to work with.


>
> On Thursday, June 8, 2017 at 2:57:20 PM UTC-4, Douglas Manley wrote:
>>
>> As far as I can tell, it's not actually the plugin that's the problem.
>> Rather, Jenkins only asks the "cloud" provider (in this case, ECS) to
>> create a new node when there are zero nodes available.  Thus, as long as
>> there is one job running, Jenkins sees it as a valid node and will politely
>> wait until it finishes to run the next job.  Instead, the node kills itself
>> and only then does Jenkins ask the cloud provider to create another node.
>>
>> It seems like there just needs to be some kind of plugin that can read
>> the *queue *and talk to the cloud providers based on the number of tasks
>> outstanding.
>>
>> On Monday, May 1, 2017 at 4:52:02 PM UTC-4, Joshua Noble wrote:
>>>
>>> This plugin has an unfortunate known flaw - it will only spin up one
>>> executor/node per label. If you have two jobs waiting to build with the
>>> same label, it will build the first one, then kill after it's done, and
>>> then start the next one. (Instead of creating two containers/tasks in
>>> parallel) I've tried all the hacks (single build slave plugin, etc) and
>>> they no longer work.
>>>
>>> For this reason I've decided not to use it. You're much better off using
>>> the EC2 plugin (which is very well supported), registering those nodes as
>>> build agents, and then using Jenkins' native Docker workflow with
>>> pipelines. (In essence, this means Jenkins will run docker containers on
>>> the EC2 machine)
>>>
>>> On Monday, July 18, 2016 at 12:46:41 AM UTC-4, Tez Macca wrote:

 Hi,

 I have configured the "Amazon EC2 Container Service Plugin" with a
 single statically associated EC2 instance. My expectation is that multiple
 slaves/containers would be started when there are multiple jobs scheduled.
 However, I get the following message when the second job runs:
 *Waiting for next available executor on aws-slaves-c50dc930a5d94*
 Where '*aws-slaves-c50dc930a5d94'* is the node instance started by the
 first job. The jobs start and execute perfectly though.

 To get multiple executors do I need to change something with:
 1. how I have configured the AWS plugin,
 2. OR the ECS cluster in AWS,
 3. OR my Jenkinsfile needs something like concurrency set in the stage?

 This also means that I am unable to run multiple parallel steps.

>>> --
> You received this message because you are subscribed to the Google Groups
> "Jenkins Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to jenkinsci-users+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jenkinsci-users/1292e400-6e91-4550-b080-b1311d1cab9d%40googlegroups.com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Sent from my phone

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/CA%2BnPnMw4XaxDhq%3DFhZ1shAXB%2BOTL4L0MNzDR%3Dqx-E6RqngbBCw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: First time Jenkins user. I am getting this error.

[Andreas Tscharner]

On 10.07.2017 02:49, Terry O'Leary wrote:

Hello,



Hello World,


I found this in the Jenkins issues:

https://issues.jenkins-ci.org/browse/JENKINS-38057

Take a look at the comments below the issue and you will see a few
people ran into this and noticed their JAVA was set to a new JAVA 9
version. Once they set it back to JAVA 7 all was OK.


Just a quick note: current Jenkins version need at least Java 8 nowadays

Best regards
Andreas
--
Andreas Tscharner 
--
"Intruder on level one. All Aliens please proceed to level one."
  -- Call in "Alien: Resurrection"

--
You received this message because you are subscribed to the Google Groups "Jenkins 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-users/92b781fb-6cdd-a5d8-9c1e-4f24f6a09ff6%40gmail.com.
For more options, visit https://groups.google.com/d/optout.