Hi there,
>From within a pipeline i would like to generate parallel jobs, and i
want all these jobs to run as ECS tasks using different specialised
docker images.
Can I use this syntax to achieve that?
stages {
stage ('Parallel builds') {
parallel {
stage ('Build#1') {
agen
On 18 March 2018 at 03:21, Sean Talts wrote:
> Hey all,
>
> I'm having this sudden crazy problem where my Windows agent can't delete
> some files in its workspace anymore, failing all builds. It's getting a
> java.nio.file.AccessDeniedException on some files that it created. You can
> see the full
On 17 March 2018 at 21:15, Christian Gagneraud wrote:
[...]
> It looks to me that the templated jenkins-slave container doesn't
> share /homme/jenkins with it's host, and so side containers
> (python:2.7 in my case) cannot inherit them.
>
> Does anyone know what sort of
Hi there,
Running Jenkins 2.89.4 (BlueOcean), with Amazon EC2 Container Service
plugin v 1.11
I have successfully setup my self-hosted docker host connected to
jenkins using the "docker cloud" plugin, i can get this cloud execute
declarative pipelines that needs docker container such as:
I'm trying the "Bitbucket Team/Project" (which uses the "multibranch Pipeline").
Using "jenkinsci/blueocean:latest" docker image.
When i create a new ""Bitbucket Team/Project"" item, the BB project is
scanned, project is added and repo too. Repo that have a
"/Jenkinsfile" are picked up and built,
On 27 February 2018 at 04:55, nicolas de loof wrote:
> For a dockerized agent to be able to run docker pipeline, it has to use a
> volume for workspace directory so this one can be shared with other
> containers it creates.
> Your docker agent template should be configured to use "/home/jenkins/ag
On 26 February 2018 at 15:29, Christian Gagneraud wrote:
> On 26 February 2018 at 03:10, nicolas de loof
> wrote:
>> docker support in declarative pipeline relies on docker-workfow plugin,
>> which require the jenkins slave to have access to a LOCAL docker daemon,
>>
On 26 February 2018 at 03:10, nicolas de loof wrote:
> docker support in declarative pipeline relies on docker-workfow plugin,
> which require the jenkins slave to have access to a LOCAL docker daemon,
> which means the docker agent you are provisioning on computer B using docker
> plugin HAS to b
Hi there,
I have a machine A that runs Jenkins and Bitbucket-server in docker containers.
I have a machine B, that just has docker listening over tcp.
I have a project that uses Declarative pipeline with "agent { docker
'foobar:X.Y'}"
I'm using "jenkinsci/blueocean:latest" docker image with
"docke
