Previously the current LTS of jenkins would not work with docker 1.12
because of this
issue https://github.com/maxfields2000/dockerjenkins_tutorial/issues/20
Has anyway here tested jenkins LTS with the Docker 1.13?
Is there a way to get around the issue with another docker plugin?
On my setup
tests steps doesn't return an exit code that is a non zero,
which should allow the test to continue but i am wondering if jenkins will
still report a failed build?
Omeka
--
You received this message because you are subscribed to the Google Groups
"Jenkins Users" group.
To unsubs
what is most efficient approach or the best practices when executing
pipelines with parallel steps in one with stage in a docker container?
the options my teammates and i are exploring is launching parallel
taskswith a single container vs using docker-compose to launch each
parallel tasks in
Thanks andrew it works very well.
do you have any intention to make failire/success/etc... usable in normal
stages so i can execute a stage only if the previous one is success?
Le lundi 21 novembre 2016 20:25:46 UTC+1, Andrew Bayer a écrit :
>
> Hi -
>
> In the latest release of Declarative Pipe
hello thank you for you response
Eddard Omka
Le samedi 26 novembre 2016 21:17:11 UTC+1, Baptiste Mathus a écrit :
>
> Hey,
>
> You should probably start with the general things like
> https://wiki.jenkins-ci.org/display/JENKINS/Distributed+builds
> https://wiki.jenkins-ci.org/display/JENKINS/C
Thank you for the hint, it worked
Le mercredi 30 novembre 2016 23:50:29 UTC+1, Victor Martinez a écrit :
>
> Hi there,
>
> Pipeline is fully supported by JobDSL (
> https://jenkinsci.github.io/job-dsl-plugin/#method/javaposse.jobdsl.dsl.DslFactory.pipelineJob)
>
> and also Multi Branch Pipeline
==
the build is excuted in docker container based on the official python 3.5
image
I have to admit i have been playing with python for about just two weeks so
i might be missing something.
Best regards
Omeka
--
You received this message because you are subscribed to the
