Re: Containerized Jenkins master and agents

[nicolas de loof]

Hi.

Why do you use some "jnlp-agent-docker" agent as you then switch to another
one, based on a docker image ? Why not just use the later for the whole
build ?

Le lun. 18 mars 2019 à 07:20, Daniele Riccucci  a
écrit :

> Hello,
> I recently switched to running Jenkins from host machine to a docker
> container (https://hub.docker.com/r/jenkins/jenkins).
> I was also using docker agents to build. This is now broken in my
> current setup as I'm spinning up a slave container to run pipelines and
> issues arise in a situation such as:
>
> pipeline {
>  agent { label 'jnlp-agent-docker' }
>  // this is the major change as before it was not a container,
>  // the label refers to a template with a similar version of
>  // https://github.com/jenkinsci/jnlp-agents/ > docker
>  stages {
>  stage('Build') {
>  agent {
>  docker { // could also be dockerfile
>  image ""
>  }
>  }
>  steps {
>  git 'myrepo'
>  sh "build"
>  archiveArtifacts artifacts: 'dist/**/*'
>  }
>  }
>  }
> }
>
> The docker plugin (this one >
> http://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin) is obviously
> unable to mount workspaces in another container and builds fail.
> I would like to avoid adding a new template for this and using docker in
> docker
> (
> https://support.cloudbees.com/hc/en-us/articles/360001566111-Set-up-a-Docker-in-Docker-Agent-Template)
>
> if possible
> (https://jpetazzo.github.io/2015/09/03/do-not-use-docker-in-docker-for-ci/),
>
> but I'll adapt to whatever works.
>
> Is there a correct way to build using containers for jenkins, and the
> slaves?
>
> Thank you.
>
> --
> 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/9fb2d785-1b74-c0d4-dd05-4b072e8efe59%40posteo.net
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Nicolas De Loof

-- 
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/CANMVJzmAcGFLmMmHd_TOpYHgZ%2Bw4fz%2BinQS3wEfeSrG-fNGDsg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Use AdoptOpenJDK as JDK Tool download source

[nicolas de loof]

I assume this would require a JEP ?

Le mar. 26 févr. 2019 à 17:32, Slide  a écrit :

> +1 on deprecation
>
> On Tue, Feb 26, 2019 at 9:08 AM nicolas de loof 
> wrote:
>
>> I don't know if we have any metric for this purpose, but docker images
>> seems to me a way better solution to cover the same need, and this "tool
>> installer" feature is just a hack-ish legacy we should deprecate.
>>
>> Le mar. 26 févr. 2019 à 15:44, Slide  a écrit :
>>
>>> How many people use the automatic installation, is there a way to track
>>> that? Would it kill someone's usage model to remove this feature? It seems
>>> to me to be fairly unsustainable.
>>>
>>> On Tue, Feb 26, 2019, 06:22 Baptiste Mathus  wrote:
>>>
>>>> Hey Martijn,
>>>>
>>>> Thanks for chiming in. I already have commented there in the JIRA, but
>>>> asking here since it seems at this stage better suited in a discussion
>>>> place: do you have an opinion/idea about whether, and how long, it will be
>>>> tolerated that certain IPs download the same JDK binaries from
>>>> adoptopenjdk.net <https://api.adoptopenjdk.net/> like dozens or
>>>> hundreds of time a day? I mean: how is the bandwidth consumption handled on
>>>> adoptopenjdk.net? Isn"t there a risk that some users be banned from
>>>> downloading from there if they suck for instance +100GB, or much more, of
>>>> bandwidth a day?
>>>>
>>>> I'm asking because I've been arguing there and some other places that
>>>> anyway this feature has always been problematic. And I tend to think it's
>>>> cool for demos, but that normal usages shouldn't rely on downloading
>>>> binaries from an external source forever, for a variety of reasons I've
>>>> listed in the JIRA issue linked previously.
>>>>
>>>> Thanks! :)
>>>>
>>>> Le dim. 24 févr. 2019 à 21:17, Martijn Verburg <
>>>> martijnverb...@gmail.com> a écrit :
>>>>
>>>>> Hi all,
>>>>>
>>>>> I help run AdoptOpenjDK - It's the defacto 'community' OpenJDK distro
>>>>> now (Amazon, Azul, GoDaddy, IBM, jClarity, Microsoft, Pivotal, Red Hat et
>>>>> al are collaborating there).  Let me know if you need any help connecting
>>>>> to our API:
>>>>>
>>>>> https://api.adoptopenjdk.net
>>>>>
>>>>> Cheers,
>>>>> Martijn
>>>>>
>>>>>
>>>>> On Sat, 23 Feb 2019 at 18:14, Sverre Moe  wrote:
>>>>>
>>>>>> Thanks for the link. Good to see that they are looking into it. Hope
>>>>>> it doesn't take to long.
>>>>>>
>>>>>> fredag 22. februar 2019 15.38.57 UTC+1 skrev Devin Nusbaum følgende:
>>>>>>>
>>>>>>> There is some relevant discussion in
>>>>>>> https://issues.jenkins-ci.org/browse/JENKINS-54305 that may be
>>>>>>> interesting to you.
>>>>>>>
>>>>>>> On Feb 22, 2019, at 09:20, Sverre Moe  wrote:
>>>>>>>
>>>>>>> Now that Oracle has shut down any commercial use of their JDK,
>>>>>>> Jenkins should add option to download JDK from AdoptOpenJDK
>>>>>>>
>>>>>>> Install automatically
>>>>>>> Extract *.zip/*.tar.gz
>>>>>>> Install from java.sun.com
>>>>>>> Run Batch Command
>>>>>>> Run Shell Command
>>>>>>>
>>>>>>> Now that the JDK from Oracle cannot be used in production we need
>>>>>>> another source.
>>>>>>>
>>>>>>> Install from AdoptOpenJDK
>>>>>>> https://adoptopenjdk.net/
>>>>>>>
>>>>>>> --
>>>>>>> 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/6a0fc33b-e4b4-4c06-9674-2c49218617fe%40googlegroups.com
>>>>>>> <https://groups.google.com/d/msgid/jen

Re: Use AdoptOpenJDK as JDK Tool download source

[nicolas de loof]

_source=footer>
>>>> .
>>>> 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/CAP7YuAT-guxrRa8J4GrpLfL_%2BUE4zZwCSa0GvEfUq49F2ficdQ%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAP7YuAT-guxrRa8J4GrpLfL_%2BUE4zZwCSa0GvEfUq49F2ficdQ%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>> 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/CANWgJS5NhKXyvHaJinOkz4P9BpxPVC7eRi%2BzYaDbR_TFcVOfEQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CANWgJS5NhKXyvHaJinOkz4P9BpxPVC7eRi%2BzYaDbR_TFcVOfEQ%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> 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/CAPiUgVcA6VkkJxR-KStpaYn-S6SGO4h%2B_QfHa53BbV8XCbm8ug%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAPiUgVcA6VkkJxR-KStpaYn-S6SGO4h%2B_QfHa53BbV8XCbm8ug%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Nicolas De Loof

-- 
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%3DrkCWQPnU58eiEdr%3DqpZmADAc7fZDTREXaxVUotm0jqg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: docker image for jenkins:lts is not latest

[nicolas de loof]

As clearly explained here : https://hub.docker.com/_/jenkins/
#RTFM :)



Le lun. 10 déc. 2018 à 09:26, Adrien Lecharpentier <
adrien.lecharpent...@gmail.com> a écrit :

> The docker image `jenkins` is deprecated for a longtime. The ofificial
> image you need to pull and use is, as you guest, `jenkins/jenkins`. The
> `jenkins` image will soon no longer be published / updated.
>
> Le lun. 10 déc. 2018 à 02:44, RAJENDRA PRASAD <
> rajendra.penuma...@gmail.com> a écrit :
>
>> Jenkins can be downloaded from here:
>> https://jenkins.io/download/
>>
>> Latest stable or LTS build is: 2.150.1
>>
>> Weekly release: 2.154 (this is not throughly tested).
>>
>> Thanks,
>> Rajendra
>>
>> On Fri, 7 Dec, 2018, 13:08 Dan Tran >
>>> Hi
>>>
>>> Current docker image for  jenkins:lts is not latest - 2.150.1
>>>
>>> Could someone confirm?  otherwise, it  may be something to do with my env
>>>
>>> Thanks
>>>
>>> -D
>>>
>>>
>>>
>>>
>>> --
>>> 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/262a206d-3bee-457d-85a4-12eefd9ede92%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/262a206d-3bee-457d-85a4-12eefd9ede92%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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/CAMrg02TfoVOfD0XjFA5XPpQNEOP%2BqD21gy5P6dRS%2Bg%2Bq8O6mMA%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAMrg02TfoVOfD0XjFA5XPpQNEOP%2BqD21gy5P6dRS%2Bg%2Bq8O6mMA%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Adrien Lecharpentier
>
> --
> 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/CAKwJSvwR6BLxyxesa0UgVGp7%2BO9HT8HGNb6peTLbb5TpF4xUHA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAKwJSvwR6BLxyxesa0UgVGp7%2BO9HT8HGNb6peTLbb5TpF4xUHA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Nicolas De Loof

-- 
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%3DTJoe8K264NT8F%2BhXx8vBe-wUsQSy9z7o2fg%3DeFg_7Dw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Configuration as a Code Plugin securiy disable

[nicolas de loof]

"enabled" in web UI is a fake attribute, it's actual effect
<https://github.com/jenkinsci/jenkins/blob/22aa2e6e766074d11249893e3f35e0b99e20d3d0/core/src/main/java/hudson/security/GlobalSecurityConfiguration.java#L120>
is to invoke disableSecurity
<https://github.com/jenkinsci/jenkins/blob/22aa2e6e76/core/src/main/java/jenkins/model/Jenkins.java#L2526>()
which is actually equivalent to yaml config setting  securityRealm : None and
authorizationStrategy : Unsecured

That being said,
very bad idea to run jenkins unsecured. Think twice. At your own risks.
Don't do that. Don't

https://www.youtube.com/watch?v=aJo8N77FOAk

Le mar. 27 nov. 2018 à 09:21, Emir Özbir  a
écrit :

> I want disable security with Configuration as a code Plugin . So that I've
> created a yaml file shown as below .
> security:
>   enabled: false
>
> jenkins:
>   cloud:
>  /*** Others Configs ***/
>
>
> I've got a error  shown as below up the Jenkins instance .
>
> org.jenkinsci.plugins.casc.ConfiguratorException: Invalid configuration
> elements for type class jenkins.model.GlobalConfigurationCategory$Security
> : enabled err
>
> Which attribute is for disable security at Jenkins in CaasC plugin .
>
> Please Help .
>
> Best Regards .
>
> --
> 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/edbfe25f-4269-484b-a48d-dd00b12f6c74%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/edbfe25f-4269-484b-a48d-dd00b12f6c74%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Nicolas De Loof

-- 
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/CANMVJzmr3JgF17Dow3zTJFaVG68GAUyurm9R%2BSZCoodBY7wwgg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Configuration as code and preservation of credentials

[nicolas de loof]

A feature we'd like to investigate for JCasC is to make the web UI
read-only once configured from yaml
The specific sample of credentials could be adapted to support "preserve
existing entries" but we have no way to support this in a generic way
Also, JCasC is designed to support re-creating an equivalent jenkins master
from scratch, so from this point of view this would make no sense.

Le mar. 25 sept. 2018 à 22:07,  a écrit :

> But many things are otherwise preserved. I feel the implementation of the
> credentials configuration is doing a none vs. all approach, not taking into
> account existing entries:
>
> In SystemCredentialsProviderConfigurator:
>
> target.setDomainCredentialsMap(DomainCredentials.asMap(value))
>
>
> Maybe this code could be replaced to preserve existing entries.
>
>
> On Tuesday, September 25, 2018 at 10:03:00 PM UTC+2,
> damien.c...@collibra.com wrote:
>>
>> I've created the PR at
>> https://github.com/jenkinsci/configuration-as-code-plugin/pull/556 to
>> show an unit test reproducing the issue.
>>
>> On Tuesday, September 25, 2018 at 9:04:31 PM UTC+2,
>> damien.c...@collibra.com wrote:
>>>
>>> Hi,
>>>
>>> We're using Jenkins 2.121.3 and CasC 1.0. One thing we define as code is
>>> a list of credentials (some SSH keys, some user/passwords, etc.) common to
>>> all our instances but we let also the administrators of a Jenkins instance
>>> define their own credential entries.
>>>
>>> However, when the Jenkins instance is restarted, only the credential
>>> entries defined by the CasC files are kept, and all the ones which were
>>> added manually are lost.
>>>
>>> Is there a way to prevent this?
>>>
>>> Thanks,
>>> Damien Coraboeuf
>>>
>> --
> 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/fb5e1d2b-4df3-4950-902d-5f18490b2ea5%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/fb5e1d2b-4df3-4950-902d-5f18490b2ea5%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Nicolas De Loof

-- 
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/CANMVJzn_LpJBVQbjHKGLmF51oAsyWW7E%2BNxng9sB-KCHKtb%2BWQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Migrating to Configuration as Code

[nicolas de loof]

the "export" feature on JENKINS/configuration-as-code page will give you a
yaml file to reflect your current configuration, but this is a very
experimental feature with many limitations, so you can only use it as
inspiration to write your own. Just will make it not as hard as fully
starting from scratch.



Le mar. 18 sept. 2018 à 12:41, Mark Bidewell  a écrit :

> Will there be a pathway to migrate from normal Jenkins configuration to
> Configuration as Code, or will server configuration need to be rewritten
> from scratch?
>
> --
> 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/527e2d7f-0ca2-447b-815e-ce8062cdb751%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/527e2d7f-0ca2-447b-815e-ce8062cdb751%40googlegroups.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Nicolas De Loof

-- 
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%3D31Yq1%3DixnrQAi8pxx-EaVdZoEsFxgikE3xETjcpRhJA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Configuration-as-Code 1.0-RC1 released

[nicolas de loof]

Hi,

The Configuration-as-Code team is proud to announce we published our first
release candidate.
We published a dozen alpha release before, and already got feedback and
contribution from early adopters, so that we are now pretty confident with
current design. We expect to release few more RC so we can get 1.0
production-ready release published in Septembre (just in time for Jenkins
World yeah!)

We welcome any feedbacks to ensure we don't miss any important use case or
compatibility issue before we get 1.0-final. Feel free to join our Gitter
chat <https://gitter.im/jenkinsci/configuration-as-code-plugin> or report
issues <https://github.com/jenkinsci/configuration-as-code-plugin/issues>.

-- 
Nicolas De Loof

-- 
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/CANMVJzmekUORUHbwSudWS7JPxQTXVxMPRfA2%2BRfB0i4qnj0OiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: automating jenkins (master) setup - plugins / extensions and their configs

[nicolas de loof]

init.groovy scripts is a very powerful way to setup jenkins but require to
know jenkins / plugins programmatic API. If you're not a plugin developer
this might be very uncomfortable to write and maintain.

As an alternative, you might be interested in
https://github.com/jenkinsci/configuration-as-code-plugin



2018-04-23 11:02 GMT+02:00 Alex Els :

> Hi there,
>
> I'm trying to create a automated setup of Jenkins masters and am
> struggling with setting up custom plugins, like terraform or docker,
> programatically via groovy scripts in
> init.groovy.d
>
>  are there any good resources on how to do this?
>
> I'm using the Jenkins docker image, which can automatically install all
> the desired plugins, but it's a mystery on how to use groovy init scripts
> to configure any custom installed plugin/extension. I've found resources
> that configure things like maven etc., but nothing that would help me set
> up a "installation" of `terraform` and such ..
>
> How do people on here go about this in general? Just do the clicky thing
> and the put the XML files into Git (minus the passwords, if any, of
> course)? I'd really rather not do that, and use the groovy init scripts
> instead, if at all possible for these cases?
>
> Thanks
> Alex
>
> --
> 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/21149959-9810-47d6-b77e-58bec2c053e2%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/CANMVJzmPBL7xN9_pAX5qTDryecUiypHjDbNVCwqh9KwBsdm%3DVw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [solved] Re: Docker cloud plugin and pipeline using docker

[nicolas de loof]

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/agent" as agent root directory, as this one is a volume and
as such workspace sub-folder will be shareable with other containers.

2018-02-26 5:14 GMT+01:00 Christian Gagneraud <chg...@gmail.com>:

> On 26 February 2018 at 15:29, Christian Gagneraud <chg...@gmail.com>
> wrote:
> > On 26 February 2018 at 03:10, nicolas de loof <nicolas.del...@gmail.com>
> 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 be configured with /var/run/docker.sock (so, the one from
> B)
> >> bind mounted. Doing so it can then create some side container to host
> the
> >> build steps.
> >
> > Hi Nicolas,
> >
> > Thanks for the tips, i think i'm getting there, but i'm still missing
> some bits:
> > - I have created a docker image based on jenkinsci/jnlp-slave, the
> > only customisation is installing docker in it
> > - The pipeline now get checkout inside tmy slave (on machine B)
> > - The docker image from the Jenkinsfile is pulled and executed.
> >
> > But i get this weird error (see full log at the end of this email):
> > 
> > docker-44734997459c on work-leader seems to be running inside
> > container e7f7a4381e32c456b806695b9b7334751d88f1a3985867bb964e9fd3d2e8
> c948
> > but /home/jenkins/workspace/aa_aaa_master-GQ43GQETZSZCK3GMCGYSLEW5TKL7YK
> HSBXYJPJLEX7A2AM6K5M6Q
> > could not be found among [/home/jenkins/.jenkins, /home/jenkins/agent]
>
> Google didn't return much with "could not be found among"
>
> https://stackoverflow.com/questions/47559469/jenkins-
> declarative-pipeline-docker-agent-timeout-run?rq=1
> https://tutel.me/c/programming/questions/46530963/run+jenkins+agent+in+
> docker+container+issue+with+jenkins+pipeline+and+varrundockersocket
>
> Not very useful, but using google's "repeat the search with the
> omitted results included.", I got a few extra results, one of them, an
> IRD log, that gave me the answer:
> https://echelog.com/logs/browse/jenkins/1497304800
>
> I had to add /home/jenkins in the "Volumes" of the "Docker Agent
> templates" (as well as "Remoting Filling System Root", but this was
> set by default).
> I noticed as well that if no "user" is specified in the "Connect
> method"/"Attach Docker Container", the Python image script will be run
> with id 1000:1000, which does not exists. But this doesn't seem to be
> a problem. (user=root is not required, nor is "Run container
> privileged").
>
> Thanks!
> Chris
>
> --
> 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/CABxGUTjm_P7nc0pk2WntGjq1BX2Eoacn6tD9xqw
> skjLpxg2_ZA%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/CANMVJz%3DL%3DP3ZGcPTEdEJi2eEfyM1Su-0sHDUoPQHN95qrHcAuA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker cloud plugin and pipeline using docker

[nicolas de loof]

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 be configured with /var/run/docker.sock (so, the one
from B) bind mounted. Doing so it can then create some side container to
host the build steps.

2018-02-25 11:16 GMT+01:00 Christian Gagneraud :

> 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
> "docker-workflow v1.15" plugin.
>
> Ignoring machine B (for now), my setup is working:
> - 1. A dev open a pull-request on bitbucket
> - 2. The declarative pipline is executed by jenkins
> - 3. The docker container(s) specified in the Jenkinsfile are executed
> by machine A
> - 4. The pipeline finished
> - 5. Jenkins notify Bitbucket.
>
> From a docker point of view, for the above to work, I simply need to
> run the Jenkins container with --volume
> /var/run/docker.sock:/var/run/docker.sock
>
> Now, I would like to achieve 3 things:
> - Leave machine A runs non-build services only
> - Use machine B to spawn containers as directed by declarative pipelines.
> - Eventually make machine B a docker swarm manager, and let other
> docker swarm workers join in if/when needed.
>
> The first modification I did to the jenkins container is to remove the
> "/var/run/docker.sock" volume. This is to make sure jenkins can only
> talk to the remote docker I configure.
>
> I have then tried 3 plugins:
> - "docker plugin" https://plugins.jenkins.io/docker-plugin
> - "docker swarm" https://plugins.jenkins.io/docker-swarm
> - "Yet another docker plugin"
> https://plugins.jenkins.io/yet-another-docker-plugin
>
> All of them add a type of "cloud providers", but I never managed to
> get my pipeline executed using one.
>
> The "docker plugin" is the only one that gave me the feeling I was almost
> there:
> The job was handled by a docker container spawn on machine B, which i
> had to specify the image name (From examples and tutorials, i settled
> down on "jenkinsci/jnlp-slave" in "Launch attached" mode).
> But at that stage, I got an error "docker: command not found" emitted
> from the jnlp-slave container.
> The reason being that Jenkins master contacted docker on machine B to
> execute a "jenkinsci/jnlp-slave", and then ask this
> "jenkinsci/jnlp-slave" to execute the pipeline, which is an operation
> that requires to instantiate the docker containers specified in the
> project's pipeline...
>
> So I would like to know if the "docker-plugin" is the right tool for
> my job or should I head in another direction.
> In case "docker-plugin" is the way to go, then how do I tell my
> customised jnlp-slave to connect to the right docker daemon? Is there
> an off-the-shelf docker image to play that role? I couldn't find
> documentation on how to create it, and the specificites of having
> docker inside it.
>
> As a side note:
> I found a bit inefficient to have to instantiate Jenkins slave
> container whose sole purpose is to read the pipeline and spawn
> containers as directed by the pipeline.
> Ideally I would like the pipeline to be parsed by Machine A (jenkins
> master) and the required containers to be executed on machine B, I do
> not know if volumes (jenkins workspace) can be shared across 2 docker
> daemons thought...
>
> Any opinion or advice are very welcome, point-out of any sort would be
> greatly appreciated too.
>
> Thanks,
> Chris
>
> --
> 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/CABxGUTgbu2BPOO1MRcPVPaxqqGhe3
> 06kU_LBAWf3H2jO2RooFA%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/CANMVJz%3DSW65OKUj7pK9xbdSjZGegEySRXTY8BfrnsmLoVNFmzQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker Plugin - Jenkins doesn't have label....

[nicolas de loof]

JENKINS-48490 is not implemented in jenkins-core but docker-plugin, and
should be fixed in 1.1.2

2017-12-19 16:18 GMT+01:00 Mandy Hubbard <mandy.hubb...@gmail.com>:

> JENKINS-48490 is fixed in 2.89.1.  I upgraded to 2.89.1 and am still
> seeing the issue.  I plan to open a new defect for this.
>
> On Monday, December 11, 2017 at 5:32:05 PM UTC-6, Mandy Hubbard wrote:
>>
>> Thanks for the reply, Nicolas.  Can't say it is the response I was hoping
>> for but at least I know it's not just me.  I've had it working many times
>> before so I knew I had configured it correctly.  Any hints for working
>> around this for now?  I tried restarting Jenkins but it didn't help.
>>
>> On Monday, December 11, 2017 at 2:24:08 PM UTC-6, nicolas de loof wrote:
>>>
>>> sounds to me this is more or less https://issues.jenkins-ci
>>> .org/browse/JENKINS-48490
>>> which is a recurrent issue. Still looking for a definitive fix
>>>
>>>
>>> 2017-12-11 17:49 GMT+01:00 Mandy Hubbard <mandy@gmail.com>:
>>>
>>>> Using the Docker Plugin to run Jenkins agents in containers, I often
>>>> get the error "Jenkins doesn't have label " even when I have
>>>> the template configured properly and the Docker image is already present on
>>>> the Docker host.  I have sometimes been able to fix it by removing the
>>>> image and re-pulling it to the host but at other times I am completely
>>>> stuck.  I've tried it using a tag and with no tag.  Has anyone else run
>>>> into this?  Do you have any hints on what it could be?
>>>>
>>>> Job run log says:
>>>>
>>>> Still waiting to schedule task
>>>> Jenkins doesn’t have label python
>>>>
>>>>
>>>> Here's my docker image
>>>> jenkins@b1e2e4c28dbd:/$ docker images
>>>> REPOSITORY  TAG IMAGE ID
>>>> CREATED SIZE
>>>> devmandy/python-jenkins-agent   1   6cc6f98875bc2 
>>>> hours ago 991MB
>>>>
>>>> A screenshot of my Jenkins config is attached.
>>>>
>>>>
>>>> --
>>>> 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/ms
>>>> gid/jenkinsci-users/bd8e173f-844b-4b48-9ba6-56df650b0868%
>>>> 40googlegroups.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/bd8e173f-844b-4b48-9ba6-56df650b0868%40googlegroups.com?utm_medium=email_source=footer>
>>>> .
>>>> 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/82b914ce-695e-47ba-aaac-041afcc6a7f6%40googlegroups.
> com
> <https://groups.google.com/d/msgid/jenkinsci-users/82b914ce-695e-47ba-aaac-041afcc6a7f6%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> 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/CANMVJzkxq_052LsywxdfaQVfqMT5R4Gb9tPUya2SGymxTcnX-A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker Plugin - Jenkins doesn't have label....

[nicolas de loof]

sounds to me this is more or less
https://issues.jenkins-ci.org/browse/JENKINS-48490
which is a recurrent issue. Still looking for a definitive fix


2017-12-11 17:49 GMT+01:00 Mandy Hubbard :

> Using the Docker Plugin to run Jenkins agents in containers, I often get
> the error "Jenkins doesn't have label " even when I have the
> template configured properly and the Docker image is already present on the
> Docker host.  I have sometimes been able to fix it by removing the image
> and re-pulling it to the host but at other times I am completely stuck.
> I've tried it using a tag and with no tag.  Has anyone else run into this?
> Do you have any hints on what it could be?
>
> Job run log says:
>
> Still waiting to schedule task
> Jenkins doesn’t have label python
>
>
> Here's my docker image
> jenkins@b1e2e4c28dbd:/$ docker images
> REPOSITORY  TAG IMAGE ID
> CREATED SIZE
> devmandy/python-jenkins-agent   1   6cc6f98875bc2 
> hours ago 991MB
>
> A screenshot of my Jenkins config is attached.
>
>
> --
> 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/bd8e173f-844b-4b48-9ba6-56df650b0868%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/CANMVJzkUHEdFPm4XArk-JOezQChKoWEzOm4kAJ2ZR-Q_pBWx0Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins and HA

[nicolas de loof]

CloudBees HA is indeed based on active/passive master, there's no support
for mutli-active-masters (yet, I don't know the roadmap for this)

2017-12-05 10:31 GMT+01:00 Walter Heestermans <walter.heesterm...@gmail.com>
:

> Are you saying that even with CloudBees you have active/passive masters,
> but can you have multiple masters active too? Or is this not the setup of
> masters?
>
>
> Op dinsdag 5 december 2017 10:26:42 UTC+1 schreef nicolas de loof:
>
>> #disclaimer I'm working by CloudBees
>> CloudBees indeed has such a HA solution based on active/passive jenkins
>> masters.
>>
>> I don't know if there's another mature alternative, haven't really
>> searched for it nor tested.
>> You might be interested by http://www.voleg.info/jenkins-
>> ha-cluster-centos-drbd-pacemaker-kvm.html
>>
>> 2017-12-05 10:17 GMT+01:00 Walter Heestermans <walter.he...@gmail.com>:
>>
>>> So, we have to go to solutions like CloudBees? Other solutions available
>>> for HA and to look at?
>>>
>>>
>>> Op dinsdag 5 december 2017 10:13:27 UTC+1 schreef nicolas de loof:
>>>
>>>> you can't do this way, two masters sharing same JENKINS_HOME would
>>>> override each other configuration on disk. Jenkins is designed as a
>>>> single-instance server.
>>>>
>>>> 2017-12-05 8:30 GMT+01:00 Walter Heestermans <walter.he...@gmail.com>:
>>>>
>>>>> Hi,
>>>>>
>>>>> How can setup HA with Jenkins OpenSource? I have now one master
>>>>> running and two agents, can I just add a second master and put an LB in
>>>>> front of it. The Jenkins home of my current master is on shared file 
>>>>> system.
>>>>>
>>>>> Regards
>>>>> walter
>>>>>
>>>>> --
>>>>> 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/b5b3b249-
>>>>> 8ad8-4cb2-9282-706b707a373e%40googlegroups.com
>>>>> <https://groups.google.com/d/msgid/jenkinsci-users/b5b3b249-8ad8-4cb2-9282-706b707a373e%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>> 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-use...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-users/c9b8fb81-09d6-4295-9218-2c3252fa8749%
>>> 40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/c9b8fb81-09d6-4295-9218-2c3252fa8749%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>> 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/4a7acc8d-f2e4-4e07-b8cf-8e23502a2f89%40googlegroups.
> com
> <https://groups.google.com/d/msgid/jenkinsci-users/4a7acc8d-f2e4-4e07-b8cf-8e23502a2f89%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> 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/CANMVJzk56LspAbAefQOux2n8TgBwOBY0UeX53PfqxejwJSO-2g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins and HA

[nicolas de loof]

#disclaimer I'm working by CloudBees
CloudBees indeed has such a HA solution based on active/passive jenkins
masters.

I don't know if there's another mature alternative, haven't really searched
for it nor tested.
You might be interested by
http://www.voleg.info/jenkins-ha-cluster-centos-drbd-pacemaker-kvm.html

2017-12-05 10:17 GMT+01:00 Walter Heestermans <walter.heesterm...@gmail.com>
:

> So, we have to go to solutions like CloudBees? Other solutions available
> for HA and to look at?
>
>
> Op dinsdag 5 december 2017 10:13:27 UTC+1 schreef nicolas de loof:
>
>> you can't do this way, two masters sharing same JENKINS_HOME would
>> override each other configuration on disk. Jenkins is designed as a
>> single-instance server.
>>
>> 2017-12-05 8:30 GMT+01:00 Walter Heestermans <walter.he...@gmail.com>:
>>
>>> Hi,
>>>
>>> How can setup HA with Jenkins OpenSource? I have now one master running
>>> and two agents, can I just add a second master and put an LB in front of
>>> it. The Jenkins home of my current master is on shared file system.
>>>
>>> Regards
>>> walter
>>>
>>> --
>>> 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/ms
>>> gid/jenkinsci-users/b5b3b249-8ad8-4cb2-9282-706b707a373e%
>>> 40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/b5b3b249-8ad8-4cb2-9282-706b707a373e%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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/c9b8fb81-09d6-4295-9218-2c3252fa8749%40googlegroups.
> com
> <https://groups.google.com/d/msgid/jenkinsci-users/c9b8fb81-09d6-4295-9218-2c3252fa8749%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> 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/CANMVJznYs1tO3UeUkEpAgJVVP5t%2B%2Bdr%2BOaog9%3DttegPtyyOHtA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins and HA

[nicolas de loof]

you can't do this way, two masters sharing same JENKINS_HOME would override
each other configuration on disk. Jenkins is designed as a single-instance
server.

2017-12-05 8:30 GMT+01:00 Walter Heestermans :

> Hi,
>
> How can setup HA with Jenkins OpenSource? I have now one master running
> and two agents, can I just add a second master and put an LB in front of
> it. The Jenkins home of my current master is on shared file system.
>
> Regards
> walter
>
> --
> 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/b5b3b249-8ad8-4cb2-9282-706b707a373e%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/CANMVJzk-gjEracC0F_DqrubodZ_o67%3Dn4CSgcPV6PHfxObxhiQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build Docker Image from a Dockerized Jenkins

[nicolas de loof]

2017-12-04 21:38 GMT+01:00 Jacob Larsen <ja...@larsen.net>:

> Here is a list of the options I know, but one important aspect to this is
> if you use pipeline or not in your builds as that affects your choices:
>
> Docker Custom Build Environment Plugin. This will use an existing executor
> to launch a container with the build. The images used need not be aware of
> Jenkins or dependencies. When I looked at it, it seemed abandoned, but it
> looks like someone is trying to pick it up again. It will probably take
> some time before it is up to date with new docker and Jenkins features.
> E.g. last I checked, pipeline was not supported. Also, it only works from
> physical Jenkins nodes.
>
pipeline is not supported by this plugin as the exact equivalent (even code
is a re-implementation) is docker-pipeline's "inside".


> Docker Slaves Plugin. This will provision slave containers on the fly from
> a single Docker host. Images need not be aware of Jenkins or dependencies.
> Limit on containers launched did not work for pipeline jobs last I checked.
> Also, this only works on a single Docker host.
>
docker-slaves-plugin do NOT require image to be aware of Jenkins or
dependencies, you can use arbitrary docker image, even without a JDK. This
was one initial goal of this plugin.

Docker Pipeline Plugin https://plugins.jenkins.io/docker-workflow. I just
> learned about this one from the previous message, but looking at the
> adoption rate, this must be the mainstream option. Odds are this would be
> your best bet to start, provided you are using pipeline.
>
> Using a build wrapper like SCUBA: https://github.com/
> JonathonReinhart/scuba in a shell step. This has the benefit of enabling
> manual/development builds to use the same steps as the automated Jenkins
> builds. For that particular wrapper, it does not support running from
> inside a container and creating sibling containers. I am considering a PR
> for that, but I think there are other wrappers that might support something
> like this.
>
> There are plugins that dynamically provision slaves from images and run
> builds on those. The common drawback for these would be that the images
> themselves must support running a jenkins Slave, e.g. have a Java runtime
> of a certain version installed.
>
> /Jacob
>
> On 2017-12-04 17:37, Jeeva Chelladhurai wrote:
>
> I would like to run my builds inside docker, so that I can manage
> different run times like node, python, go thru docker images.
>
> - Jeeva
>
> On Mon, Dec 4, 2017 at 5:51 PM, nicolas de loof <nicolas.del...@gmail.com>
> wrote:
>
>> (another) plugin of mines.
>> Same design as docker-pipeline's "docker.inside"
>>
>> Can you please describe your use-case so we give better advise ?
>>
>> if you just want to "build Docker images" as your initial message told,
>> then just run "docker build" within your job, what else ?
>>
>> 2017-12-04 13:15 GMT+01:00 Jeeva Chelladhurai <sje...@gmail.com>:
>>
>>> Any  thoughts on https://wiki.jenkins.io/displa
>>> y/JENKINS/CloudBees+Docker+Custom+Build+Environment+Plugin
>>>
>>> On Mon, Dec 4, 2017 at 12:04 PM, Jeeva Chelladhurai <sje...@gmail.com>
>>> wrote:
>>>
>>>>
>>>>
>>>>> I have not tried this, so, cannot vouch for this. Please be cautious
>>>>> about the approach presented in this blog.
>>>>>
>>>>> http://niels.nu/blog/2017/continuous-blog-delivery-p2.html : you
>>>>> might be interested in Docker-in-Docker.
>>>>>
>>>>>
>>>>> Thanks for the suggestion.. Docker-in-Docker is been discouraged here
>>>> is good read on it https://jpetazzo.github.io/
>>>> 2015/09/03/do-not-use-docker-in-docker-for-ci/
>>>>
>>>> - Jeeva
>>>>
>>>
>>>
>>>
>>> --
>>> Jeeva K S Chelladhurai
>>>
>>> --
>>> 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/ms
>>> gid/jenkinsci-users/CAK5CbZVSDwjOAUe_uB_u89GRufSrbk2MyeUzSHz
>>> 9w88K6af0QA%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAK5CbZVSDwjOAUe_uB_u89GRufSrbk2MyeUzSHz9w88K6af0QA%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>>> For more options, visi

Re: Build Docker Image from a Dockerized Jenkins

[nicolas de loof]

ok, so for this purpose you can rely on docker-plugin to create agents
on-demand from configured docker images, or docker-slaves-plugin if you
want this configured directly within your jobs, and docker-pipeline
"inside" if you prefer Jenkinsfiles to setup CI/CD in jenkins.

2017-12-04 17:37 GMT+01:00 Jeeva Chelladhurai <sje...@gmail.com>:

> I would like to run my builds inside docker, so that I can manage
> different run times like node, python, go thru docker images.
>
> - Jeeva
>
> On Mon, Dec 4, 2017 at 5:51 PM, nicolas de loof <nicolas.del...@gmail.com>
> wrote:
>
>> (another) plugin of mines.
>> Same design as docker-pipeline's "docker.inside"
>>
>> Can you please describe your use-case so we give better advise ?
>>
>> if you just want to "build Docker images" as your initial message told,
>> then just run "docker build" within your job, what else ?
>>
>> 2017-12-04 13:15 GMT+01:00 Jeeva Chelladhurai <sje...@gmail.com>:
>>
>>> Any  thoughts on https://wiki.jenkins.io/displa
>>> y/JENKINS/CloudBees+Docker+Custom+Build+Environment+Plugin
>>>
>>> On Mon, Dec 4, 2017 at 12:04 PM, Jeeva Chelladhurai <sje...@gmail.com>
>>> wrote:
>>>
>>>>
>>>>
>>>>> I have not tried this, so, cannot vouch for this. Please be cautious
>>>>> about the approach presented in this blog.
>>>>>
>>>>> http://niels.nu/blog/2017/continuous-blog-delivery-p2.html : you
>>>>> might be interested in Docker-in-Docker.
>>>>>
>>>>>
>>>>> Thanks for the suggestion.. Docker-in-Docker is been discouraged here
>>>> is good read on it https://jpetazzo.github.io/
>>>> 2015/09/03/do-not-use-docker-in-docker-for-ci/
>>>>
>>>> - Jeeva
>>>>
>>>
>>>
>>>
>>> --
>>> Jeeva K S Chelladhurai
>>>
>>> --
>>> 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/ms
>>> gid/jenkinsci-users/CAK5CbZVSDwjOAUe_uB_u89GRufSrbk2MyeUzSHz
>>> 9w88K6af0QA%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAK5CbZVSDwjOAUe_uB_u89GRufSrbk2MyeUzSHz9w88K6af0QA%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>>> 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/ms
>> gid/jenkinsci-users/CANMVJznKg%3DXKpeaT62PVkmEvLh4kruCyc1HV%
>> 2BQGFNtnjLhX%3DLQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CANMVJznKg%3DXKpeaT62PVkmEvLh4kruCyc1HV%2BQGFNtnjLhX%3DLQ%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Jeeva K S Chelladhurai
>
> --
> 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/CAK5CbZVoig-s%3DvfVi5SEcrLVjBwZ5-0danHP-X54_
> CogRT9n0Q%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAK5CbZVoig-s%3DvfVi5SEcrLVjBwZ5-0danHP-X54_CogRT9n0Q%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> 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/CANMVJznagKiHR4qPv6%2BCBJ-N%3DJ6Q%3Dj6ZDspYtWLGEnNDcP-bSQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build Docker Image from a Dockerized Jenkins

[nicolas de loof]

(another) plugin of mines.
Same design as docker-pipeline's "docker.inside"

Can you please describe your use-case so we give better advise ?

if you just want to "build Docker images" as your initial message told,
then just run "docker build" within your job, what else ?

2017-12-04 13:15 GMT+01:00 Jeeva Chelladhurai :

> Any  thoughts on https://wiki.jenkins.io/display/JENKINS/CloudBees+
> Docker+Custom+Build+Environment+Plugin
>
> On Mon, Dec 4, 2017 at 12:04 PM, Jeeva Chelladhurai 
> wrote:
>
>>
>>
>>> I have not tried this, so, cannot vouch for this. Please be cautious
>>> about the approach presented in this blog.
>>>
>>> http://niels.nu/blog/2017/continuous-blog-delivery-p2.html : you might
>>> be interested in Docker-in-Docker.
>>>
>>>
>>> Thanks for the suggestion.. Docker-in-Docker is been discouraged here is
>> good read on it https://jpetazzo.github.io/2015/09/03/do-not-use-docker-i
>> n-docker-for-ci/
>>
>> - Jeeva
>>
>
>
>
> --
> Jeeva K S Chelladhurai
>
> --
> 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/CAK5CbZVSDwjOAUe_uB_u89GRufSrbk2MyeUzSHz9w88K6af0Q
> A%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/CANMVJznKg%3DXKpeaT62PVkmEvLh4kruCyc1HV%2BQGFNtnjLhX%3DLQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build Docker Image from a Dockerized Jenkins

[nicolas de loof]

There's no "recommended" solution, each plugin comes with it's own vision,
benefits and drawbacks.

docker-plugin can be used to run dockerized agents, it can run from a
dockerized jenkins master with /var/run/docker.sock without docker CLI
installed, as it uses a java client library for docker API.
docker-slaves-plugin do rely on running docker CLI executed from master, I
planned to use a java API at some point but still need to work on this. In
the meantime I don't think there's a simple way to just install docker CLI.
Installing full docker will make your image a bit bigger with additional
files on filesystem but there won't be any extra process running, so not a
major issue (considering jenkins docker image is already a big one)

2017-12-03 18:42 GMT+01:00 Jeeva Chelladhurai :

> Hello All,
>
> I would like to build Docker images from a Dockerized Jenkins. There are
> multiple solution out there but what is the recommended solution...
>
> I have been using ssh node as a work around, but I was told to use
> https://wiki.jenkins.io/display/JENKINS/Docker+Slaves+Plugin . In order
> for this plugin to work, I have to install docker inside the Jenkins (my
> docker host is RHEL) and also mount the /var/run/docker.sock or enable
> TLS. Isn't installing docker blow up the size of the Jenkins image?
>
> Any way to install just the docker client in side the Jenkins image?
>
> Thanks,
> Jeeva
>
> --
> Jeeva K S Chelladhurai
>
> --
> 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/CAK5CbZV3Sc-fgYS_34PgEwRzsF20%
> 3Dp6mbaagbR2Ehtz01op2%3Dw%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/CANMVJzk7GJDmKUKQNvt4PzLpXHtTp%2B7BnikYfeysX7_kdpxcUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: docker jenkinsci/ssh-slave volumes

[nicolas de loof]

This is to make it clear where (potentially) persistent data should live,
the rest of the container being fully transient.

Le 28 nov. 2017 1:41 PM,  a écrit :

> Hi,
> I would like to know the utility of the "volume" command in
> jenkinsci/ssh-slave docker file :
> https://hub.docker.com/r/jenkinsci/ssh-slave/~/dockerfile/
>
> Is it for performance reasons like explained in :
> https://docs.docker.com/engine/admin/volumes/
>
> or is it necessary for some other reasons ?
>
> Thanks by advance.
>
> --
> 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/6c36-1cb5-4636-a6cc-d2b2901e0470%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/CANMVJzkp3SJQUf-HdVFYdv%3D3it-N7DSu_LD6TBxzi06vUD%3DduQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Provisioning Docker Containers on a Remote Host Using Jenkins Master

[nicolas de loof]

Please give more details on what you want to do with this remote machine.

I assume you want to use it as a Jenkins agent to host build, not running
on your master node. Then using docker plugin you can configure a "cloud"
to access this remote Docker API (with adequate TLS keys registered as
credentials) and define an agent template so your builds can allocate a
transient build agent on this remote node. You'll need to define a label in
this template so your job are configured with this label, and Jenkins knows
they are supposed to run here.

2017-11-25 12:50 GMT+01:00 Sujeet Kumar Padhi :

> I have Docker Engine installed on an Ubuntu 14.04 LTS Server. I have
> activated the Docker API as well by making some changes to the config files
> and I am able to access the APIs.
>
> I have jenkins installed on another Ubuntu 14.04 server.
>
> Can somebody please help me with the steps to build/run images on the
> remote docker server with the help if Jenkins.
> I am not able to find any proper steps or plugin present in Jenkins to run
> the Docker commands remotely.
>
> --
> 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/865e9f0e-c178-4a4f-a4ee-504faf1c94b4%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/CANMVJzneQAPVMTPhet%3DBBu8H27u0_Gb3tWDf7766ExSk8jv1Gw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: cloud docker give options to java command

[nicolas de loof]

just use the "JVM Options" parameter for this launcher (in advanced options)

2017-11-24 11:09 GMT+01:00 <pi.quiro...@gmail.com>:

> I'm using ssh launch mechanism with ssh credentials.
> I would like to pass -xmx argument to the java command launching jenkins
> to limit the memory used by my jenkins nodes.
>
>
>
> Le jeudi 23 novembre 2017 18:52:22 UTC+1, nicolas de loof a écrit :
>>
>> it depends the docker agent template "launch" mechanism you're using.
>> Can you please describe your use-case ? Which argument do you want to
>> pass to the jenkins remote agent ?
>>
>> 2017-11-23 15:50 GMT+01:00 <pi.qu...@gmail.com>:
>>
>>> Hi,
>>> how could I give an option to the java command launching jenkins in a slave 
>>> :
>>> java  -jar slave.jar
>>>
>>> Is it possible with Jenkins/configuration "Cloud/Docker/Docker agent 
>>> templates/Container settings" ?
>>>
>>> --
>>> 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/ms
>>> gid/jenkinsci-users/0366d397-a6d9-4259-9ae8-e6276f3e18a0%40g
>>> ooglegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/0366d397-a6d9-4259-9ae8-e6276f3e18a0%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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/ms
> gid/jenkinsci-users/d92d8aa9-1ef8-416d-aaa8-c1c6bd1e6488%
> 40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/d92d8aa9-1ef8-416d-aaa8-c1c6bd1e6488%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> 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/CANMVJznjJCpXkAqZsDHMPhVT9f4vd1C7HaFbnQP1mLYTgqPAbg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: cloud docker give options to java command

[nicolas de loof]

it depends the docker agent template "launch" mechanism you're using.
Can you please describe your use-case ? Which argument do you want to pass
to the jenkins remote agent ?

2017-11-23 15:50 GMT+01:00 :

> Hi,
> how could I give an option to the java command launching jenkins in a slave :
> java  -jar slave.jar
>
> Is it possible with Jenkins/configuration "Cloud/Docker/Docker agent 
> templates/Container settings" ?
>
> --
> 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/0366d397-a6d9-4259-9ae8-e6276f3e18a0%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/CANMVJzm07D986aMoHoaKPDH%2BiLm2vSU7rqct1dKoMfNAQYyGKA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker plugin. How to manage concurrent builds/volumes

[nicolas de loof]

2017-11-02 22:55 GMT+01:00 Ryan Hochstetler :

> Kris,
>
> I tried to travel down the same road, mounting a volume with the workspace
> directory into the slave containers as well as the master in order to
> expose the workspace contents post-build.  The *jenkins way* to provide
> developer-visibility into workspace contents seems to be committing the
> container so that the team can pull the resulting image and view the
> contents there.  That's pretty slick, but essentially requires me to teach
> hundreds of colleagues *how to docker *(and suffer their questions about
> why it can't work the way it used to work in the meantime).
>

That's indeed a feature the docker-plugin provides and I totally dislike
this approach. A local volume for the workspace would be a way better
approach, and one could browse it's content from UI by running an ephemeral
jenkins agent. Offering this option is on my todo-list for 1.1

Same for dependency cache : a local volume could be used to store this
cache a retrieve it for subsequent builds (just like circle CI does
).

Main issue is we don't know the job to run on a docker agent as it get
provisioned. This is by design of the Cloud API, which was designed for
long-running VMs, not containers one can create and drop within a second.
My plan is to adopt an approach comparable to one-shot-executor
 (or maybe just
use this plugin, but there's few things I have to fix) so that a Docker
Agent is tied to a specific item in build queue so we know about it and can
decide a volume to use as workspace based (for sample) on job's name
checksum, or something comparable.



>
> Given that this post is pretty dusty, I'm hoping you got past your
> problem.  Mind posting back here to summarize your solution?
>
> On Tuesday, December 8, 2015 at 10:39:25 AM UTC-6, Kris Massey wrote:
>>
>> Hi All,
>>
>> I'm new to Docker, so thought I'd attempt to setup Jenkins with slaves
>> that are Docker containers. The software we build used gradle as the build
>> tool, and I've git a few issues. Below is a overview of where I am, however
>> I'm struggling to progress to the next stage
>>
>> Current Situation:
>>
>> Jenkins - Running on a standalone VM (may put into Docker at a later
>> date)
>>
>>- Docker plugin to start/stop containers for builds
>>- At the moment build steps are just to echo something into a file
>>
>>
>> Slaves - Docker images
>>
>>- Jenkins starts the image does whats needed and then stops
>>the container
>>- *Issue* - the container is left behind...is there anyway to
>>automate removal of the containers from within Jenkins?
>>
>>
>> The next issues I have are:
>>
>>- How to mount the workspace into the container.
>>   - The issue I'm having here is that we start X slaves, so if I
>>   mount the Jenkins master workspace onto the slave. Each slave will end 
>> up
>>   pointing to the same folder on the host trampling all over each other
>>   - Another issue here is, the project uses Gradle so it would be
>>   nice to attempt to reload/retain the gradle wrapper and dependency 
>> caches.
>>- Extract build results (JUnit etc)
>>   - By solving the issue above this could be resolved
>>
>>
>> So I guess summed up my question is, how should the file system be
>> managed when using Docker containers as Jenkins Slaves? Any thoughts or how
>> youve implemented things would be great.
>>
>> Thanks,
>> Kris
>>
> --
> 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/95857ff9-f7f0-4ab0-a570-de8922894112%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/CANMVJzk%3DaFi%3DfP6otO92seeYDWSFPMowAb1uJYL%3De9ZkjEHDHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Does Docker Slave Plugin support Pipeline Maven Integration Plugin?

[nicolas de loof]

I can't tell, best to give it a try and report any issue you encounter
doing this.

Le 2 nov. 2017 1:41 PM, "'Sandra Parsick' via Jenkins Users" <
jenkinsci-users@googlegroups.com> a écrit :

>
> ...

-- 
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/CANMVJzmD02Uj56Jgdn_PU-vz-vPtP7M3FE-dWFudDCjon4mFXA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker-plugin - ssh connection refused when connecting to slave

[nicolas de loof]

thanks for reporting this. Most probably I've only ran tests for various
launchers only once :P

2017-10-20 17:05 GMT+02:00 Martin Heg <seola...@gmail.com>:

> Sounds good - if it helps with your analysis I've noticed that first build
> after a restart always seems to work fine with the executor being destroyed
> correctly. Subsequent builds then suffer from the 'offline'/non-terminated
> executor.
> Thanks.
>
> On 20 October 2017 at 15:59, nicolas de loof <nicolas.del...@gmail.com>
> wrote:
>
>> looks like the build termination isn't successfully caught to terminate
>> this node.
>> I'm trying to stabilize the "launch" mechanism in 1.0.x, then will try to
>> address the more general lifecycle for docker agents, being created as a
>> task enter the queue and destroyed on completion. My experiments on
>> one-shot-executor give me some ideas on how to improve this process without
>> being too much hack-ish :D
>>
>> 2017-10-20 16:16 GMT+02:00 Martin Heg <seola...@gmail.com>:
>>
>>> Aha - yes I have 'Docker Host URI' set to 'unix:///var/run/docker.sock',
>>> but what I was probably missing was to set the 'Docker Hostname' under the
>>> Advanced section in the Cloud settings... once I set that to the ip address
>>> of the docker host I am having some more success...
>>>
>>> Now slave containers are being spawned and builds are running in them
>>> :), but all is not quite right..
>>>
>>> Even though the container is created and destroyed after the build the
>>> UI is still showing the 'node' as offline. See attached screenshot.
>>>
>>> Looking at the log for any of these shows that the docker host ip
>>> address is now being used for routing instead of 0.0.0.0 but the log still
>>> shows the 'connection refused' error... (I've masked out ip address in the
>>> paste below)..
>>>
>>> Despite this error, the build history for the node shows that it ran the
>>> build successfully..
>>>
>>> *[10/20/17 14:06:44] [SSH] Opening SSH connection to 10.x.x.x:32842.
>>> Connection refused (Connection refused)
>>> SSH Connection failed with IOException: "Connection refused (Connection 
>>> refused)".
>>> java.io.IOException: There was a problem while connecting to 10.x.x.x:32842
>>> at com.trilead.ssh2.Connection.co 
>>> <http://com.trilead.ssh2.Connection.co>nnect(Connection.java:834)
>>> at com.trilead.ssh2.Connection.co 
>>> <http://com.trilead.ssh2.Connection.co>nnect(Connection.java:703)
>>> at com.trilead.ssh2.Connection.co 
>>> <http://com.trilead.ssh2.Connection.co>nnect(Connection.java:617)
>>> at 
>>> hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1284)
>>> at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:804)
>>> at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:793)
>>> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>> at 
>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>> at 
>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>> at java.lang.Thread.run(Thread.java:748)
>>> Caused by: java.net.ConnectException: Connection refused (Connection 
>>> refused)
>>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>>> at java.net 
>>> <http://java.net>.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
>>> at java.net 
>>> <http://java.net>.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
>>> at java.net 
>>> <http://java.net>.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
>>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>>> at java.net.Socket.connect(Socket.java:589)
>>> at 
>>> com.trilead.ssh2.transport.TransportManager.establishConnection(TransportManager.java:367)
>>> at 
>>> com.trilead.ssh2.transport.TransportManager.initialize(TransportManager.java:480)
>>> at com.trilead.ssh2.Connection.co 
>>> <http://com.trilead.ssh2.Connection.co>nnect(Connection.java:774)
>>> ... 9 more
>>> [10/20/17 14:06:44] Launch failed - cleaning up connection
>>> [10/20/17 14:06:44] [SSH] Connection closed.*
>>>
>>>
>>>
>>>
>>> Thank you so much for your help Nicolas.
>>>
>>> On

Re: Docker-plugin - ssh connection refused when connecting to slave

[nicolas de loof]

looks like the build termination isn't successfully caught to terminate
this node.
I'm trying to stabilize the "launch" mechanism in 1.0.x, then will try to
address the more general lifecycle for docker agents, being created as a
task enter the queue and destroyed on completion. My experiments on
one-shot-executor give me some ideas on how to improve this process without
being too much hack-ish :D

2017-10-20 16:16 GMT+02:00 Martin Heg <seola...@gmail.com>:

> Aha - yes I have 'Docker Host URI' set to 'unix:///var/run/docker.sock',
> but what I was probably missing was to set the 'Docker Hostname' under the
> Advanced section in the Cloud settings... once I set that to the ip address
> of the docker host I am having some more success...
>
> Now slave containers are being spawned and builds are running in them :),
> but all is not quite right..
>
> Even though the container is created and destroyed after the build the UI
> is still showing the 'node' as offline. See attached screenshot.
>
> Looking at the log for any of these shows that the docker host ip address
> is now being used for routing instead of 0.0.0.0 but the log still shows
> the 'connection refused' error... (I've masked out ip address in the paste
> below)..
>
> Despite this error, the build history for the node shows that it ran the
> build successfully..
>
> *[10/20/17 14:06:44] [SSH] Opening SSH connection to 10.x.x.x:32842.
> Connection refused (Connection refused)
> SSH Connection failed with IOException: "Connection refused (Connection 
> refused)".
> java.io.IOException: There was a problem while connecting to 10.x.x.x:32842
>   at com.trilead.ssh2.Connection.connect(Connection.java:834)
>   at com.trilead.ssh2.Connection.connect(Connection.java:703)
>   at com.trilead.ssh2.Connection.connect(Connection.java:617)
>   at 
> hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1284)
>   at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:804)
>   at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:793)
>   at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>   at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>   at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>   at java.lang.Thread.run(Thread.java:748)
> Caused by: java.net.ConnectException: Connection refused (Connection refused)
>   at java.net.PlainSocketImpl.socketConnect(Native Method)
>   at java.net 
> <http://java.net>.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
>   at java.net 
> <http://java.net>.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
>   at java.net 
> <http://java.net>.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
>   at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>   at java.net.Socket.connect(Socket.java:589)
>   at 
> com.trilead.ssh2.transport.TransportManager.establishConnection(TransportManager.java:367)
>   at 
> com.trilead.ssh2.transport.TransportManager.initialize(TransportManager.java:480)
>   at com.trilead.ssh2.Connection.connect(Connection.java:774)
>   ... 9 more
> [10/20/17 14:06:44] Launch failed - cleaning up connection
> [10/20/17 14:06:44] [SSH] Connection closed.*
>
>
>
>
> Thank you so much for your help Nicolas.
>
> On 20 October 2017 at 14:11, nicolas de loof <nicolas.del...@gmail.com>
> wrote:
>
>> issue here is 0.0.0.0 (localhost) from jenkins master is a container, not
>> the docker host, so can't connect to ssh slave.
>> I assume you have master to access docker.sock to run this sibling
>> container ? So master has no way to guess the external IP
>>
>> 2017-10-20 14:51 GMT+02:00 Martin Heg <seola...@gmail.com>:
>>
>>> What I should add once more just to clarify is that the slave container
>>> does actually get started (and hence why I am able to try manually ssh-ing
>>> into it) - it stays running for a few minutes and then exits.
>>>
>>>
>>> On 20 October 2017 at 13:34, Martin Heg <seola...@gmail.com> wrote:
>>>
>>>> Frustrating thing is that I definitely had this same exact setup
>>>> working previously (jenkins master in docker container spawning slaves in
>>>> sibling containers), albeit in the context of docker toolbox (boot2docker)
>>>> running on windows, whereas I am now running against standard docker on
>>>> linux.
>>>>
>>>> On 20 October 2017 at 13:25, Martin Heg <seola...@gmail.com> wrote:
>>>

Re: Docker-plugin - ssh connection refused when connecting to slave

[nicolas de loof]

issue here is 0.0.0.0 (localhost) from jenkins master is a container, not
the docker host, so can't connect to ssh slave.
I assume you have master to access docker.sock to run this sibling
container ? So master has no way to guess the external IP

2017-10-20 14:51 GMT+02:00 Martin Heg <seola...@gmail.com>:

> What I should add once more just to clarify is that the slave container
> does actually get started (and hence why I am able to try manually ssh-ing
> into it) - it stays running for a few minutes and then exits.
>
>
> On 20 October 2017 at 13:34, Martin Heg <seola...@gmail.com> wrote:
>
>> Frustrating thing is that I definitely had this same exact setup working
>> previously (jenkins master in docker container spawning slaves in sibling
>> containers), albeit in the context of docker toolbox (boot2docker) running
>> on windows, whereas I am now running against standard docker on linux.
>>
>> On 20 October 2017 at 13:25, Martin Heg <seola...@gmail.com> wrote:
>>
>>> Yes - jenkins master running in container.
>>> From the docker host I can manually ssh into the slave container with:
>>> ssh -p *ephmeral_port* jenkins@0.0.0.0
>>> If I docker exec into the jenkins master I can also ssh into the slave
>>> container using the docker host ip:
>>> ssh -p *ephmeral_port* jenkins@*hostip*
>>>
>>> h.
>>>
>>> On 20 October 2017 at 13:05, nicolas de loof <nicolas.del...@gmail.com>
>>> wrote:
>>>
>>>> Is your jenkins master running in a docker container as well ?
>>>>
>>>> stacktrace seems to demonstrate failure to establish a route to
>>>> 0.0.0.0:32791, even before any SSH authentication attempt
>>>>
>>>> 2017-10-20 12:16 GMT+02:00 Martin Heg <seola...@gmail.com>:
>>>>
>>>>> Thanks for your reply Nicolas. Yes I saw that suggestion in one of
>>>>> your other posts and have already tried it but still seeing the same issue
>>>>> unfortunately.
>>>>>
>>>>> On 20 October 2017 at 11:11, nicolas de loof <nicolas.del...@gmail.com
>>>>> > wrote:
>>>>>
>>>>>> to use your own SSH credentials you need to disable the "SSH key
>>>>>> management" option (title is unclear)
>>>>>> with this option set the container is configured to rely on jenkins
>>>>>> master Identity ssh key
>>>>>>
>>>>>> I'm working on a UI refactoring to avoid such confusing options
>>>>>>
>>>>>> 2017-10-20 11:38 GMT+02:00 <seola...@gmail.com>:
>>>>>>
>>>>>>> Just to add that the Docker plugin also recognises the slave
>>>>>>> container as running as shown in this attachment.
>>>>>>>
>>>>>>>
>>>>>>> <https://lh3.googleusercontent.com/-dwvQgB3E6S4/WenD9OpnTbI/AAM/zOJHAj-aEuQ32teM26AFPsAELCX8QAVvwCLcBGAs/s1600/screenshot.9.jpg>
>>>>>>>
>>>>>>>
>>>>>>> On Friday, 20 October 2017 10:03:45 UTC+1, seol...@gmail.com wrote:
>>>>>>>>
>>>>>>>> Hi,
>>>>>>>> I am getting this error on various versions of Jenkins and the
>>>>>>>> docker-plugin including latest of both.
>>>>>>>> My Jenkins master is running in a container. It successfully
>>>>>>>> launches a docker container for the slave (using the 
>>>>>>>> evarga/jenkins-slave
>>>>>>>> image) but then fails to connect with the error below.
>>>>>>>> I can see my slave running with a docker ps and can even
>>>>>>>> successfully connect to it via ssh on 0.0.0.0:32791 (or whatever
>>>>>>>> the given ephmeral port is) using the same credentials configured in 
>>>>>>>> the
>>>>>>>> docker agent template section.
>>>>>>>> Any ideas really welcome as I'm now going round in circles trying
>>>>>>>> to get this working.
>>>>>>>> Thanks.
>>>>>>>>
>>>>>>>>
>>>>>>>> [10/20/17 08:13:45] [SSH] Opening SSH connection to 0.0.0.0:32791.
>>>>>>>> Connection refused (Connection refused)
>>>>>>>> SSH Connection failed with IOException: "Connection refused 
>>>>

Re: Docker-plugin - ssh connection refused when connecting to slave

[nicolas de loof]

Is your jenkins master running in a docker container as well ?

stacktrace seems to demonstrate failure to establish a route to
0.0.0.0:32791, even before any SSH authentication attempt

2017-10-20 12:16 GMT+02:00 Martin Heg <seola...@gmail.com>:

> Thanks for your reply Nicolas. Yes I saw that suggestion in one of your
> other posts and have already tried it but still seeing the same issue
> unfortunately.
>
> On 20 October 2017 at 11:11, nicolas de loof <nicolas.del...@gmail.com>
> wrote:
>
>> to use your own SSH credentials you need to disable the "SSH key
>> management" option (title is unclear)
>> with this option set the container is configured to rely on jenkins
>> master Identity ssh key
>>
>> I'm working on a UI refactoring to avoid such confusing options
>>
>> 2017-10-20 11:38 GMT+02:00 <seola...@gmail.com>:
>>
>>> Just to add that the Docker plugin also recognises the slave container
>>> as running as shown in this attachment.
>>>
>>>
>>> <https://lh3.googleusercontent.com/-dwvQgB3E6S4/WenD9OpnTbI/AAM/zOJHAj-aEuQ32teM26AFPsAELCX8QAVvwCLcBGAs/s1600/screenshot.9.jpg>
>>>
>>>
>>> On Friday, 20 October 2017 10:03:45 UTC+1, seol...@gmail.com wrote:
>>>>
>>>> Hi,
>>>> I am getting this error on various versions of Jenkins and the
>>>> docker-plugin including latest of both.
>>>> My Jenkins master is running in a container. It successfully launches a
>>>> docker container for the slave (using the evarga/jenkins-slave image) but
>>>> then fails to connect with the error below.
>>>> I can see my slave running with a docker ps and can even successfully
>>>> connect to it via ssh on 0.0.0.0:32791 (or whatever the given ephmeral
>>>> port is) using the same credentials configured in the docker agent template
>>>> section.
>>>> Any ideas really welcome as I'm now going round in circles trying to
>>>> get this working.
>>>> Thanks.
>>>>
>>>>
>>>> [10/20/17 08:13:45] [SSH] Opening SSH connection to 0.0.0.0:32791.
>>>> Connection refused (Connection refused)
>>>> SSH Connection failed with IOException: "Connection refused (Connection 
>>>> refused)".
>>>> java.io.IOException: There was a problem while connecting to 0.0.0.0:32791
>>>>at com.trilead.ssh2.Connection.connect(Connection.java:834)
>>>>at com.trilead.ssh2.Connection.connect(Connection.java:703)
>>>>at com.trilead.ssh2.Connection.connect(Connection.java:617)
>>>>at 
>>>> hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1284)
>>>>at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:804)
>>>>at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:793)
>>>>at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>>>at 
>>>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>>>at 
>>>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>>>at java.lang.Thread.run(Thread.java:748)
>>>> Caused by: java.net.ConnectException: Connection refused (Connection 
>>>> refused)
>>>>at java.net.PlainSocketImpl.socketConnect(Native Method)
>>>>at 
>>>> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
>>>>at 
>>>> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:204)
>>>>at 
>>>> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
>>>>at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>>>>at java.net.Socket.connect(Socket.java:589)
>>>>at 
>>>> com.trilead.ssh2.transport.TransportManager.establishConnection(TransportManager.java:367)
>>>>at 
>>>> com.trilead.ssh2.transport.TransportManager.initialize(TransportManager.java:480)
>>>>at com.trilead.ssh2.Connection.connect(Connection.java:774)
>>>>... 9 more
>>>> [10/20/17 08:13:45] Launch failed - cleaning up connection
>>>> [10/20/17 08:13:45] [SSH] Connection closed.
>>>>
>>>>
>>>> --
>>> 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, sen

Re: Docker-plugin - ssh connection refused when connecting to slave

[nicolas de loof]

to use your own SSH credentials you need to disable the "SSH key
management" option (title is unclear)
with this option set the container is configured to rely on jenkins master
Identity ssh key

I'm working on a UI refactoring to avoid such confusing options

2017-10-20 11:38 GMT+02:00 :

> Just to add that the Docker plugin also recognises the slave container as
> running as shown in this attachment.
>
>
> 
>
>
> On Friday, 20 October 2017 10:03:45 UTC+1, seol...@gmail.com wrote:
>>
>> Hi,
>> I am getting this error on various versions of Jenkins and the
>> docker-plugin including latest of both.
>> My Jenkins master is running in a container. It successfully launches a
>> docker container for the slave (using the evarga/jenkins-slave image) but
>> then fails to connect with the error below.
>> I can see my slave running with a docker ps and can even successfully
>> connect to it via ssh on 0.0.0.0:32791 (or whatever the given ephmeral
>> port is) using the same credentials configured in the docker agent template
>> section.
>> Any ideas really welcome as I'm now going round in circles trying to get
>> this working.
>> Thanks.
>>
>>
>> [10/20/17 08:13:45] [SSH] Opening SSH connection to 0.0.0.0:32791.
>> Connection refused (Connection refused)
>> SSH Connection failed with IOException: "Connection refused (Connection 
>> refused)".
>> java.io.IOException: There was a problem while connecting to 0.0.0.0:32791
>>  at com.trilead.ssh2.Connection.connect(Connection.java:834)
>>  at com.trilead.ssh2.Connection.connect(Connection.java:703)
>>  at com.trilead.ssh2.Connection.connect(Connection.java:617)
>>  at 
>> hudson.plugins.sshslaves.SSHLauncher.openConnection(SSHLauncher.java:1284)
>>  at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:804)
>>  at hudson.plugins.sshslaves.SSHLauncher$2.call(SSHLauncher.java:793)
>>  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>>  at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>>  at 
>> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>>  at java.lang.Thread.run(Thread.java:748)
>> Caused by: java.net.ConnectException: Connection refused (Connection refused)
>>  at java.net.PlainSocketImpl.socketConnect(Native Method)
>>  at 
>> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
>>  at 
>> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:204)
>>  at 
>> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
>>  at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>>  at java.net.Socket.connect(Socket.java:589)
>>  at 
>> com.trilead.ssh2.transport.TransportManager.establishConnection(TransportManager.java:367)
>>  at 
>> com.trilead.ssh2.transport.TransportManager.initialize(TransportManager.java:480)
>>  at com.trilead.ssh2.Connection.connect(Connection.java:774)
>>  ... 9 more
>> [10/20/17 08:13:45] Launch failed - cleaning up connection
>> [10/20/17 08:13:45] [SSH] Connection closed.
>>
>>
>> --
> 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/9359318d-f78f-432a-bd06-4c10768f2cdc%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/CANMVJzkXMLjco0tzp_rcZpcyQ-4xFMQNi9%3DKAAEK6-Z8r%3DLYMg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker plugin problems

[nicolas de loof]

Docker-plugin 1.0.1 introduce a new option to disable SSH key injection in
container.
Main idea for this feature is to avoid SSH private key in docker image,
which is a terrible security issue. But for backward compatibility it might
be needed.


> The plugin no longer assumes 4243 as default port. But that’s ok and can
be configured.

I'm not sure where this assumption was made, I have no idea what 4243 port
is supposed to be. default ports for SSH is 22 and docker API is 2375/2376.

> The plugin now always try to check a docker registry to start a docker
container.

which pull strategy do you have configured on your agent template ? Should
be set to "Never Pull" for your use-case



2017-10-17 7:52 GMT+02:00 jessi lopes :

> This is pretty much our use case also...
>
> we spawn a container then ssh into it with "name" "password"
> we did try downgrade to 0.16.2 but no change..
>
> we had upgraded from 0.15 to 0.18... thats when the problem started.
> we are now unable to ssh into the containers...
>
> errors like "
>
> ERROR: Server rejected the 1 private key(s) for root 
> (credentialId:InstanceIdentity/method:publickey)"
> even though we aren't using keys.
> Its also trying to do this as root.?
>
> this error will then be followed with a"
>
> Connection refused (Connection refused)
> SSH Connection failed with IOException: "Connection refused (Connection 
> refused)".
>
> we have tried "Non verifying Verification Strategy"
> as suggested by others online to no avail..
>
> essentially plugin does not work for us anymore.
>
>
> On Thursday, October 12, 2017 at 8:53:40 AM UTC+2, Gunther Laure wrote:
>>
>> Hello!
>>
>>
>>
>> Posting this here, because I am not able create an account to create a
>> Jira issue.
>>
>>
>>
>> Yesterday our jenkins  installation (2.73.1) proposed to update the
>> Docker plugin to 0.18.
>>
>>
>>
>> Reading the plugins notes I reconfigured our cloud settings.
>>
>> A number of issues occurred.
>>
>>
>>
>> The plugin no longer assumes 4243 as default port. But that’s ok and can
>> be configured.
>>
>>
>>
>> The plugin now always try to check a docker registry to start a docker
>> container. If no registry is configures a fallback registry is used.
>>
>> In our situation: We have no registry. Our docker hosts have a fixed set
>> of custom images that are used. No registry involved.
>>
>>
>>
>> The effect is, that many temporary slaves are shown on as executors, but
>> none is really started on the hosts.
>>
>> Docker log on the hosts shows failed pull attempts.
>>
>>
>>
>> Docker ps shows no containers
>>
>>
>>
>>
>>
>> Playing with the configuration, sometimes a docker container could be
>> started (No idea how that worked, with the issue mentioned above).
>>
>> Docker ps showed the started containers, but immediately terminated them.
>>
>> Somehow ssh always got connection refused. (We are using a user/pw stored
>> in the images).
>>
>> I see those messages in the log of the spawned slave nodes.
>>
>>
>>
>> Reverting the plugin to version 16.2 resolved all those issues.
>>
>>
>>
>> If information, like our current docker configuration is needed, I am
>> happy to provide it.
>>
>>
>>
>> Thank you in advance,
>>
>> Gunther
>>
> --
> 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/cf62af03-7894-4da4-adbb-8d02c97fa712%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/CANMVJzmYCXjsCVsX8ie9z4Lnr61uquQ5pp64%3DTzKcRFu6PA4zw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins docker container overrides with "--entrypoint cat" ...

[nicolas de loof]

docker.inside NEED some way to run a docker container in some "wait" mode,
so the use of the `cat` command.
if your entrypoint script do follow docker recommendations it *should* detect
use of such a command and enventually execute it, but real world experience
demonstrated many people don't follow this recommendation, and as such the
container failed to start as expected / stopped immediately. But the "fix"
to override entrypoint is worst imho

Feel free to comment on
https://github.com/jenkinsci/docker-workflow-plugin/pull/85


2017-09-29 9:26 GMT+02:00 Eric Tan :

> https://issues.jenkins-ci.org/browse/JENKINS-39748
>
> On Thursday, 28 September 2017 18:49:04 UTC+8, Eric Tan wrote:
>>
>> Hi,
>>
>> Is there a way to prevent Jenkin from overriding the entrypoint specified
>> in the container image?
>> As shown below in the console output, Jenkins adds "*--entrypoint cat*"
>> which overrides my own entrypoint.
>>
>> $ docker run -t -d -u 1000:1000 -w 
>> /var/jenkins_home/workspace/Test_Pipeline_master-K2ZSF4WTA --volumes-from 
>> db477ccfb5f8261f85de03 -e  -e  -e  *--entrypoint 
>> cat* test-app
>>
>>
>>
>> docker inspect shows:
>>
>> "Entrypoint": [
>>
>> "cat"
>>
>> ],
>>
>> The original image is
>>
>> "Entrypoint": [
>>
>> "python",
>>
>> "test-app.py"
>>
>> ],
>>
>> --
> 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/b62b27a1-98e6-4e36-92d4-366fc0b508d6%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/CANMVJzmtbzd22h4sdbuA5rtMqgX9JOrUwjibnnNvi-hqisycmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins and Docker

[nicolas de loof]

The chapter you refer to is about running Jenkins as a docker container. If
you used another installation process, just ignore
That being said, docker is a nice complement to jenkins, and is used in
various samples in documentation, including Declarative Pipeline. So I
recommend you install it so you're not limited in your newcomer experience
(install docker4mac/windows, it's just about few clicks)

2017-09-05 16:21 GMT+02:00 Tibbs :

> I'm sorry if this has been asked before but I am new to both Jenkins and
> virtualised containers and couldn't find something related to my question.
>
> Can anyone tell me if I need Docker in order to use Jenkins? I am slightly
> puzzled by Jenkins documentation saying the you need to have Docker
> *properly* installed ( https://jenkins.io/doc/book/
> getting-started/installing/#docker ).
>
> I installed Jenkins on my local pc without Docker. How would Docker help
> here? Is it really needed?
>
> 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/a5e3e8f0-e993-4844-b1a5-0a799e4bff35%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/CANMVJzmbfZ%3DUgB%3D9bCCP5W8ak0i4pe4wF1W_83PHG%3DidvP%3DsSw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Declarative pipeline docker executeable TCP supported?

[nicolas de loof]

docker agent in declarative pipeline actually translate into docker.inside

(see docker-pipeline-plugin for details) which require running docker
containers on the same node as the build (so it can access workspace)

2017-09-02 19:50 GMT-07:00 'Peter Teichner' via Jenkins Users <
jenkinsci-users@googlegroups.com>:

> That doesn't really work as I haven't got docker or have no intention of
> running docker on the node of the jenkins master. So is there a way to use
> a remote docker machine or no?
>
> On Saturday, 2 September 2017 00:00:25 UTC+1, Reza Etezal wrote:
>>
>> You need to either set it in the Global Tool Confoguration, at the system
>> level https:///configureTools/, or in the Tool Location at
>> the node level https:///computer//configure
>>
>>
>> On Friday, September 1, 2017 at 6:40:32 PM UTC-4, Peter Teichner wrote:
>>>
>>> I've got a quick question: when using declarative pipeline with the
>>> agent specified as a docker image how does the pipeline determine where the
>>> docker executable is? Is there a way to set a remote docker over TCP?
>>>
>>> agent {
>>> docker {
>>> image 'maven:3-alpine'
>>> label 'my-defined-label'
>>> args  '-v /tmp:/tmp'
>>> }
>>> }
>>>
>>> I use CoreOS for all the Docker related stuff and I haven't got Docker 
>>> running on the Jenkins master.
>>>
>>> --
> 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/346beadc-4834-49ba-a6f1-0c91e482e13c%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/CANMVJzmebNSjL9CiCgWUGs9G4x63NRFuGdEa3KoQ4cb0uZ2maw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Does docker-slaves-plugin with pipeline assume Linux?

[nicolas de loof]

Yes indeed. But as long g as you use git this one is actually ran in
Jenkins agent container due to an implementation issue.

Le 13 août 2017 12:16 PM, "Jacob Larsen" <ja...@larsen.net> a écrit :

> Wouldn't you need a Windows SCM image as well?
>
> On 2017-08-12 18:56, nicolas de loof wrote:
>
> I think you just miss a Jenkins agent docker image for Windows
> architecture, everything else should work (linux style paths aren't an
> issue afaik)
>
> Le 11 août 2017 16:37, "Thiago Carvalho Davila" <
> thiago.dav...@serpro.gov.br> a écrit :
>
>> That is very sad.. I have slaves for windows and linux, and I was
>> begining a migration of my machine slaves to containers =(
>>
>> Is there a JIRA feature created for that cause?
>>
>> Em 11/08/2017 04:52:49, Geoff Bache escreveu:
>>
>>
>> OK, I think we can conclude from my evidence that it doesn't yet work on
>> Windows then: I'm not trying to do anything beyond basic usage. Perhaps you
>> could write this in the plugin description?
>>
>> On Friday, 11 August 2017 09:08:51 UTC+2, nicolas de loof wrote:
>>>
>>> This plugin has never been tested for Windows containers, so I can't
>>> tell if they can work without changes.
>>>
>>> Le 11 août 2017 9:04 AM, "Geoff Bache" <geoff...@gmail.com> a écrit :
>>>
>>>>
>>>> I removed the extra slash in global configuration, but it still fails
>>>> and there are still Linux-style paths that I don't seem to be able to
>>>> configure. See text below.
>>>> I also tried using jenkinsci/slave, which the tooltip recommends, but
>>>> got the same error.
>>>>
>>>> /Geoff
>>>>
>>>> Start Docker container to host the build
>>>> $ docker volume create
>>>> $ docker create --interactive --log-driver=none --env
>>>> TMPDIR=/home/jenkins/.tmp --user 1:1 --rm --volume
>>>> 20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/
>>>> jenkins/agent java -Djava.io.tmpdir=/home/jenkins/.tmp -jar
>>>> /home/jenkins/slave.jar Error response from daemon: invalid bind mount spec
>>>> "20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/":
>>>> invalid volume specification: '20cf056ee345717252ece59811047
>>>> e0692a9bea818f5ca23b79af77f220dbd0a:\home\jenkins\'
>>>>
>>>> On Thursday, 10 August 2017 17:14:30 UTC+2, Geoff Bache wrote:
>>>>>
>>>>> Hi all,
>>>>>
>>>>>
>>>>>
>>>>> I have a Jenkins pipeline defined (Windows server 2016) and I’m trying
>>>>> to get it to use docker containers instead of building locally. The
>>>>> docker-slaves-plugin looked like the most convenient interface for this
>>>>> among a confusing forest of different Docker plugins.
>>>>>
>>>>>
>>>>>
>>>>> So I installed it and pointed it at my Docker image in the
>>>>> configuration. It carried on exactly as before and ignored Docker 
>>>>> entirely,
>>>>> even after Jenkins restart.
>>>>>
>>>>>
>>>>>
>>>>> I then found a hint that I should replace “node” with
>>>>> “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the
>>>>> following in my build log (with debug option enabled).
>>>>>
>>>>> Note the “docker create” line which seems to be referring to a bunch
>>>>> of linux paths that just don’t exist and looks a bit hardcoded...
>>>>>
>>>>>
>>>>> If, as I suspect, this isn't supported, any hints on which plugin to
>>>>> use instead would be appreciated.
>>>>>
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> Geoff Bache
>>>>>
>>>>>
>>>>>
>>>>> Start Docker container to host the build
>>>>>
>>>>> $ docker volume create
>>>>>
>>>>> $ docker create --interactive --log-driver=none --env
>>>>> TMPDIR=/home/jenkins/.tmp --user 1:1 --rm --volume
>>>>> 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/
>>>>> jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar
>>>>> /home/jenkins/slave.

Re: Does docker-slaves-plugin with pipeline assume Linux?

[nicolas de loof]

I think you just miss a Jenkins agent docker image for Windows
architecture, everything else should work (linux style paths aren't an
issue afaik)

Le 11 août 2017 16:37, "Thiago Carvalho Davila" <thiago.dav...@serpro.gov.br>
a écrit :

> That is very sad.. I have slaves for windows and linux, and I was begining
> a migration of my machine slaves to containers =(
>
> Is there a JIRA feature created for that cause?
>
> Em 11/08/2017 04:52:49, Geoff Bache escreveu:
>
>
> OK, I think we can conclude from my evidence that it doesn't yet work on
> Windows then: I'm not trying to do anything beyond basic usage. Perhaps you
> could write this in the plugin description?
>
> On Friday, 11 August 2017 09:08:51 UTC+2, nicolas de loof wrote:
>>
>> This plugin has never been tested for Windows containers, so I can't tell
>> if they can work without changes.
>>
>> Le 11 août 2017 9:04 AM, "Geoff Bache" <geoff...@gmail.com> a écrit :
>>
>>>
>>> I removed the extra slash in global configuration, but it still fails
>>> and there are still Linux-style paths that I don't seem to be able to
>>> configure. See text below.
>>> I also tried using jenkinsci/slave, which the tooltip recommends, but
>>> got the same error.
>>>
>>> /Geoff
>>>
>>> Start Docker container to host the build
>>> $ docker volume create
>>> $ docker create --interactive --log-driver=none --env
>>> TMPDIR=/home/jenkins/.tmp --user 1:1 --rm --volume
>>> 20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/
>>> jenkins/agent java -Djava.io.tmpdir=/home/jenkins/.tmp -jar
>>> /home/jenkins/slave.jar Error response from daemon: invalid bind mount spec
>>> "20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/":
>>> invalid volume specification: '20cf056ee345717252ece59811047
>>> e0692a9bea818f5ca23b79af77f220dbd0a:\home\jenkins\'
>>>
>>> On Thursday, 10 August 2017 17:14:30 UTC+2, Geoff Bache wrote:
>>>>
>>>> Hi all,
>>>>
>>>>
>>>>
>>>> I have a Jenkins pipeline defined (Windows server 2016) and I’m trying
>>>> to get it to use docker containers instead of building locally. The
>>>> docker-slaves-plugin looked like the most convenient interface for this
>>>> among a confusing forest of different Docker plugins.
>>>>
>>>>
>>>>
>>>> So I installed it and pointed it at my Docker image in the
>>>> configuration. It carried on exactly as before and ignored Docker entirely,
>>>> even after Jenkins restart.
>>>>
>>>>
>>>>
>>>> I then found a hint that I should replace “node” with
>>>> “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the
>>>> following in my build log (with debug option enabled).
>>>>
>>>> Note the “docker create” line which seems to be referring to a bunch of
>>>> linux paths that just don’t exist and looks a bit hardcoded...
>>>>
>>>>
>>>> If, as I suspect, this isn't supported, any hints on which plugin to
>>>> use instead would be appreciated.
>>>>
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Geoff Bache
>>>>
>>>>
>>>>
>>>> Start Docker container to host the build
>>>>
>>>> $ docker volume create
>>>>
>>>> $ docker create --interactive --log-driver=none --env
>>>> TMPDIR=/home/jenkins/.tmp --user 1:1 --rm --volume
>>>> 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/
>>>> jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar
>>>> /home/jenkins/slave.jar
>>>>
>>>> Error parsing reference: "jenkins/agent/" is not a valid
>>>> repository/tag: invalid reference format
>>>>
>>>> [Pipeline] // dockerNode
>>>>
>>>> [Pipeline] }
>>>>
>>>> [Pipeline] // stage
>>>>
>>>> [Pipeline] }
>>>>
>>>> [Pipeline] // node
>>>>
>>>> [Pipeline] End of Pipeline
>>>>
>>>> java.io.IOException: Failed to create docker image
>>>>
>>>> at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemoti
>>>> ngContainer(CliDockerDriver.java:176)
>>>>
&g

Re: Does docker-slaves-plugin with pipeline assume Linux?

[nicolas de loof]

This plugin has never been tested for Windows containers, so I can't tell
if they can work without changes.

Le 11 août 2017 9:04 AM, "Geoff Bache"  a écrit :

>
> I removed the extra slash in global configuration, but it still fails and
> there are still Linux-style paths that I don't seem to be able to
> configure. See text below.
> I also tried using jenkinsci/slave, which the tooltip recommends, but got
> the same error.
>
> /Geoff
>
> Start Docker container to host the build
> $ docker volume create
> $ docker create --interactive --log-driver=none --env
> TMPDIR=/home/jenkins/.tmp --user 1:1 --rm --volume
> 20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/
> jenkins/agent java -Djava.io.tmpdir=/home/jenkins/.tmp -jar
> /home/jenkins/slave.jar Error response from daemon: invalid bind mount spec
> "20cf056ee345717252ece59811047e0692a9bea818f5ca23b79af77f220dbd0a:/home/jenkins/":
> invalid volume specification: '20cf056ee345717252ece59811047e
> 0692a9bea818f5ca23b79af77f220dbd0a:\home\jenkins\'
>
> On Thursday, 10 August 2017 17:14:30 UTC+2, Geoff Bache wrote:
>>
>> Hi all,
>>
>>
>>
>> I have a Jenkins pipeline defined (Windows server 2016) and I’m trying to
>> get it to use docker containers instead of building locally. The
>> docker-slaves-plugin looked like the most convenient interface for this
>> among a confusing forest of different Docker plugins.
>>
>>
>>
>> So I installed it and pointed it at my Docker image in the configuration.
>> It carried on exactly as before and ignored Docker entirely, even after
>> Jenkins restart.
>>
>>
>>
>> I then found a hint that I should replace “node” with
>> “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the
>> following in my build log (with debug option enabled).
>>
>> Note the “docker create” line which seems to be referring to a bunch of
>> linux paths that just don’t exist and looks a bit hardcoded...
>>
>>
>> If, as I suspect, this isn't supported, any hints on which plugin to use
>> instead would be appreciated.
>>
>>
>>
>> Regards,
>>
>> Geoff Bache
>>
>>
>>
>> Start Docker container to host the build
>>
>> $ docker volume create
>>
>> $ docker create --interactive --log-driver=none --env
>> TMPDIR=/home/jenkins/.tmp --user 1:1 --rm --volume
>> 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/
>> jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar
>> /home/jenkins/slave.jar
>>
>> Error parsing reference: "jenkins/agent/" is not a valid repository/tag:
>> invalid reference format
>>
>> [Pipeline] // dockerNode
>>
>> [Pipeline] }
>>
>> [Pipeline] // stage
>>
>> [Pipeline] }
>>
>> [Pipeline] // node
>>
>> [Pipeline] End of Pipeline
>>
>> java.io.IOException: Failed to create docker image
>>
>> at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemoti
>> ngContainer(CliDockerDriver.java:176)
>>
>> at it.dockins.dockerslaves.DefaultDockerProvisioner.launchRemot
>> ingContainer(DefaultDockerProvisioner.java:88)
>>
>> at it.dockins.dockerslaves.DockerComputerLauncher.launch(Docker
>> ComputerLauncher.java:58)
>>
>> at it.dockins.dockerslaves.DockerComputerLauncher.launch(Docker
>> ComputerLauncher.java:49)
>>
>> at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSl
>> ave.java:123)
>>
>> Caused: it.dockins.dockerslaves.api.OneShotExecutorProvisioningException
>>
>> at it.dockins.dockerslaves.api.OneShotSlave.provisionFailed(One
>> ShotSlave.java:145)
>>
>> at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSl
>> ave.java:129)
>>
>> at it.dockins.dockerslaves.api.OneShotSlave.createLauncher(OneS
>> hotSlave.java:154)
>>
>> at it.dockins.dockerslaves.DockerSlave.createLauncher(DockerSla
>> ve.java:96)
>>
>> at it.dockins.dockerslaves.pipeline.DockerNodeStepExecution$Pla
>> ceholderTask$PlaceholderExecutable.run(DockerNodeStepExecution.java:573)
>>
>> at hudson.model.ResourceController.execute(ResourceController.
>> java:97)
>>
>> at hudson.model.Executor.run(Executor.java:405)
>>
>> Finished: 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/1ce34aee-8be4-4065-b189-4f27c079e781%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 

Re: Does docker-slaves-plugin with pipeline assume Linux?

[nicolas de loof]

Oh yes that's a stupid typo in default value, will fix this and push a
release. We are still missing multi arch docker images so this same id can
pull a Windows version of the agent image

Le 10 août 2017 8:51 PM, "Jacob Larsen" <ja...@larsen.net> a écrit :

> Looks like the agent image is the default one that was just set in the
> latest release, see https://github.com/jenkinsci/
> docker-slaves-plugin/commit/2d0470b27a84ddff00c3e1adc7aec9b7e8dece00
>
> Take a look at the Docker Slaves section of the global Jenkins
> configuration. The remoting image is probably set to jenkins/agent/.
> Notice the final slash as Slide mentions, I believe the specific error you
> experience would go away by removing that final slash.
>
> Anyhow, that would probably not work for you no matter what. Since you are
> using a Windows Docker instance then you will need Windows images for the
> remoting image and the SCM image. But I have no idea if the volume mounts
> would work there. You might be right that this part is hardcoded to Linux.
>
> /Jacob
>
> On 2017-08-10 18:19, nicolas de loof wrote:
>
> I'm on vacation so can't help before 1 week. Pipeline is fully supported,
> please check global configuration for the agent image you have configured
> for docker-slaves-plugin
>
> Le 10 août 2017 5:30 PM, "Geoff Bache" <geoff.ba...@gmail.com> a écrit :
>
>>
>> Yes, I didn't contribute anything to that generated command.
>>
>> On Thursday, 10 August 2017 17:22:17 UTC+2, slide wrote:
>>>
>>> The extra slash after "agent" is odd, I assume that the docker create
>>> command is generated by the plugin?
>>>
>>> On Thu, Aug 10, 2017 at 8:14 AM Geoff Bache <geoff...@gmail.com> wrote:
>>>
>>>> Hi all,
>>>>
>>>>
>>>>
>>>> I have a Jenkins pipeline defined (Windows server 2016) and I’m trying
>>>> to get it to use docker containers instead of building locally. The
>>>> docker-slaves-plugin looked like the most convenient interface for this
>>>> among a confusing forest of different Docker plugins.
>>>>
>>>>
>>>>
>>>> So I installed it and pointed it at my Docker image in the
>>>> configuration. It carried on exactly as before and ignored Docker entirely,
>>>> even after Jenkins restart.
>>>>
>>>>
>>>>
>>>> I then found a hint that I should replace “node” with
>>>> “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the
>>>> following in my build log (with debug option enabled).
>>>>
>>>> Note the “docker create” line which seems to be referring to a bunch of
>>>> linux paths that just don’t exist and looks a bit hardcoded...
>>>>
>>>>
>>>> If, as I suspect, this isn't supported, any hints on which plugin to
>>>> use instead would be appreciated.
>>>>
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Geoff Bache
>>>>
>>>>
>>>>
>>>> Start Docker container to host the build
>>>>
>>>> $ docker volume create
>>>>
>>>> $ docker create --interactive --log-driver=none --env
>>>> TMPDIR=/home/jenkins/.tmp --user 1:1 --rm --volume
>>>> 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/
>>>> jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar
>>>> /home/jenkins/slave.jar
>>>>
>>>> Error parsing reference: "jenkins/agent/" is not a valid
>>>> repository/tag: invalid reference format
>>>>
>>>> [Pipeline] // dockerNode
>>>>
>>>> [Pipeline] }
>>>>
>>>> [Pipeline] // stage
>>>>
>>>> [Pipeline] }
>>>>
>>>> [Pipeline] // node
>>>>
>>>> [Pipeline] End of Pipeline
>>>>
>>>> java.io.IOException: Failed to create docker image
>>>>
>>>> at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemoti
>>>> ngContainer(CliDockerDriver.java:176)
>>>>
>>>> at it.dockins.dockerslaves.DefaultDockerProvisioner.launchRemot
>>>> ingContainer(DefaultDockerProvisioner.java:88)
>>>>
>>>> at it.dockins.dockerslaves.DockerComputerLauncher.launch(Docker
>>>> ComputerLauncher.java:58)
>>>>
>>>> at it.dockins.dockerslaves.DockerComputerLau

Re: Does docker-slaves-plugin with pipeline assume Linux?

[nicolas de loof]

I'm on vacation so can't help before 1 week. Pipeline is fully supported,
please check global configuration for the agent image you have configured
for docker-slaves-plugin

Le 10 août 2017 5:30 PM, "Geoff Bache"  a écrit :

>
> Yes, I didn't contribute anything to that generated command.
>
> On Thursday, 10 August 2017 17:22:17 UTC+2, slide wrote:
>>
>> The extra slash after "agent" is odd, I assume that the docker create
>> command is generated by the plugin?
>>
>> On Thu, Aug 10, 2017 at 8:14 AM Geoff Bache  wrote:
>>
>>> Hi all,
>>>
>>>
>>>
>>> I have a Jenkins pipeline defined (Windows server 2016) and I’m trying
>>> to get it to use docker containers instead of building locally. The
>>> docker-slaves-plugin looked like the most convenient interface for this
>>> among a confusing forest of different Docker plugins.
>>>
>>>
>>>
>>> So I installed it and pointed it at my Docker image in the
>>> configuration. It carried on exactly as before and ignored Docker entirely,
>>> even after Jenkins restart.
>>>
>>>
>>>
>>> I then found a hint that I should replace “node” with
>>> “dockerNode(‘myimage’)” in my Jenkinsfile. So I did that, and got the
>>> following in my build log (with debug option enabled).
>>>
>>> Note the “docker create” line which seems to be referring to a bunch of
>>> linux paths that just don’t exist and looks a bit hardcoded...
>>>
>>>
>>> If, as I suspect, this isn't supported, any hints on which plugin to use
>>> instead would be appreciated.
>>>
>>>
>>>
>>> Regards,
>>>
>>> Geoff Bache
>>>
>>>
>>>
>>> Start Docker container to host the build
>>>
>>> $ docker volume create
>>>
>>> $ docker create --interactive --log-driver=none --env
>>> TMPDIR=/home/jenkins/.tmp --user 1:1 --rm --volume
>>> 45aa67db1c5cc27820ebc3afd7abdd4a708b78f8d7ce2720fdbc2c7956ac2a52:/home/jenkins/
>>> jenkins/agent/ java -Djava.io.tmpdir=/home/jenkins/.tmp -jar
>>> /home/jenkins/slave.jar
>>>
>>> Error parsing reference: "jenkins/agent/" is not a valid repository/tag:
>>> invalid reference format
>>>
>>> [Pipeline] // dockerNode
>>>
>>> [Pipeline] }
>>>
>>> [Pipeline] // stage
>>>
>>> [Pipeline] }
>>>
>>> [Pipeline] // node
>>>
>>> [Pipeline] End of Pipeline
>>>
>>> java.io.IOException: Failed to create docker image
>>>
>>> at it.dockins.dockerslaves.drivers.CliDockerDriver.launchRemoti
>>> ngContainer(CliDockerDriver.java:176)
>>>
>>> at it.dockins.dockerslaves.DefaultDockerProvisioner.launchRemot
>>> ingContainer(DefaultDockerProvisioner.java:88)
>>>
>>> at it.dockins.dockerslaves.DockerComputerLauncher.launch(Docker
>>> ComputerLauncher.java:58)
>>>
>>> at it.dockins.dockerslaves.DockerComputerLauncher.launch(Docker
>>> ComputerLauncher.java:49)
>>>
>>> at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSl
>>> ave.java:123)
>>>
>>> Caused: it.dockins.dockerslaves.api.OneShotExecutorProvisioningException
>>>
>>> at it.dockins.dockerslaves.api.OneShotSlave.provisionFailed(One
>>> ShotSlave.java:145)
>>>
>>> at it.dockins.dockerslaves.api.OneShotSlave.provision(OneShotSl
>>> ave.java:129)
>>>
>>> at it.dockins.dockerslaves.api.OneShotSlave.createLauncher(OneS
>>> hotSlave.java:154)
>>>
>>> at it.dockins.dockerslaves.DockerSlave.createLauncher(DockerSla
>>> ve.java:96)
>>>
>>> at it.dockins.dockerslaves.pipeline.DockerNodeStepExecution$Pla
>>> ceholderTask$PlaceholderExecutable.run(DockerNodeStepExecution.java:573)
>>>
>>> at hudson.model.ResourceController.execute(ResourceController.
>>> java:97)
>>>
>>> at hudson.model.Executor.run(Executor.java:405)
>>>
>>> Finished: 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-use...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-users/57ecdf26-75eb-4e04-b93c-35d403283ae1%
>>> 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/dca1ccde-53bb-4056-ba43-68456da927d0%40googlegroups.
> com
> 
> .
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google 

Re: The official docker image jenkins/jenkins:lts is missing ruby

[nicolas de loof]

We recommend to NOT run build within the master image anyway, and always
connect a slave computer/container to enforce resources isolation.

Le 27 juil. 2017 9:12 PM, "Jacob Larsen"  a écrit :

> I agree. Extending the base image is the way to go. Alternatively, you can
> use a clean image for the master and set up slaves with ruby, labeled
> appropriately.
>
> /Jacob
>
> On 2017-07-27 16:02, Mark Waite wrote:
>
> I would be very surprised if the Jenkins docker image were extended to
> include ruby.  Ruby is not a mandatory requirement for Jenkins development
> and adding it to the base Jenkins Docker image will increase the size of
> the docker image for all Jenkins users.
>
> Mark Waite
>
> On Thu, Jul 27, 2017 at 3:33 AM Federico Paolantoni <
> federico.paolant...@gmail.com> wrote:
>
>> Dear list,
>> I'm setting up a software development lifecycle infrastructure.
>> I decided to use the official docker container provided by Jenkins
>> community and the idea is not to extend it writing my own image avoiding
>> the amount of work required to maintain an image and to keep as standard as
>> possible.
>> But:
>> I noticed that ruby is not provided with the container, so i wonder if
>> the community is considering to add it on the official supported image,
>> considering that there is no way to inject ruby, rake an gems inside the
>> builds as done for nodejs,
>>
>> Thank you
>>
>>
>> --
>> 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/29e93174-df1e-4d7f-a36c-
>> e47780fc7d77%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/CAO49JtEsoZw5kcnrv750wFn6BbOWO
> 5_8vH5ZcDOsHmc9B-7usg%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/e61bcd3c-6ef6-f141-d92f-5321f6bf74fe%40larsen.net
> 
> .
> 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/CANMVJznn9XHFnfQAVnw%2BVJpYUcjYg%2B5Zy01SpGq-wCdEP%2BNKog%40mail.gmail.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

[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

[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: build docker container inside dockerized Jenkins

[nicolas de loof]

to use docker-slaves plugin you'll need docker socket or a DOCKER_HOST url
set so master can run docker commands

2017-06-07 4:33 GMT+02:00 Jeeva Chelladhurai <sje...@gmail.com>:

> > docker-slaves don't follow the classic slave approach, it doesn't use
> any transport (ssh, jnlp) but the plain docker CLI terminal emulation.
>
> Does that mean I have to bind mount docker socket to the Jenkins container?
>
> -Jeeva
>
> On Tue, Jun 6, 2017 at 10:07 PM, nicolas de loof <nicolas.del...@gmail.com
> > wrote:
>
>> docker-slaves don't follow the classic slave approach, it doesn't use any
>> transport (ssh, jnlp) but the plain docker CLI terminal emulation.
>>
>> 2017-06-06 18:19 GMT+02:00 Jeeva Chelladhurai <sje...@gmail.com>:
>>
>>> currently I am using SSH slaves for building docker images. Is it a
>>> recommended practice?
>>>
>>> How does Docker slave plugin works? Does function like a slave or
>>> piggyback on any of the existing slaves?
>>> https://wiki.jenkins-ci.org/display/JENKINS/Docker+Slaves+Plugin
>>>
>>> On Tue, Jun 6, 2017 at 7:45 PM, nicolas de loof <
>>> nicolas.del...@gmail.com> wrote:
>>>
>>>> When you're running Jenkins in a container don't build on master,
>>>> always connect a slave. This slave can also be a container. Doing this
>>>> you'll enforce process isolation.
>>>> To run docker commands like 'docker build' the commonly used approach
>>>> is to bind mount /car/run/docker.sock. that's beer red wings if you just
>>>> throw away security: build can do anything on host until you add another
>>>> isolation layer, for sample a LXD container.
>>>>
>>>> Le 6 juin 2017 4:03 PM, "Jeeva Chelladhurai" <sje...@gmail.com> a
>>>> écrit :
>>>>
>>>> I run by Jenkins inside a docker container. Now I need to build docker
>>>> images from this Jenkins instance. Would you please suggest me some 
>>>> options.
>>>>
>>>> --
>>>> Jeeva K S Chelladhurai
>>>>
>>>> --
>>>> 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/ms
>>>> gid/jenkinsci-users/CAK5CbZXmRA8w4to2zRO01KCz0QJcGQuY0azXLZQ
>>>> 5EBG%3DmDfJfw%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAK5CbZXmRA8w4to2zRO01KCz0QJcGQuY0azXLZQ5EBG%3DmDfJfw%40mail.gmail.com?utm_medium=email_source=footer>
>>>> .
>>>> 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/ms
>>>> gid/jenkinsci-users/CANMVJzk5X%2BMsLrptSGpwCSKXgGKpOLdAEjzRB
>>>> cfPbHrnsO3vwg%40mail.gmail.com
>>>> <https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzk5X%2BMsLrptSGpwCSKXgGKpOLdAEjzRBcfPbHrnsO3vwg%40mail.gmail.com?utm_medium=email_source=footer>
>>>> .
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>>
>>>
>>> --
>>> Jeeva K S Chelladhurai
>>>
>>> --
>>> 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/ms
>>> gid/jenkinsci-users/CAK5CbZUEqY-2FXVWYApHVNMjz_7m%2BdmLyHL7f
>>> 0U%2BTyMe9b8%3D7g%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/CAK5CbZUEqY-2FXVWYApHVNMjz_7m%2BdmLyHL7f0U%2BTyMe9b8%3D7g%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
>> You received this message because you are subscribed to the Google Groups

Re: build docker container inside dockerized Jenkins

[nicolas de loof]

docker-slaves don't follow the classic slave approach, it doesn't use any
transport (ssh, jnlp) but the plain docker CLI terminal emulation.

2017-06-06 18:19 GMT+02:00 Jeeva Chelladhurai <sje...@gmail.com>:

> currently I am using SSH slaves for building docker images. Is it a
> recommended practice?
>
> How does Docker slave plugin works? Does function like a slave or
> piggyback on any of the existing slaves?
> https://wiki.jenkins-ci.org/display/JENKINS/Docker+Slaves+Plugin
>
> On Tue, Jun 6, 2017 at 7:45 PM, nicolas de loof <nicolas.del...@gmail.com>
> wrote:
>
>> When you're running Jenkins in a container don't build on master, always
>> connect a slave. This slave can also be a container. Doing this you'll
>> enforce process isolation.
>> To run docker commands like 'docker build' the commonly used approach is
>> to bind mount /car/run/docker.sock. that's beer red wings if you just throw
>> away security: build can do anything on host until you add another
>> isolation layer, for sample a LXD container.
>>
>> Le 6 juin 2017 4:03 PM, "Jeeva Chelladhurai" <sje...@gmail.com> a écrit :
>>
>> I run by Jenkins inside a docker container. Now I need to build docker
>> images from this Jenkins instance. Would you please suggest me some options.
>>
>> --
>> Jeeva K S Chelladhurai
>>
>> --
>> 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/ms
>> gid/jenkinsci-users/CAK5CbZXmRA8w4to2zRO01KCz0QJcGQuY0azXLZQ
>> 5EBG%3DmDfJfw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CAK5CbZXmRA8w4to2zRO01KCz0QJcGQuY0azXLZQ5EBG%3DmDfJfw%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> 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/ms
>> gid/jenkinsci-users/CANMVJzk5X%2BMsLrptSGpwCSKXgGKpOLdAEjzRB
>> cfPbHrnsO3vwg%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzk5X%2BMsLrptSGpwCSKXgGKpOLdAEjzRBcfPbHrnsO3vwg%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Jeeva K S Chelladhurai
>
> --
> 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/CAK5CbZUEqY-2FXVWYApHVNMjz_7m%
> 2BdmLyHL7f0U%2BTyMe9b8%3D7g%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAK5CbZUEqY-2FXVWYApHVNMjz_7m%2BdmLyHL7f0U%2BTyMe9b8%3D7g%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> 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/CANMVJzmegp%3DN%2BRJF_vVTkM5ghUVw3KQJ7KAx7h%2BN4XrG__q5Gw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: build docker container inside dockerized Jenkins

[nicolas de loof]

When you're running Jenkins in a container don't build on master, always
connect a slave. This slave can also be a container. Doing this you'll
enforce process isolation.
To run docker commands like 'docker build' the commonly used approach is to
bind mount /car/run/docker.sock. that's beer red wings if you just throw
away security: build can do anything on host until you add another
isolation layer, for sample a LXD container.

Le 6 juin 2017 4:03 PM, "Jeeva Chelladhurai"  a écrit :

I run by Jenkins inside a docker container. Now I need to build docker
images from this Jenkins instance. Would you please suggest me some options.

-- 
Jeeva K S Chelladhurai

-- 
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/CAK5CbZXmRA8w4to2zRO01KCz0QJcGQuY0azXLZQ5EBG%3DmDfJfw%
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/CANMVJzk5X%2BMsLrptSGpwCSKXgGKpOLdAEjzRBcfPbHrnsO3vwg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins dkr container on top of CoreOS + Kubernetes - DNS Issue resolving mirrors.jenkins-ci.org

[nicolas de loof]

That's pretty odd as the blueocean container is based on the jenkins docker
image.

2017-02-21 7:02 GMT+01:00 :

> Thanks Mark. Since I can't send docker-specific args via Kubernetes pods,
> I've shifted to the blueocean container and the issue doesn't happen there.
>
> It's a pity I can't use the main jenkins container, but this will do me
> for now.
>
> Cheers,
> Shaun
>
> On Tuesday, February 21, 2017 at 3:56:58 PM UTC+11, Mark Waite wrote:
>>
>> I've had to launch the docker command with the "--dns" argument and the
>> IP address of the DNS server on my network.  My environment is just the
>> simple Docker daemon on a Ubuntu host, but I seemed to consistently have
>> DNS problems until I added that argument to the docker command line.
>>
>> Mark Waite
>>
>> On Mon, Feb 20, 2017 at 9:54 PM  wrote:
>>
>>> Hey there,
>>>
>>> I'm wondering if anyone else has come up against this issue.
>>>
>>> I'm running up the latest jenkins container (2.32.2) on top of:
>>>
>>>- Docker 1.13.0
>>>- CoreOS 1313.0.0
>>>- Kubernetes v1.5.3
>>>- Vagrant 1.9.1
>>>
>>> And jenkins complains on start up that it can't find the updates mirror:
>>>
 java.net.UnknownHostException: mirrors.jenkins-ci.org
>>>
>>>
>>> Fair enough. But if I try and resolve the host in that same container I
>>> can resolve back to an IP, even curling that host brings back the site:
>>>
>>> $ kubectl exec -it jenkins-pwqwq curl http://mirrors.jenkins-ci.org |
>>> head
>>> 
>>> 
>>> 
>>>   Jenkins mirrors
>>>
>>> Additionally, if I run a jenkins job with a simple command to curl that
>>> host (it's a single master jenkins setup), I get content back.
>>>
>>> Anyone got any pointers? I've blown the stack away and recreated a
>>> number of times, no resolution. I feel like jenkins thinks the DNS host is
>>> something it is not.
>>>
>>>
>>> Regards,
>>> Shaun
>>>
>>> --
>>> 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/ms
>>> gid/jenkinsci-users/7b50abf6-2eb5-4afe-890f-d70b4a889878%
>>> 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/7fe54834-3498-44d4-8f82-156447455332%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/CANMVJzkk9kO8%2BzkYm98mv_Pob8yb1rNtDcCud8vyj9U95ypFbA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: docker.inside or agnet {docker} executing as host user (jenkins) instead of the containers root

[nicolas de loof]

uname gives you kernel informations, and the kernel is shared between
dockerhost and container.

2017-02-16 17:09 GMT+01:00 Tom Lester :

> It also seems like my sh command are not running in the container.   For
> example... If you see this Jenkins file:
>
> node {
>   ECR_LOGIN = sh (
>   script: 'aws ecr get-login',
>   returnStdout: true
>   ).trim()
>   sh "${ECR_LOGIN}"
>   docker.image('129132148275.dkr.ecr.us-east-1.amazonaws.
> com/gobuild-base:latest').inside {
>
> stage("Build") {
>   sh 'uname -a'
> }
>   }
> }
>
> If I'm understanding this correctly, uname -a should return the OS info
> from the container.   Instead it is returning the OS info of the AWS EC2
> instance.  Here's the output:
>
> Running on docker001 in 
> /home/jenkins/workspace/ity-service_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZVI3M4MT7EMS4ERA[Pipeline]
>  {[Pipeline] 
> sh[ity-service_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZVI3M4MT7EMS4ERA]
>  Running shell script
> + aws ecr get-login[Pipeline] 
> sh[ity-service_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZVI3M4MT7EMS4ERA]
>  Running shell script
> + docker login -u AWS -p
> 
>
> Login Succeeded[Pipeline] 
> sh[ity-service_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZVI3M4MT7EMS4ERA]
>  Running shell script
> + docker inspect -f . 
> 129132148275.dkr.ecr.us-east-1.amazonaws.com/gobuild-base:latest
> .[Pipeline] withDockerContainer$ docker run -t -d -u 501:501 -w 
> /home/jenkins/workspace/ity-service_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZVI3M4MT7EMS4ERA
>  -v 
> /home/jenkins/workspace/ity-service_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZVI3M4MT7EMS4ERA:/home/jenkins/workspace/ity-service_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZVI3M4MT7EMS4ERA:rw
>  -v 
> /home/jenkins/workspace/ity-service_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZVI3M4MT7EMS4ERA@tmp:/home/jenkins/workspace/ity-service_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZVI3M4MT7EMS4ERA@tmp:rw
>  -e  -e  -e  -e  -e  -e  -e 
>  -e  -e  -e  -e  -e  -e 
>  -e  -e  -e  -e  -e  -e 
>  -e  -e  -e  -e  --entrypoint cat 
> 129132148275.dkr.ecr.us-east-1.amazonaws.com/gobuild-base:latest[Pipeline] 
> {[Pipeline] stage[Pipeline] { (Build)[Pipeline] 
> sh[ity-service_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZVI3M4MT7EMS4ERA]
>  Running shell script
> + uname -a
> Linux 3cb0b774fe50 4.4.23-31.54.amzn1.x86_64 #1 SMP Tue Oct 18 22:02:09 UTC 
> 2016 x86_64 Linux[Pipeline] }[Pipeline] // stage
>
> [Pipeline] }$ docker stop --time=1 
> 3cb0b774fe50fa3e603146ffc791fc40f5464959f95bea5dbc87ac80f45ae217
> $ docker rm -f 
> 3cb0b774fe50fa3e603146ffc791fc40f5464959f95bea5dbc87ac80f45ae217[Pipeline] // 
> withDockerContainer[Pipeline] }[Pipeline] // node[Pipeline] End of Pipeline
>
>
>
> --
> 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/0c65bdef-9a3a-41ae-939b-35c41a7df8e5%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%3DnrF9ExcPQSKja-0Qe6KjMxuW_HXCrpHSaBfd_vxBFDQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: docker.inside or agnet {docker} executing as host user (jenkins) instead of the containers root

[nicolas de loof]

This is by design. If the build process doesn't run as host's user
"jenkins" then this would corrupt the workspace with files one can't
read/delete later
The fact the jenkins user doesn't exists isn't an issue.

You should prepare your docker image so it let arbitrary user create
content under /go/src, or maybe use an alternate GOPATH for this build.

2017-02-16 16:12 GMT+01:00 Tom Lester :

> My basic pipeline used to generate this output:
>
> pipeline {
> agent {
> docker {
> image 'maven:3-alpine'
> args  '-u root'
> }
> }
> stages {
> stage('Example Build') {
> steps {
> sh 'ps -ef'
> }
> }
> }
> }
>
>
>
> On Thursday, February 16, 2017 at 10:08:44 AM UTC-5, Tom Lester wrote:
>>
>> Hi all -
>>
>> I have a docker host.  Jenkins ssh's (as the user jenkins) to this host
>> via pipeline steps and builds apps inside the specified docker image.  This
>> all pretty much flows as planned.  However... when the pipeline executes a
>> "docker.insdie" or via pipeline -> agent -> docker, the docker image is
>> always launched as the jenkins user.   Even if I specify "-u root" in the
>> option, it's still has the "-u 501" which is the jenkins user.
>>
>> How can I get around this?   My build steps requires me to be able to
>> create a /go/src/ directory and the jenkins user doesn't have
>> permissions to do this (it doesn't even exist on the docker image).
>>
>> Here's the output...  you can see that the docker run actually includes
>> the -u 501 and the -u root.
>>
>>
>> [Pipeline] withDockerContainer
>> $ docker run -t -d -u 501:501 -u root -w /home/jenkins/workspace/ity-se
>> rvice_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZVI3M4MT7EMS4ERA
>> -v /home/jenkins/workspace/ity-service_tlester_jenkins-ZAK24AVE
>> OSII6FI5ZPP6GCRQQ7ISJCROTD5BZVI3M4MT7EMS4ERA:/home/jenkins/workspace/ity-
>> service_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCR
>> QQ7ISJCROTD5BZVI3M4MT7EMS4ERA:rw -v /home/jenkins/workspace/ity-se
>> rvice_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZV
>> I3M4MT7EMS4ERA@tmp:/home/jenkins/workspace/ity-service_tlester_jenkins-
>> ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZVI3M4MT7EMS4ERA@tmp:rw -e  -e
>>  -e  -e  -e  -e  -e  -e
>>  -e  -e  -e  -e  -e  -e
>>  -e  -e  -e  -e  -e  -e
>>  -e  -e  -e  --entrypoint cat maven:3-
>> alpine
>> [Pipeline] {
>> [Pipeline] stage
>> [Pipeline] { (Example Build)
>> [Pipeline] sh
>> [ity-service_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCR
>> OTD5BZVI3M4MT7EMS4ERA] Running shell script
>> + ps -ef
>> PID USER TIME COMMAND
>>  1 root 0:00 cat
>>  7 root 0:00 sh -c echo $$ > '/home/jenkins/workspace/ity-s
>> ervice_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZ
>> VI3M4MT7EMS4ERA@tmp/durable-4de63803/pid'; jsc=durable-8732979585d96e4fbb
>> b59583fb030a62; JENKINS_SERVER_COOKIE=$jsc '/home/jenkins/workspace/ity-s
>> ervice_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZ
>> VI3M4MT7EMS4ERA@tmp/durable-4de63803/script.sh' >
>> '/home/jenkins/workspace/ity-service_tlester_jenkins-ZAK24AV
>> EOSII6FI5ZPP6GCRQQ7ISJCROTD5BZVI3M4MT7EMS4ERA@tmp/durable-
>> 4de63803/jenkins-log.txt' 2>&1; echo $? > '/home/jenkins/workspace/ity-s
>> ervice_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZ
>> VI3M4MT7EMS4ERA@tmp/durable-4de63803/jenkins-result.txt'
>>  12 root 0:00 {script.sh} /bin/sh -xe /home/jenkins/workspace/ity-se
>> rvice_tlester_jenkins-ZAK24AVEOSII6FI5ZPP6GCRQQ7ISJCROTD5BZV
>> I3M4MT7EMS4ERA@tmp/durable-4de63803/script.sh
>>  13 root 0:00 ps -ef
>> [Pipeline] }
>> [Pipeline] // stage
>>
>> [Pipeline] }
>> $ docker stop --time=1 2955c0a99e3468245e1d72e9986af7
>> 20b4be5f0eba05911d6de5f1e8919e8152
>> $ docker rm -f 2955c0a99e3468245e1d72e9986af7
>> 20b4be5f0eba05911d6de5f1e8919e8152
>> [Pipeline] // withDockerContainer
>> [Pipeline] }
>> [Pipeline] // node
>> [Pipeline] End of Pipeline
>>
>>
>> --
> 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/ba344ed6-81a9-42b8-a582-688a90e3df84%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 

Re: [ANNOUNCE] Jenkins Upgrades to Java 8

[nicolas de loof]

pipeline (and docker-pipeline plugin) still rely on a plain java jenkins
agent running on build node.
so this won't change the migration issue for people with exotic hardware.

Anyway, JDK8 is available for most platforms, maybe not in the default
upstream repository, but - hey - is this such a pain to download from
Oracle ?

2017-01-20 11:23 GMT+01:00 Staffan Forsell :

> I'm thinking that we might solve it by having pipelines running in docker.
> That way only the docker host will have to have jdk8 installed and
> everything else will be scripted. Maybe it's a good push for us moving
> towards pipelines for all jobs, not just actively developed ones.
> /S
>
> On Thursday, 19 January 2017 20:51:48 UTC+1, Mark Waite wrote:
>>
>> I agree with Baptiste.  Don't mix JDK versions between master and
>> agents.  I had the illusion that the git plugin worked across that
>> environment until a bug was found which shattered that illusion.
>>
>> Mark Waite
>>
>> On Thu, Jan 19, 2017 at 9:51 AM Baptiste Mathus  wrote:
>>
>>> There's a strong debate about this. I would recommend not doing so
>>> (mixing versions). I've seen again a ClassFormatError happen in a
>>> production system because of that (JDK7 on agent, JDK8 on master). It will
>>> happen to work, but might start failing probably when you don't expect it.
>>> This is probably not worth the risk.
>>>
>>> For your question, just checked again: being a fan of config mgmt myself
>>> and so, I understand the desire to use official upstream packages. But
>>> sometimes, you have to diverge for various reasons.
>>>
>>> I just tested it and this works totally fine on Ubuntu:14.04 : download
>>> JDK from http://www.oracle.com/technetwork/java/javase/downloads
>>> /jdk8-downloads-2133151.html for your system, uncompress it, add its
>>> bin directory in the PATH, done you have a JDK8 on 14.04.
>>>
>>> And if really, you are using a special system, far more funky than that,
>>> as Jesse said already: you can then just connect to those using ssh during
>>> a build, and would work perfectly fine too.
>>>
>>> HTH
>>>
>>> 2017-01-19 12:42 GMT+01:00 Staffan Forsell :
>>>
 Will this also mean that the agents/slaves will require java 8? Will
 the ssh-slaves plugin install a java 8 jre if one is not available?
 We have some slaves building on stuff on Ubuntu 14.04 LTS (and
 older...) which still does does not have a backported java 8 (See
 https://bugs.launchpad.net/trusty-backports/+bug/1368094). This is a
 Ubuntu LTS release with 2 years of support left which is used as the base
 OS for some machines, hence the reluctance to upgrade or use non standard
 package repositories.
 We have java 8 support on mainline but we still need long term support
 for branches of delivered machines and these branches are built using
 jenkins.
 So basically will it be possible to still run ssh slaves on OS:es
 not-supporting jdk8 by default?

 /Thanks
 Staffan

 On Tuesday, 17 January 2017 14:48:37 UTC+1, Baptiste Mathus wrote:
>
> Hello,
>
> Please read the announcement on https://jenkins.io/blog/201
> 7/01/17/Jenkins-is-upgrading-to-Java-8/, especially if you are still
> running Jenkins on Java 7 VM.
>
> Thank you
>
 --
 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/ms
 gid/jenkinsci-users/bcdf871b-8cc7-4e29-a139-e85a8b8e37d1%
 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-use...@googlegroups.com.
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/jenkinsci-users/CANWgJS6qjH5DQvTpRix_hWcSLm_meuz59L%3D__
>>> j7k3GqcwTWH4g%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/
> 

Re: Docker Build & Publish using --force=true in Pipeline?

[nicolas de loof]

why not just use a plain sh "docker push foo:tag" step ? I never understood
what this docker.xx basic methods where for, as they just replicate the
plain docker CLI without extra features

2017-01-20 3:46 GMT+01:00 :

> Hi David!
>
> I'm not sure that follows. According to the plugin page (
> https://wiki.jenkins-ci.org/display/JENKINS/CloudBees+
> Docker+Pipeline+Plugin), v1.4 includes a change to "Handle recent
> deprecation of docker tag --force", so I've got some reason to believe that
> it doesn't just run docker commands. I'm certainly not running a docker
> command with --force in it.
>
> Jack
>
> On Thursday, January 19, 2017 at 7:56:33 PM UTC-5, David Karr wrote:
>>
>> The plugin just runs docker commands. If the version of docker you
>> have installed on the box doesn't support a "--force" parameter, it
>> will fail.  I have no idea what the history is of that, but it seems
>> likely this is the cause of your problem.
>>
>> On Tue, Jan 17, 2017 at 12:58 PM,   wrote:
>> > All right, I was incorrect about one thing- this was NOT due to Docker
>> Build
>> > & Publish, but Docker Pipeline (formerly CloudBees Docker Pipeline).
>> > Supposedly, this was also resolved back in 1.4; I have 1.9.1. Can
>> anyone
>> > think of why I'm experiencing this issue in Pipeline?
>> >
>> > Thanks!
>> > Jack
>> >
>> > On Monday, January 16, 2017 at 9:56:55 PM UTC-5, jbr...@snapapp.com
>> wrote:
>> >>
>> >> Hi all,
>> >>
>> >> I'm running into an issue when executing a job to build and publish an
>> >> image to a registry:
>> >>
>> >> + docker tag --force=true foo:tag foo:tag
>> >> unknown flag: --force
>> >> See 'docker tag --help'.
>> >>
>> >> The relevant bit from my Jenkinsfile:
>> >>
>> >> node {
>> >>   stage('deploy'){
>> >> git branch: 'feature/branch', credentialsId: 'foo-key', url:
>> >> 'g...@github.com:bar/baz.git'
>> >> withDockerRegistry([credentialsId: 'ecr:us-east-1:foo-key', url:
>> >> 'https://etcetera/']) {
>> >> docker.image('foo:tag').push()
>> >> }
>> >>
>> >> Now, I see that the --force=true issue was resolved
>> >> (https://issues.jenkins-ci.org/browse/JENKINS-36188), and I've
>> confirmed
>> >> that my plugin is up to date. Has anyone run into this? I'm planning
>> to open
>> >> an issue for this unless I'm missing something.
>> >>
>> >> Thanks!
>> >> Jack
>> >
>> > --
>> > 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/071e74d8-
>> c5e0-4c4e-afb3-3a8e550aea6d%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/0ecdf71e-6627-45e5-bfff-7d30a93d1998%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/CANMVJzkrP50AC8WXZJG1smW4_-YdVv81L1uotmrLDxdSba4ciQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Pipeline : How could I access the git repository cloned at job start

[nicolas de loof]

the Jenkinsfile detection indeed relies on a git clone on master, but this
isn't considered a workspace. Also, it might not be necessary for some
integrations, typically one could access this specific file remotely (not
sure about the actual implementation)

To get the exact commit that triggered a build, your Jenkinsfile should
look like :

node() {
   checkout scm
   ...
}



2016-12-05 9:30 GMT+01:00 Christoph Nenning :

> Hi,
>
>
> > Where do you put this ws step ?
>
> You can put it at the beginning of your Jenkinsfile
>
>
> > My concern is how to benefit from the SCM schedule and checkout
> > phase made to retrieve the so called jenkinsfile, i.e. the script
> > (and possible libraries) that is executed to run the pipeline.
>
> AFAIK you cannot use the workspace that jenkins creates to checkout
> Jenkinsfile.
>
> But you can checkout the same repo (or other polled SCM URLs) with this
> command:
>
> checkout scm
>
>
> Regards,
> Christoph
>
>
>
> > From: Jean-Luc Pinardon 
> > To: jenkinsci-users@googlegroups.com,
> > Date: 05.12.2016 09 <05%2012%2020%2016%2009>:05
> > Subject: Re: Jenkins Pipeline : How could I access the git
> > repository cloned at job start
> > Sent by: jenkinsci-users@googlegroups.com
> >
> > Hello,
> >
> > Thanks for your answer.
> > But I am not sure to understand.
> > Where do you put this ws step ?
> > I am not sure to have been clear enough.
> > My concern is how to benefit from the SCM schedule and checkout
> > phase made to retrieve the so called jenkinsfile, i.e. the script
> > (and possible libraries) that is executed to run the pipeline.
> >
> > 2016-12-03 7:37 GMT+01:00 Sam K :
> > I just use a ws('') {
> >git url:. , branch: 'master'
> > }
> >
> > and now all the cloned content is within the directory I want.
> >
> > On Tuesday, November 29, 2016 at 1:14:03 AM UTC-8, Jean-Luc Pinardon
> wrote:
> > Dear all,
> >
> > I am exploring pipeline features, and I fall into a problem.
> > The repository is indeed correctly cloned at job start and the
> > "jenkinsfile" is run.
> > But I "discover" that I cannot access the cloned files from within
> > the stages within nodes. Just because, the workspace used at job
> > begin is certainly not the same as the workspace within the nodes.
> >
> > So, my question is : is there a way to make available the initially
> > cloned files all over the pipeline, or should I clone the repository
> > once more within the first stage and then stash the files I need.
> >
> > Thanks for your help.
> > J.L.P.
> > --
> > 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/qzBWmFHOmoI/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/aca57995-52c2-42f6-94aa-5cee7e434b29%
> > 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/CALijN65Q_TE2zj5NhwJpoi5%2BW3jX-
> > vVXds0QVJrXO4iKs72Wkw%40mail.gmail.com.
> > For more options, visit https://groups.google.com/d/optout.
>
>
> This Email was scanned by Sophos Anti Virus
>
> --
> 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/OFE7E55BA0.1AC16254-ONC1258080.002E9363-C1258080.
> 002EBDB0%40lex-com.net
> 
> .
>
> 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/CANMVJzmgh7jBd%2B6JbL_16J5TsnsAMpDmOiEX4WkK6vmqzfoWUQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins Pipeline : How could I access the git repository cloned at job start

[nicolas de loof]

by pipeline design, you need to define node usage (so workspace) and how
long same node has to be used to run your build. This allows to distribute
the build steps on multiple nodes (including parallel execution). For
simplest scenario, you can just wrap the whole pipeline with a `node() { }`
block.



2016-11-29 10:14 GMT+01:00 Jean-Luc Pinardon :

> Dear all,
>
> I am exploring pipeline features, and I fall into a problem.
> The repository is indeed correctly cloned at job start and the
> "jenkinsfile" is run.
> But I "discover" that I cannot access the cloned files from within the
> stages within nodes. Just because, the workspace used at job begin is
> certainly not the same as the workspace within the nodes.
>
> So, my question is : is there a way to make available the initially cloned
> files all over the pipeline, or should I clone the repository once more
> within the first stage and then stash the files I need.
>
> Thanks for your help.
> J.L.P.
>
> --
> 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/067b2647-bb7a-44c6-81ca-5fa2afa1290d%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/CANMVJzmEO5i2CViyS9bumPu%3DD7hcWAgSnbqprJJNYzH_OX5C%3DQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins with Docker

[nicolas de loof]

RTFM :P
https://github.com/jenkinsci/docker#preinstalling-plugins

2016-10-19 15:47 GMT+02:00 :

> I can launch a Docker container with Jenkins but I still have to login to
> the Jenkins URL and perform the final steps of adding plugins.
>
> Does anyone know how to install or script in a way that doesn't require
> these manual 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/c5e81fa8-6d69-4c8e-9fb4-64179c566e2d%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/CANMVJzkhGODOzWxrxZrTP-x%3DiLxm4Pw%3D_fiY%3Dfb6U4nu1euRcw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker Slaves plugin - how to specify volumes

[nicolas de loof]

The whole build agent root directory is managed as a docker volume, and 
retrieved from previous build, so you can easily benefit such caching if 
you configure maven to use adequate path for local repository (which should 
be the case by default, as /home/jenkins is slave root).

We also considered to offer an option to cache some path, comparable to 
travis-ci approach (based on tar.gz), so typically let end-user configure 
maven local repository as "cached". Backed could rely on additional volumes 
for this purpose, but definitively not on bind-mounts :P. This would let us 
investigate scalability challenge to distribute such a cache, maybe just by 
relying on docker volume-plugin features (but then relying on proprietary 
API), or maybe by using jenkins as a volume replication facility, *à la* 
TravisCI.

Le dimanche 16 octobre 2016 00:44:12 UTC+2, Qiang a écrit :
>
> Hi, Nicolas,
>
> One example I can think of:  for maven build, we want to cache the 
> downloaded dependencies so we don't have to download them every time.
>
> So in that case, I was thinking to cache on the host, or a data volume. 
> Any suggestions?
>
> Thanks,
> Qiang
>
> On Saturday, October 15, 2016 at 11:59:08 AM UTC-5, Qiang wrote:
>>
>>
>> Thank you for posting the response ! I do need to rethink my strategy 
>> now. Even though I need to solve legacy problems in a short term , I agree 
>> that it does not become a requirement :)
>>
>> So for moving data between containers , what options can I explore ? And 
>> is there instruction to use side containers ? I was not able to find much 
>> documentation.
>>
>> Regards,
>> Qiang
>>
>>
>>
>> Hi,
>>
>> There's no technical limitation to use this option (we actually already 
>> support it to allow docker.sock bind mount on a dedicated side container), 
>> but our experience is most user use this for bind-mount, which result in 
>> permission issues and in most case are just short terms workarounds to 
>> introduce bad practices. So we decided *not* to expose this option to 
>> end-user.
>>
>> IIUC your use case (from some private email) some legacy jobs you run 
>> rely on a NFS server to host project dependencies. Relying on a bind mount 
>> would make your build fragile and non-reproducible. You better should 
>> create a project specific docker image, to include those dependencies 
>> (assuming you can't update your build script to a modern dependency 
>> resolution approach).  
>> For sure this require some effort to migrate your builds, but I can't 
>> consider "*legacy bad practice*" as a valid use-case :P
>>
>>
>> Le vendredi 14 octobre 2016 15:55:01 UTC+2, Qiang a écrit :
>>>
>>> hi,
>>>
>>> How can I set container options to the Docker slave such as volume 
>>> settings? I need to mount a host directory to the container.
>>>
>>> So far, the only option I can see is to define the slave container 
>>> image, and side container image as following:
>>>
>>>   dockerNode(image: "maven:3.3.3-jdk-8", sideContainers: 
>>> ["selenium/standalone-firefox"]) 
>>>
>>> How do I pass "-v" or "--volumes-from" to the slave container?
>>>
>>> Regards,
>>> Qiang
>>>
>>>
>>>
>>

-- 
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/f788cd3e-fd30-44aa-b2e8-34e20582827a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker Slaves plugin - how to specify volumes

[nicolas de loof]

Hi,

There's no technical limitation to use this option (we actually already 
support it to allow docker.sock bind mount on a dedicated side container), 
but our experience is most user use this for bind-mount, which result in 
permission issues and in most case are just short terms workarounds to 
introduce bad practices. So we decided *not* to expose this option to 
end-user.

IIUC your use case (from some private email) some legacy jobs you run rely 
on a NFS server to host project dependencies. Relying on a bind mount would 
make your build fragile and non-reproducible. You better should create a 
project specific docker image, to include those dependencies (assuming you 
can't update your build script to a modern dependency resolution approach). 
 
For sure this require some effort to migrate your builds, but I can't 
consider "*legacy bad practice*" as a valid use-case :P


Le vendredi 14 octobre 2016 15:55:01 UTC+2, Qiang a écrit :
>
> hi,
>
> How can I set container options to the Docker slave such as volume 
> settings? I need to mount a host directory to the container.
>
> So far, the only option I can see is to define the slave container image, 
> and side container image as following:
>
>   dockerNode(image: "maven:3.3.3-jdk-8", sideContainers: 
> ["selenium/standalone-firefox"]) 
>
> How do I pass "-v" or "--volumes-from" to the slave container?
>
> Regards,
> Qiang
>
>
>

-- 
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/06362a69-ead3-440f-a636-283707f541e2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker Slaves Plugin Exception in Pipeline

[nicolas de loof]

Hi.

Identified the root cause, a fix will be released asap.

Le 11 oct. 2016 15:38, "Qiang Ma"  a écrit :

> Hi, all,
>
> Have you successfully run the sample of Docker Slaves Plugin?
>
> I am using Docker Slaves Plugin v 1.0.4, on Jenkins 2.6.
> Copied the sample (Pipeline job support) from
> https://github.com/jenkinsci/docker-slaves-plugin
>
> The images were downloaded, git checkout happened,  but the pipeline
> finished with error below:
>
> [Pipeline] }
>
> [Pipeline] // dockerNode[Pipeline] End of 
> Pipelinejava.lang.NullPointerException
>   at 
> it.dockins.dockerslaves.drivers.CliDockerDriver.applyHints(CliDockerDriver.java:236)
>   at 
> it.dockins.dockerslaves.drivers.CliDockerDriver.launchSideContainer(CliDockerDriver.java:366)
>   at 
> it.dockins.dockerslaves.DefaultDockerProvisioner.createSideContainers(DefaultDockerProvisioner.java:122)
>   at 
> it.dockins.dockerslaves.DefaultDockerProvisioner.launchBuildContainers(DefaultDockerProvisioner.java:99)
>   at 
> it.dockins.dockerslaves.DefaultDockerProvisioner.launchBuildProcess(DefaultDockerProvisioner.java:139)
>   at it.dockins.dockerslaves.DockerLauncher.launch(DockerLauncher.java:56)
>   at hudson.Launcher$ProcStarter.start(Launcher.java:381)
>
>
>
> Any comment/help is appreciated.
>
> Regards,
> Qiang
>
> --
> 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/59c6a543-8e06-445f-9098-30024e83e2f6%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/CANMVJzmgWWDOtebiqGVtUJUijdyE%2B6WppCWVcSFh44Z9WCHVMA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upgrade manually doesn't works

[nicolas de loof]

Your custom image should be built using a Dockerfile to download a specific
version of jenkins war (just like the official image does)
Docker should be used with "immutable infrastructure" in mind, don't try to
run upgrades in a container, this isn't a VM

2016-10-07 10:36 GMT+02:00 YusufSalahAdDin <alagun...@gmail.com>:

> Ok, i feel so good with this, but i have a problem with it: i'm using a
> custom image that download this war and install it, using CentOS, you know,
> for get more control with this, but, i have a problem upgrading it, and you
> can see in other thread that i post in this group.
>
> El viernes, 7 de octubre de 2016, 3:30:45 (UTC-5), nicolas de loof
> escribió:
>>
>> Don't update jenkins.war inside container, just pull a newer docker image
>> and start a fresh new container using same jenkins_home volume
>>
>>
>> 2016-10-07 10:28 GMT+02:00 YusufSalahAdDin <alag...@gmail.com>:
>>
>>> I installed jenkins in docker container and i want update it.
>>>
>>> So, manually, using root user i downloaded the war file and replace it
>>> with old war file, i verified it:
>>>
>>> jenkins@fdfeef9f1f14:/$ java -jar /usr/share/jenkins/jenkins.war
>>> --version
>>> 2.24
>>>
>>> But, when i go to jenkins dashboard, well, i still have the old version:
>>> 2.23.
>>>
>>> I restarted jenkins using url: jenkins.mydomain.com/restart, many
>>> times, but i have still the same jenkins version.
>>>
>>> What i have wrong?
>>>
>>> Thanks guys!
>>>
>>> --
>>> 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/ms
>>> gid/jenkinsci-users/e6848710-50b5-49be-af1e-5508f7db22f4%
>>> 40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/e6848710-50b5-49be-af1e-5508f7db22f4%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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/6aea7d4c-9206-4ab7-ba42-6bedc88d7d67%40googlegroups.
> com
> <https://groups.google.com/d/msgid/jenkinsci-users/6aea7d4c-9206-4ab7-ba42-6bedc88d7d67%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> 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/CANMVJzmD2oYf0FddRkLsCJunn3X0QBDMji_gcwVCYU1RwWtSiw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upgrade manually doesn't works

[nicolas de loof]

Don't update jenkins.war inside container, just pull a newer docker image
and start a fresh new container using same jenkins_home volume


2016-10-07 10:28 GMT+02:00 YusufSalahAdDin :

> I installed jenkins in docker container and i want update it.
>
> So, manually, using root user i downloaded the war file and replace it
> with old war file, i verified it:
>
> jenkins@fdfeef9f1f14:/$ java -jar /usr/share/jenkins/jenkins.war
> --version
> 2.24
>
> But, when i go to jenkins dashboard, well, i still have the old version:
> 2.23.
>
> I restarted jenkins using url: jenkins.mydomain.com/restart, many times,
> but i have still the same jenkins version.
>
> What i have wrong?
>
> Thanks guys!
>
> --
> 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/e6848710-50b5-49be-af1e-5508f7db22f4%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/CANMVJzkZeEXU1uD-HAu12qoKsF10NM8DM8rOwOcGCT1aF8_LEw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Jenkins in container is offline

[nicolas de loof]

Try running this :

*docker run --rm -it jenkins bash*

jenkins@b2b041c448b1:/$ *ping google.com *

PING google.com (172.217.19.142): 56 data bytes

64 bytes from 172.217.19.142: icmp_seq=0 ttl=37 time=0.147 ms

64 bytes from 172.217.19.142: icmp_seq=1 ttl=37 time=0.338 ms

^C--- google.com ping statistics ---





2016-09-21 22:25 GMT+02:00 Hung Suen :

> I posted the topic to Jenkins developers. Should have posted it here.
> https://groups.google.com/d/topic/jenkinsci-dev/LCPjMbKCmGM/discussion
>
> --
> 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/b3c1a12a-f2f7-44ab-9227-9546cd228853%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/CANMVJzmFh31Nwm13nBzHQOZfxRB-a12npV6h2Y3qwA_2Bc%3DcRw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to run jenkins in jdk 1.6

[nicolas de loof]

You have to distinguish the JDK running jenkins and the JDK building your
project. You can configure jenkins to build with arbitrary JDK, using Java
installations on global configuration and selecting the adequate one for
your jobs

2016-08-26 11:22 GMT+02:00 Panikera Raj :

> Hi All,
>
> I have a problem, please do help me on this
>
> First I have installed JDK 1.7 in windows-64 bit machine, then I have
> started jenkins, in jenkins i have created some projects Called Android and
> I was able executing successfully, But later I am facing some issue in
> Android project, so I have downgraded My Java JDK to 1.6, Here only my
> actual problem started,
>   After downgrading java version I am trying run jenkins, but I am
> facing blow exception.
> D:\Jenkins>java -jar jenkins.war
> Jenkins requires Java7 or later, but you are running 1.6.0_21-b06 from
> C:\Program Files\Java\jdk1.6.0_21\jre
> java.lang.UnsupportedClassVersionError: 50.0 at Main.main (Main.java:83)
>
> D:\Jenkins>
>
>
> Please let me know how to resolve this issue. I don't have other chance to
> upgrade the Java version to 1.7, I have to use 1.6 only please help me on
> this.
> your help will be highly appriciated
>
> -Panikera
>
>
>
> --
> 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/CAEzR4Zxk8CKY4-zGmPGfve2K5T6RiYb2Oevg2xwcTc7u
> nh273Q%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/CANMVJzkxY_RQLWuO5Bff1ekGAZrnqTWxfb1bwvT0yUwA0LJg9g%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: scm.gitTool in Jenkinsfile

[nicolas de loof]

Any reason you don't set git in default path ? Would be so simpler ;)
Le 27 juil. 2016 10:56 PM, "Nigel Magnay"  a écrit :

> No, as it's not on the path so would not be found.
>
> Oddly, if I do
> scm.gitTool = 'win git'
> echo scm.gitTool
>
> it responds with 'null' - so something is odd in the field setter :-/
>
>
> On Wed, Jul 27, 2016 at 9:53 PM, Mark Waite 
> wrote:
>
>> Have you tried configuring your git executable to be "git" rather than
>> "/usr/bin/git"?  That's what I've used in multi-platform environments and
>> it has worked well for me.
>>
>> Mark Waite
>>
>> On Wed, Jul 27, 2016 at 1:57 PM Nigel Magnay 
>> wrote:
>>
>>> In a bitbucket-sourced multibranch repository, I need to ensure the git
>>> checkout doesn't occur with /usr/bin/git, but with a tool that stands a
>>> chance of executing on Windows.
>>>
>>> I had rather hoped it would simply be the case of doing
>>>
>>> scm.gitTool = 'win git';
>>>
>>> before my
>>> checkout scm
>>>
>>> But it still seems to insist on using the wrong binary (even though
>>> there appears to be a setter, as I had to approve it in the script console).
>>>
>>> What have I missed?
>>>
>>>
>>>
>>> --
>>> 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/CAPYP83SpLOHmoJBupi6Q0QV6TDjKOf9EYtbXrtj3NZ0L9f1PTg%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/CAO49JtG8AdnRuA8LX3xSgkpD7p9jepaec%2BjxmaLg7TRZLaBi8A%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/CAPYP83Qxg3RtukcGLL8Ouf43x3VpJmaUS0nr0zsZhFkM1Yr7Yg%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/CANMVJz%3DZceaH3FQZ4B6oXuUaHVtLXTqTjaQjC1ra83Zbgx561A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker Slave : saving artifacts

[nicolas de loof]

Here is my way to do this :

I build the binary using docker and a build Dockerfile

then I create a container from resulting image and cp artifact from it into
local working directory - you can't cp from image, so need to create a
container, no need to start it, but need to create one

then I build a second docker image using a production Dockerfile, to
include built artifact, and push to repo (maybe you don't need this step,
if you don't use docker as target artifact)

sample here :
https://github.com/cfpio/callForPapers/blob/master/Jenkinsfile.sh


2016-06-10 20:07 GMT+02:00 Matthew Ceroni :

> Using a docker container as a slave to build RPM packages.
>
> My ideal setup would be to have one job build the RPM and then a dependent
> job upload the RPM to our internal repositories. However I haven't figured
> out yet how to get the RPM outside the container so other jobs can pick it
> up. Once the job finishes, the container is torn down.
>
> Looking at the settings for the docker plugin the Remote Root FS setting
> and volume mapping seem to be what I would want, I use a volume mapping
> from ${WORKSPACE} to the /home/jenkins directory inside the container (as
> that is where the build is happening) but I don't think ${WORKSPACE} was
> expanded to its value as upon container creation it failed.
>
> --
> 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/f85895a6-87ab-4c4f-9931-9140837924a2%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/CANMVJzmQDgNsWNcP%2BBtU4iqOLx9_Vyr99RY%3D9%2BDx76fK4ROQqA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Blue ocean plugin release

[nicolas de loof]

http://hub.docker.com/r/jenkinsci/blueocean indeed is (at this time) a
demo-only docker image for Blue Ocean, running SNAPSHOTs.


2016-05-30 8:44 GMT+02:00 Michael Neale :

> Hi - hopefully sometime soon there will be some beta version. At the
> moment a few critical features are missing to make it useful.
>
> If you want to try it I believe there is a docker image which will launch
> it - but not with your existing jenkins instance of course.
>
> On Monday, May 30, 2016 at 7:37:15 AM UTC+10, redpublic wrote:
>>
>> As far as I understand it's in active development. When it will be
>> possible to install some alpha-beta from Jenkins plugin manager?
>>
>> On Monday, May 30, 2016 at 12:29:53 AM UTC+3, Thorsten Scherler wrote:
>>>
>>> https://github.com/jenkinsci/blueocean-plugin
>>>
>>> it is already, HTH.
>>>
>>> salu2
>>>
>>> On Sunday, May 29, 2016 at 11:17:26 PM UTC+2, redpublic wrote:

 When Jenkins Blue Ocean plugin is going to be available?

>>> --
> 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/e1330e52-44c3-4523-a4ac-cebdfe6e6603%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%3D5c%3DPSD%2BHzRsz%2B4P%2BuuJQ8EZim0J4eZUHkZDbsh1rPUg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] A new user experience project for Jenkins

[nicolas de loof]

2016-05-27 20:34 GMT+02:00 Stephen Connolly :

> The Jenkins specific tasks should be mostly single purpose and logicless
> in my view.
>
> The complex logic should be testable outside of Jenkins.
>
> But building complex logic in groovy "just because it is there" and not
> "because we cannot do it elsewhere" is the problem my rant is directed at
>


This was my exact concern with build-flow, as I've seen more and more
people abuse it (imo) using more and more groovy logic there.
My preference goes to very basic pipeline scripting to inject credentials,
then invoke a file I use to name Jenkinsfile.sh, where all the build take
place ... and that I can test on my computer.



>
>
> On Friday 27 May 2016, Maciej Jaros  wrote:
>
>> Stephen Connolly (2016-05-27 12:12):
>>
>>
>>
>> On 27 May 2016 at 07:59, Craig Rodrigues  wrote:
>>
>>> Hi,
>>>
>>> The new Jenkins UI looks nice, and will be a big improvement over the
>>> existing UI.
>>>
>>> The original selling point of Jenkins was that even with the simplistic
>>> forms-based UI,
>>> someone could fill out a relatively simple form, and have a continuous
>>> integration pipeline.
>>> I have met people who were general devops and scripting people, and
>>> could use Jenkins quite nicely.
>>>
>>> While I understand the motivation for Pipeline (previously known as
>>> Workflow), I can't say I'm very happy with the results.
>>>
>>> Here are some of the pain points I've encountered with Pipeline scripts:
>>>
>>>- Other than the most trivial of scripts, you need to be a
>>>knowledgable Groovy programmer.  For example, to make a global variable,
>>>you need to use a @Field.  (What?!)  Most scripting and devops people 
>>> that
>>>I know don't really know Groovy.
>>>
>>> So in my personal opinion, this is a sign of People Doing Things Wrong™
>>
>> By this I mean that your Jenkinsfile should *not* be doing complex
>> things. You should have shell scripts or equivalent to do the complex
>> functionality. That lets you test each individual step in the phase on
>> local developer machines. Then your pipeline should end up mostly being
>>
>>
>> But you cannot test everything locally, because you e.g. don't have build
>> parameters, you might not have certain SSH credentials defined... That said
>> I do tend to move everything to scripts, but this really defeats the
>> purpose of almost all Jenkins plugins... And plugins gives you some
>> integrations (especially with credentials) you don't have in scripts. And
>> it's much easier to add build step for triggering e.g. call of another
>> project and passing all parameters to it from current build (which BTW is
>> overly hard with Groovy).
>>
>> Regards,
>> Nux.
>>
>> --
>> 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/fac125e7-9e6c-46f1-bbe7-42067660d98c%40mol.com.pl
>> 
>> .
>> 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%2BnPnMxSo6%3D9WaaBUZYxdYfMsj%3DRgbcrQyO3F3J%3D2oUuXcuoFA%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/CANMVJzk-wL%2BS85jcbp2%3DW69qOjKvxwNQ_BssRL8%2BavW98brHUA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Blue Ocean] A new user experience project for Jenkins

[nicolas de loof]

source code actually has been moved to
https://github.com/jenkinsci/blueocean

2016-05-27 8:16 GMT+02:00 Dirk Heinrichs :

> Am 27.05.2016 um 00:21 schrieb James Dumay:
>
> Today we’ve made the source code 
> available on Github, written a blog post
>  and created
> a video  explaining the
> project in more detail.
>
>
> Unfortunately, the blog post is not completely readable, because the
> schedule on the right side overlapps the text.
>
> Bye...
>
> Dirk
> --
>
> *Dirk Heinrichs*, Senior Systems Engineer, Engineering Solutions
> *Recommind GmbH*, Von-Liebig-Straße 1, 53359 Rheinbach
> *Tel*: +49 2226 159 (Ansage) 1149
> *Email*: d...@recommind.com
> *Skype*: dirk.heinrichs.recommind
> www.recommind.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/53fe65f9-348b-f110-c9f6-578d6eaa18be%40recommind.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/CANMVJzm_SMmWeS93A7U9x19Z%2BG_4oEzaV_-nMO%3D6Y4pb3v2VGw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkinsci/jenkins docker image ssl issues

[nicolas de loof]

ok, then you can use an init.groovy file for this purpose (stored in
jenkins_home)

2016-05-25 19:35 GMT+02:00 Zoratto Thomas <thomas.zora...@gmail.com>:

> Docker exec is ok if you don't want to persist this configuration
>
> Le 25 mai 2016 à 19:07, nicolas de loof <nicolas.del...@gmail.com> a
> écrit :
>
> Can't you just docker exec this jenkins container and configure git to
> accept this self-signed certificate ? see
> https://git-scm.com/docs/git-repo-config/1.4.3#http.sslCAPath
>
>
> 2016-05-25 18:25 GMT+02:00 Zoratto Thomas <thomas.zora...@gmail.com>:
>
>> Hello,
>>
>> You can build your own Jenkins image based on the official one but with
>> the Java trust store configured with your certs.
>>
>> Or you could use ssh (or event git protocol?) instead of https.
>>
>> The plugin you are talking about seems broken and no longer maintained
>>
>> Thomas
>>
>> Le 25 mai 2016 à 15:37, christian polzer <christian.pol...@gmail.com> a
>> écrit :
>>
>> Hello,
>>
>> I am currently trying to evaluate an update to Jenkins 2.x here at work
>> with the actual docker image of jenkinsci/jenkins.
>>
>> For this I need to git pull my git repo from a selfhosted Bitbucket/Stash
>> Server via https.
>>
>> Of course, the docker image's JVM has no clue of that cert.
>>
>> So I wanted to give the plugin "skip-certificate-check" a try, which
>> isn't helping in this case.
>>
>> After several hours of trying and searching my way through the interwebz,
>> I am turning to this group, with the hope that anyone here has solved that
>> problem before?
>>
>> Kind regards,
>>
>> Chris
>>
>>
>>
>>
>> --
>> 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/8c0b64a6-564b-4f61-aa06-e2dba5da3084%40googlegroups.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/8c0b64a6-564b-4f61-aa06-e2dba5da3084%40googlegroups.com?utm_medium=email_source=footer>
>> .
>> 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/E2D5610F-CB6B-4762-BA0C-8BA9F1E5ABC7%40gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/E2D5610F-CB6B-4762-BA0C-8BA9F1E5ABC7%40gmail.com?utm_medium=email_source=footer>
>> .
>>
>> 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%3DA9PPABSyOQeJ3ekXwDL3XnFLP-zHioqWs3WxNwSOYPA%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CANMVJz%3DA9PPABSyOQeJ3ekXwDL3XnFLP-zHioqWs3WxNwSOYPA%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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/C6C3D2D8-7B24-4B71-A58C-892537F2DAC6%40gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/C6C3D2D8-7B24-4B71-A58C-892537F2DAC6%40gmail.com?utm_medium=email_source=footer>
> .
>
> 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/CANMVJzkWK9zLoYr9-ijvTtEa-kZ%3D0qHvrRMj_bgaqvt-7zv4Bw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkinsci/jenkins docker image ssl issues

[nicolas de loof]

Can't you just docker exec this jenkins container and configure git to
accept this self-signed certificate ? see
https://git-scm.com/docs/git-repo-config/1.4.3#http.sslCAPath


2016-05-25 18:25 GMT+02:00 Zoratto Thomas :

> Hello,
>
> You can build your own Jenkins image based on the official one but with
> the Java trust store configured with your certs.
>
> Or you could use ssh (or event git protocol?) instead of https.
>
> The plugin you are talking about seems broken and no longer maintained
>
> Thomas
>
> Le 25 mai 2016 à 15:37, christian polzer  a
> écrit :
>
> Hello,
>
> I am currently trying to evaluate an update to Jenkins 2.x here at work
> with the actual docker image of jenkinsci/jenkins.
>
> For this I need to git pull my git repo from a selfhosted Bitbucket/Stash
> Server via https.
>
> Of course, the docker image's JVM has no clue of that cert.
>
> So I wanted to give the plugin "skip-certificate-check" a try, which isn't
> helping in this case.
>
> After several hours of trying and searching my way through the interwebz,
> I am turning to this group, with the hope that anyone here has solved that
> problem before?
>
> Kind regards,
>
> Chris
>
>
>
>
> --
> 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/8c0b64a6-564b-4f61-aa06-e2dba5da3084%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/E2D5610F-CB6B-4762-BA0C-8BA9F1E5ABC7%40gmail.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%3DA9PPABSyOQeJ3ekXwDL3XnFLP-zHioqWs3WxNwSOYPA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Upgrading to Jenkins 2.2 Breaks Build Flow Plugin DSL Editing

[nicolas de loof]

Pipeline is not perfect but definitively is more mature than build-flow has
ever been (*)

(*) I'm build-flow initial author, and gave up for major technical
limitations

2016-05-24 16:48 GMT+02:00 Stefan Thomasson :

> It is said that jenkins 2.x should be backwards compatible so I not really
> sure why buildflow break the gui. For me it only dissapear when navigating
> using the tab, so scrolling usually works.
> Right now I do not consider pipeline mature enough for use in production
> but you may be of other opinion.
>
>
> 24 maj 2016 kl. 16:09 skrev AJ Ferrigno :
>
> Hello,
>
> We have been using the Build Flow plugin for about a year now. We have a
> large block of DSL which we mostly needed for parallel execution.
>
> I have just tried upgrading to Jenkins 2.2, and I am now unable to edit
> the DSL in our existing Build Flow job. I open the job, click
> configuration, scroll down to where the DSL would be, and the entire DSL
> just disappears from view. The only way I can edit the DSL is to navigate
> to the config.xml file on the master, change it there, and then reload
> configuration from disk. Obviously, this is an inconvenience.
>
> I have tried making a brand new (blank) Build Flow job and the same issue
> happens. Once I paste in my DSL, save it, then return to the configuration
> and scroll down, the DSL box disappears.
>
> Upgrading to Jenkins 2.6 does not fix the issue (in fact, it breaks other
> things sadly). Upgrading all my plugins does not fix the issue.
>
> It looks like this plugin is deprecated in favor of Pipelines and may no
> longer be supported. I will need to investigate Pipelines to see how to
> move away from our DSL. However, there was a change this month to link it
> to Pipelines. Is it possible to get this problem fixed as well? I even
> volunteer myself to fixing it, although I am not a Jenkins developer and
> wouldn't know where to start debugging this thing. I'm hoping someone else
> would understand why something would disappear from the page as a result of
> the 2.2 upgrade. Maybe after having it explained, I can make the hopefully
> small code change to get it fixed.
>
> Thanks in advance,
> AJ
>
> --
> 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/9c600c2b-9a10-4f1b-87ed-bf6a8bf90dd6%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/E7D7FABA-27AA-4C7F-B93C-735C4F293241%40gmail.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/CANMVJzm-VDKN6nrEyujmC53YezQCjRYY%2BcKazR%2Be3fzEkP5%3DHA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: latest Jenkins on Docker

[nicolas de loof]

use https://hub.docker.com/_/jenkinsci/jenkins

jenkins official image only do host LTS releases.

2016-05-19 9:47 GMT+02:00 Jeeva Chelladhurai :

> Where I can find the latest docker image for Jenkins?
> https://hub.docker.com/_/jenkins/ does not have Jenkins 2.0 or later
> images...
>
>
> Thanks,
> Jeeva
>
> --
> 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/a1af84d1-7bb0-48a9-8e05-36730376cff4%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%3DsB7wFnfreZhuP%3D9%2B80KRRtFNyaKfKF3ezXbUe6YR7TQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to mount volume in a docker job inside a dockerized jenkins

[nicolas de loof]

The reason it works like this is the bind mount is done from host, so need
a valid fully qualified host path, but the `pwd` command is ran inside
jenkins container, so resolves to container filesystem.
A possible alternate approach is for you to rely on " --volumes-from
$(hostname) ", as a container hostname defaults to it's ID. As a result,
your second container will share /var/jenkins_home with jenkins master.
Then you can run some commands using $workspace as a valid path in both
containers :

docker run --rm --volumes-from $(hostname) graviteeio/python3 python
${WORKSPACE}/package_bundles.py

2016-05-18 10:34 GMT+02:00 Nicolas Geraud <nicolas.ger...@gmail.com>:

> Thanks for the quick answer, I'll test this tonight.
>
> Do you have any blog post (or perhaps i've missed a "Quoi de neuf Docker"
> episode) which explain why it works like this ?
>
> Le mercredi 18 mai 2016 10:28:05 UTC+2, nicolas de loof a écrit :
>>
>> For this to work, you'll need the host path to be the exact same as the
>> jenkins container path, i.e. not use /opt/jenkins but /var/jenkins_home
>> on host
>> so `pwd` will resolve to some /var/jenkins_home/... subfolder that make
>> sense to be mounted from host into your side container
>>
>> 2016-05-18 10:14 GMT+02:00 Nicolas Geraud <nicolas...@gmail.com>:
>>
>>> Hi all,
>>>
>>> i'm using a dockerized jenkins (from jenkinsci/jenkins:2.2) and mounting
>>> the following volumes from my host :
>>> volumes:
>>> - "/opt/jenkins:/var/jenkins_home"
>>> - "/var/run/docker.sock:/var/run/docker.sock"
>>>
>>>
>>> I've created a job that launch a docker container to build some python
>>> files :
>>> --Dockerfile
>>>
>>> FROM python:3-onbuild
>>> CMD [ "python" ]
>>>
>>>
>>> docker command of my jenkins job :
>>> $docker run --rm -v `pwd`:"/usr/src/myapp" graviteeio/python3 python
>>> src/main/python/package_bundles.py
>>>
>>> But the result is :
>>>
>>>
>>> Starting docker_package_bundle_and_publish_1
>>> Attaching to docker_package_bundle_and_publish_1
>>> [36mpackage_bundle_and_publish_1 | [0m python: can't open file './src/
>>> main/python/package_bundles.py': [Errno 2] No such file or directory
>>> [36mdocker_package_bundle_and_publish_1 exited with code 2
>>> [0mFinished: SUCCESS
>>>
>>>
>>> This is working fine on a classic jenkins, but not on a dockerized jenkins. 
>>> I've googled this error and it seems that mounting a volume inside a 
>>> container with an already mounting volume doesn't work.
>>>
>>> I think that some of you have already test the same use case so, how to do 
>>> that ?
>>>
>>> Thanks for any clue.
>>> I need to test a data volume instead of mounting a host volume.
>>>
>>>
>>> --
>>> 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/f847d41e-3b28-4b2b-b61e-ca0bf2927e5e%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/f847d41e-3b28-4b2b-b61e-ca0bf2927e5e%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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/f8487560-3e1a-44a2-883f-b5ae02213cc1%40googlegroups.com
> <https://groups.google.com/d/msgid/jenkinsci-users/f8487560-3e1a-44a2-883f-b5ae02213cc1%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> 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%3DFuxvJNRxu2z1-KCiNguQ%2Bz0srqeds9Hwsnjbhf4pM-Q%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: How to mount volume in a docker job inside a dockerized jenkins

[nicolas de loof]

For this to work, you'll need the host path to be the exact same as the
jenkins container path, i.e. not use /opt/jenkins but /var/jenkins_home on
host
so `pwd` will resolve to some /var/jenkins_home/... subfolder that make
sense to be mounted from host into your side container

2016-05-18 10:14 GMT+02:00 Nicolas Geraud :

> Hi all,
>
> i'm using a dockerized jenkins (from jenkinsci/jenkins:2.2) and mounting
> the following volumes from my host :
> volumes:
> - "/opt/jenkins:/var/jenkins_home"
> - "/var/run/docker.sock:/var/run/docker.sock"
>
>
> I've created a job that launch a docker container to build some python
> files :
> --Dockerfile
>
> FROM python:3-onbuild
> CMD [ "python" ]
>
>
> docker command of my jenkins job :
> $docker run --rm -v `pwd`:"/usr/src/myapp" graviteeio/python3 python
> src/main/python/package_bundles.py
>
> But the result is :
>
>
> Starting docker_package_bundle_and_publish_1
> Attaching to docker_package_bundle_and_publish_1
> [36mpackage_bundle_and_publish_1 | [0m python: can't open file './src/main
> /python/package_bundles.py': [Errno 2] No such file or directory
> [36mdocker_package_bundle_and_publish_1 exited with code 2
> [0mFinished: SUCCESS
>
>
> This is working fine on a classic jenkins, but not on a dockerized jenkins. 
> I've googled this error and it seems that mounting a volume inside a 
> container with an already mounting volume doesn't work.
>
> I think that some of you have already test the same use case so, how to do 
> that ?
>
> Thanks for any clue.
> I need to test a data volume instead of mounting a host volume.
>
>
> --
> 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/f847d41e-3b28-4b2b-b61e-ca0bf2927e5e%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/CANMVJzmsALEiNxFHqudZ6zsoMHpjW48UGkkR7AMwsBe5%2B%2BUvhA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Amazon ECR Plugin not providing credentials for Docker Build & Push Plugin

[nicolas de loof]

Did you well selected amazon credentials in build and publish build step
configuration ?

2016-04-11 22:53 GMT+02:00 A. Best :

> *Versions used in testing:*
> Jenkins: 1.642.3
> Amazon ECR Plugin: 1.0
> 
> Cloudbees Docker Build & Publish: 1.2.1
> 
>
> *ECS Container Instance*
> Docker Version: 1.9.1
> API Version: 1.21
>
>
> I have a couple of quick question about the amazon-ecr-plugin
> .
>
> In the About
>  
> section
> of the plugin, the Cloudbees Docker Build and Publish
> 
>  is
> referenced as an example of how the ECR plugin can be used.
>
> For my specific use case, I have the Jenkins master connecting to a
> Jenkins JNLP slave running in an ECS cluster. I’m using a container based
> on the jenkinsci/jnlp-slave
>  to perform the build.
> With the right permissions and mounted volumes, I am able to use the docker
> host(which is the ECS container instance) to build docker images.
>
>
> 
>
>
> The *Docker Build and Publish* plugin does use the dockerfile at the root
> of the project and build it as expected. However, I’m running into an issue
> when the plugin attempts to push the image to ECR.
>
> The push refers to a repository 
> [.dkr.ecr.us-east-1.amazonaws.com/ 
> test-repository] (len: 1)7a8e1872c5e2: 
> Preparing
> Post 
> https://.dkr.ecr.us-east-1.amazonaws.com/v2/test-repository/blobs/uploads/
>  : no basic auth 
> credentials
> Build step 'Docker Build and Publish' marked build as failure
> Finished: FAILURE
>
> It seems that the build is attempting to push to the registry with no
> credentials. I was assuming that the ECR plugin would provide docker with
> the correct AWS credentials to login to the registry so that the newly
> built image could be pushed.
>
> Do I need any additional packages installed on the Jenkins slave to get
> this to work?
>
> Am I missing something?
>
> Are my expectations for the plugin wrong?
>
>
> Thanks,
>
> Adam
>
> --
> 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/eaf6f71a-9758-4838-bb05-fd4fa43ee021%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/CANMVJzkbcHPGFmQD%3DWknEaKQf3%2BpM7KLmnk9FPVs0Qy_pNzPSA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build-flow plugin - fetching script from SVN/Git

[nicolas de loof]

You should look at Pipeline plugin, which do support storing build DSL
definition in project SCM (as so called "Jenkinsfile")
DSL syntax is not the same as build-flow, but comparable so as you just
started using it migrating will not be such an issue.

2016-02-11 14:48 GMT+01:00 Tomasz Szandała :

> Greetings,
> I have just started using DSL in my Jenkins.
> I have encountered a problem: how to keep DSL scripts under version
> control?
> I have:
>
> BUt the console log says:
>
> [EnvInject] - Loading node environment variables.
> [EnvInject] - Preparing an environment for the build.
> [EnvInject] - Keeping Jenkins system variables.
> [EnvInject] - Keeping Jenkins build variables.
> [EnvInject] - Executing and processing the following script content:
> svn export --force ${SVN_CREDENTIALS} 
> https://path.to.my.repo/szandala/factory_test 
> 
>  .
> echo "My workspace: ${WORKSPACE}"
> pwd
> [jenkins] $ /bin/sh -xe /var/tmp/hudson192879847093505.sh
> A.
> Afactory.dsl
> Exported revision 2450.
> + echo 'My workspace: '
> My workspace:
> + pwd
> /var/jenkins
> [EnvInject] - Script executed successfully.
> [EnvInject] - Injecting contributions.
> Building on master in workspace 
> /var/jenkins/jobs/szandala.factory_test/workspace
> [build-flow] reading DSL from file 'factory.dsl'
> FATAL: /var/jenkins/jobs/szandala.factory_test/workspace/factory.dsl (No such 
> file or directory)java.io.FileNotFoundException 
> :
>  /var/jenkins/jobs/szandala.factory_test/workspace/factory.dsl (No such file 
> or directory)
>   at java.io.FileInputStream.open(Native Method)
>   at java.io.FileInputStream.(FileInputStream.java:146)
>   at hudson.FilePath.read(FilePath.java:1752)
>   at hudson.FilePath.readToString(FilePath.java:1853)
>   at 
> com.cloudbees.plugins.flow.FlowRun$BuildWithWorkspaceRunnerImpl.doRun(FlowRun.java:177)
>   at 
> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537)
>   at hudson.model.Run.execute(Run.java:1741)
>   at hudson.model.Run.run(Run.java:1679)
>   at com.cloudbees.plugins.flow.FlowRun.run(FlowRun.java:153)
>   at hudson.model.ResourceController.execute(ResourceController.java:98)
>   at hudson.model.Executor.run(Executor.java:408)
> Finished: FAILURE
>
>
> How can I export DSL script from Git / SVN?
>
> --
> 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/95c0553e-f447-4286-856d-c83ccb191205%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%3DyxEF%2Bs9AUhOmhBT53bqi%2BvKRHNFH5M1C5qJrfv9%2BpLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: AWS ECS Plugin

[nicolas de loof]

docker socket is only accessible to users in docker group or to root.
running from a container doesn't bypass such permission check.

2016-02-01 23:55 GMT+01:00 Mulloy Morrow <mulloymor...@gmail.com>:

> Was able to get this working. Mounted the docker socket using the mount
> point configs in the jenkins plugin. However, I was getting a permission
> denied when trying to nc or curl the socket for info. I had to run the
> slaves as user root rather than user jenkins. Has either of you come across
> this issue?
>
>
> On Monday, February 1, 2016 at 10:48:15 AM UTC-8, Mulloy Morrow wrote:
>>
>>
>> Has anyone successfully been able to mount the Docker UNIX socket on the
>> slave containers? I've attempted to mount this socket using the Jenkins ECS
>> plugin (v1.2) by configuring "container mount points".  (see jenkins config
>> screenshot below)
>>
>>
>> <https://lh3.googleusercontent.com/-OMv5j1De_So/Vq-oNwqovqI/AAACzGo/hppFEgNB3bs/s1600/Screen%2BShot%2B2016-02-01%2Bat%2B10.42.52%2BAM.png>
>>
>> On Monday, January 25, 2016 at 7:52:30 AM UTC-8, nicolas de loof wrote:
>>>
>>> Latest development build for ECS plugin do let you define bind mounts,
>>> see https://jenkins.ci.cloudbees.com/job/plugins/job/amazon-ecs-plugin/
>>>
>>> 2016-01-25 16:33 GMT+01:00 Brandon Wagner <bmwag...@gmail.com>:
>>>
>>>> If I'm understanding correctly, I would mount the docker.sock to the
>>>> slave container? I created an image extended from the jenkinsci/jnlp-slave
>>>> that does a wget for the docker CLI.
>>>>
>>>> However, I don't see a place to mount the docker.sock through the ECS
>>>> configuration options.
>>>>
>>>>
>>>> -Brandon Wagner
>>>>
>>>> On Sat, Jan 23, 2016 at 1:08 PM, nicolas de loof <nicolas...@gmail.com>
>>>> wrote:
>>>>
>>>>> You could use docker-custom-build-environment-plugin for this exact
>>>>> scenario, with bind mounted /var/run/docker.sock so you can run containers
>>>>> side by side (vs "in-docker"). Would need some tests on my side to ensure
>>>>> this scenario is supported, I have this on my TOD for a while but never
>>>>> took time to setup a test environment for it...
>>>>>
>>>>> 2016-01-22 21:01 GMT+01:00 Brandon Wagner <bmwag...@gmail.com>:
>>>>>
>>>>>> I would like to run Docker containers for all of my software projects
>>>>>> and dynamically allocate build slaves via ECS (so that I can have a core
>>>>>> cluster that can do builds quickly; in contrast to spinning up an EC2
>>>>>> instance).
>>>>>>
>>>>>>  For example, I have a Java application which is completely contained
>>>>>> in a Docker container (I can build it, run tests, and run the actual
>>>>>> application with Tomcat all within the container). I want to use this 
>>>>>> for a
>>>>>> variety of different purposes (dev, testing, qa, and production). In 
>>>>>> order
>>>>>> to make it reusable like that, I don't want to include Jenkins Slave
>>>>>> packages and expose ports. I'd rather deploy out a Jenkins-Slave 
>>>>>> container
>>>>>> to my ECS cluster, and then have that slave handle running my 
>>>>>> application's
>>>>>> docker container which also performs tests.
>>>>>>
>>>>>> I also support other team applications which are already running
>>>>>> docker container builds in Jenkins (locally on the Jenkins Master). I 
>>>>>> want
>>>>>> it to be transparent to them that I'm "outsourcing" build slaves to ECS. 
>>>>>> It
>>>>>> shouldn't matter to them that I'm changing the way Jenkins is performing
>>>>>> builds.
>>>>>>
>>>>>> Let me know if you (or anyone else) have suggestions based on my
>>>>>> goals.
>>>>>>
>>>>>> -Brandon Wagner
>>>>>>
>>>>>>
>>>>>> On Fri, Jan 22, 2016 at 2:48 PM, nicolas de loof <
>>>>>> nicolas...@gmail.com> wrote:
>>>>>>
>>>>>>> privileged flag has been added to development build (
>>>>>>> https://jenkins.ci.cloudbees.com/job/plugins/job/amazon-ecs-plugin/)
>>

Re: AWS ECS Plugin(JENKINS-31197)

[nicolas de loof]

further experiments demonstrated my fix does not actually fix anything. I
need to look further at NodeProvisioner to understand why it behave so
badly when used in a Onte-time-executor docker container context.

2016-01-28 0:12 GMT+01:00 <yamamurataro1...@yahoo.co.jp>:

> Sure, that would be great.
> Thank you very much!
>
> - Original Message -
> *From:* nicolas de loof <nicolas.del...@gmail.com>
> *To:* "jenkinsci-users@googlegroups.com" <jenkinsci-users@googlegroups.com>
>
> *Date:* 2016/1/27, Wed 15:34
> *Subject:* Re: AWS ECS Plugin(JENKINS-31197)
>
> as you can see on Jira, JENKINS-31197 is still open.
> I have a fix in progress, would you like to give it a try ?
>
> 2016-01-27 2:58 GMT+01:00 <yamamurataro1...@yahoo.co.jp>:
>
> Hi
>
> Has JENKINS-31197 <https://issues.jenkins-ci.org/browse/JENKINS-31197> been
> sloved? I tried the single use slave plugin, but it does not launch new
> container to run the jobs.
> Is there any other workaround?
> We have many jobs need to run at once it is impossible to run job one by
> one.
>
> 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/578918.10993.qm%40web101520.mail.kks.yahoo.co.jp
> <https://groups.google.com/d/msgid/jenkinsci-users/578918.10993.qm%40web101520.mail.kks.yahoo.co.jp?utm_medium=email_source=footer>
> .
> 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/CANMVJzkiWAcsEKJUWWwEXdUCVW%2Bry%3DMYCDRxMR4%3DonPgnNmdyg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzkiWAcsEKJUWWwEXdUCVW%2Bry%3DMYCDRxMR4%3DonPgnNmdyg%40mail.gmail.com?utm_medium=email_source=footer>
> .
> 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/833671.43546.qm%40web101509.mail.kks.yahoo.co.jp
> <https://groups.google.com/d/msgid/jenkinsci-users/833671.43546.qm%40web101509.mail.kks.yahoo.co.jp?utm_medium=email_source=footer>
> .
>
> 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/CANMVJznf4C7SJtFs50F1LworCUCBx05pXRBTDtU15brnK2qtQw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: AWS ECS Plugin(JENKINS-31197)

[nicolas de loof]

as you can see on Jira, JENKINS-31197 is still open.
I have a fix in progress, would you like to give it a try ?

2016-01-27 2:58 GMT+01:00 :

> Hi
>
> Has JENKINS-31197  been
> sloved? I tried the single use slave plugin, but it does not launch new
> container to run the jobs.
> Is there any other workaround?
> We have many jobs need to run at once it is impossible to run job one by
> one.
>
> 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/578918.10993.qm%40web101520.mail.kks.yahoo.co.jp
> 
> .
> 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/CANMVJzkiWAcsEKJUWWwEXdUCVW%2Bry%3DMYCDRxMR4%3DonPgnNmdyg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: AWS ECS Plugin

[nicolas de loof]

Latest development build for ECS plugin do let you define bind mounts, see
https://jenkins.ci.cloudbees.com/job/plugins/job/amazon-ecs-plugin/

2016-01-25 16:33 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:

> If I'm understanding correctly, I would mount the docker.sock to the slave
> container? I created an image extended from the jenkinsci/jnlp-slave that
> does a wget for the docker CLI.
>
> However, I don't see a place to mount the docker.sock through the ECS
> configuration options.
>
>
> -Brandon Wagner
>
> On Sat, Jan 23, 2016 at 1:08 PM, nicolas de loof <nicolas.del...@gmail.com
> > wrote:
>
>> You could use docker-custom-build-environment-plugin for this exact
>> scenario, with bind mounted /var/run/docker.sock so you can run containers
>> side by side (vs "in-docker"). Would need some tests on my side to ensure
>> this scenario is supported, I have this on my TOD for a while but never
>> took time to setup a test environment for it...
>>
>> 2016-01-22 21:01 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:
>>
>>> I would like to run Docker containers for all of my software projects
>>> and dynamically allocate build slaves via ECS (so that I can have a core
>>> cluster that can do builds quickly; in contrast to spinning up an EC2
>>> instance).
>>>
>>>  For example, I have a Java application which is completely contained in
>>> a Docker container (I can build it, run tests, and run the actual
>>> application with Tomcat all within the container). I want to use this for a
>>> variety of different purposes (dev, testing, qa, and production). In order
>>> to make it reusable like that, I don't want to include Jenkins Slave
>>> packages and expose ports. I'd rather deploy out a Jenkins-Slave container
>>> to my ECS cluster, and then have that slave handle running my application's
>>> docker container which also performs tests.
>>>
>>> I also support other team applications which are already running docker
>>> container builds in Jenkins (locally on the Jenkins Master). I want it to
>>> be transparent to them that I'm "outsourcing" build slaves to ECS. It
>>> shouldn't matter to them that I'm changing the way Jenkins is performing
>>> builds.
>>>
>>> Let me know if you (or anyone else) have suggestions based on my goals.
>>>
>>> -Brandon Wagner
>>>
>>>
>>> On Fri, Jan 22, 2016 at 2:48 PM, nicolas de loof <
>>> nicolas.del...@gmail.com> wrote:
>>>
>>>> privileged flag has been added to development build (
>>>> https://jenkins.ci.cloudbees.com/job/plugins/job/amazon-ecs-plugin/)
>>>> anyway, DinD is probably not a good idea (there's really few docker
>>>> usages to actually require it). What's your actual need ?
>>>>
>>>> 2016-01-22 20:46 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:
>>>>
>>>>> So I ended up figuring my issue out. I think there were a couple of
>>>>> issues. My JNLP port was set to 50,000 instead of 5,000 which the Jenkins
>>>>> Docker Container I was using was mapping to the host port 5000. And my 
>>>>> Load
>>>>> Balancer in front of Jenkins was not forwarding port 5000 to the host 
>>>>> (only
>>>>> 443). Anyways, all of that is fixed and I can now run builds on slaves in
>>>>> ECS.
>>>>>
>>>>> My next problem: I want to use docker-in-docker to run docker builds
>>>>> on my docker jenkins slaves. I'm trying to use
>>>>> https://github.com/tehranian/dind-jenkins-slave which looks good, but
>>>>> I don't see an option on the Jenkins ECS plugin to run the slave as
>>>>> privileged which is necessary for docker-in-docker.
>>>>>
>>>>>
>>>>> -Brandon Wagner
>>>>>
>>>>> On Fri, Jan 22, 2016 at 7:11 AM, nicolas de loof <
>>>>> nicolas.del...@gmail.com> wrote:
>>>>>
>>>>>> First look into jenkins logs.
>>>>>> Also check on ECS a task definition has been created for
>>>>>> jenkins-slaves.
>>>>>> Also double check ECS nodes can ping your jenkins master URL.
>>>>>>
>>>>>> 2016-01-21 22:13 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:
>>>>>>
>>>>>>> I'm trying to use the Jenkins AWS EC2 Container Service (ECS) plugin
>>>>>>> to dep

Re: AWS ECS Plugin

[nicolas de loof]

You could use docker-custom-build-environment-plugin for this exact
scenario, with bind mounted /var/run/docker.sock so you can run containers
side by side (vs "in-docker"). Would need some tests on my side to ensure
this scenario is supported, I have this on my TOD for a while but never
took time to setup a test environment for it...

2016-01-22 21:01 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:

> I would like to run Docker containers for all of my software projects and
> dynamically allocate build slaves via ECS (so that I can have a core
> cluster that can do builds quickly; in contrast to spinning up an EC2
> instance).
>
>  For example, I have a Java application which is completely contained in a
> Docker container (I can build it, run tests, and run the actual application
> with Tomcat all within the container). I want to use this for a variety of
> different purposes (dev, testing, qa, and production). In order to make it
> reusable like that, I don't want to include Jenkins Slave packages and
> expose ports. I'd rather deploy out a Jenkins-Slave container to my ECS
> cluster, and then have that slave handle running my application's docker
> container which also performs tests.
>
> I also support other team applications which are already running docker
> container builds in Jenkins (locally on the Jenkins Master). I want it to
> be transparent to them that I'm "outsourcing" build slaves to ECS. It
> shouldn't matter to them that I'm changing the way Jenkins is performing
> builds.
>
> Let me know if you (or anyone else) have suggestions based on my goals.
>
> -Brandon Wagner
>
>
> On Fri, Jan 22, 2016 at 2:48 PM, nicolas de loof <nicolas.del...@gmail.com
> > wrote:
>
>> privileged flag has been added to development build (
>> https://jenkins.ci.cloudbees.com/job/plugins/job/amazon-ecs-plugin/)
>> anyway, DinD is probably not a good idea (there's really few docker
>> usages to actually require it). What's your actual need ?
>>
>> 2016-01-22 20:46 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:
>>
>>> So I ended up figuring my issue out. I think there were a couple of
>>> issues. My JNLP port was set to 50,000 instead of 5,000 which the Jenkins
>>> Docker Container I was using was mapping to the host port 5000. And my Load
>>> Balancer in front of Jenkins was not forwarding port 5000 to the host (only
>>> 443). Anyways, all of that is fixed and I can now run builds on slaves in
>>> ECS.
>>>
>>> My next problem: I want to use docker-in-docker to run docker builds on
>>> my docker jenkins slaves. I'm trying to use
>>> https://github.com/tehranian/dind-jenkins-slave which looks good, but I
>>> don't see an option on the Jenkins ECS plugin to run the slave as
>>> privileged which is necessary for docker-in-docker.
>>>
>>>
>>> -Brandon Wagner
>>>
>>> On Fri, Jan 22, 2016 at 7:11 AM, nicolas de loof <
>>> nicolas.del...@gmail.com> wrote:
>>>
>>>> First look into jenkins logs.
>>>> Also check on ECS a task definition has been created for
>>>> jenkins-slaves.
>>>> Also double check ECS nodes can ping your jenkins master URL.
>>>>
>>>> 2016-01-21 22:13 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:
>>>>
>>>>> I'm trying to use the Jenkins AWS EC2 Container Service (ECS) plugin
>>>>> to deploy Jenkins Slave Containers for builds. I have an ECS cluster 
>>>>> setup,
>>>>> and I have it configured in my Jenkins Configuration. Everything appears 
>>>>> to
>>>>> be good until I try to build a job, restricting to the ecs cloud label I
>>>>> setup, and it just comes back with "(pending—
>>>>> Jenkins-Container-Cloud-456...164
>>>>> <https://jenkins.itsec.aolcloud.net/computer/Jenkins-Container-Cloud-456b6d1601164>is
>>>>> offline)" .
>>>>>
>>>>> Does anyone know how to fix this, or have suggestions on debugging
>>>>> 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/f9bf24d9-a9e3-46f6-8fba-041b3344bdc7%40googlegroups.c

Re: AWS ECS Plugin

[nicolas de loof]

privileged flag has been added to development build (
https://jenkins.ci.cloudbees.com/job/plugins/job/amazon-ecs-plugin/)
anyway, DinD is probably not a good idea (there's really few docker usages
to actually require it). What's your actual need ?

2016-01-22 20:46 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:

> So I ended up figuring my issue out. I think there were a couple of
> issues. My JNLP port was set to 50,000 instead of 5,000 which the Jenkins
> Docker Container I was using was mapping to the host port 5000. And my Load
> Balancer in front of Jenkins was not forwarding port 5000 to the host (only
> 443). Anyways, all of that is fixed and I can now run builds on slaves in
> ECS.
>
> My next problem: I want to use docker-in-docker to run docker builds on my
> docker jenkins slaves. I'm trying to use
> https://github.com/tehranian/dind-jenkins-slave which looks good, but I
> don't see an option on the Jenkins ECS plugin to run the slave as
> privileged which is necessary for docker-in-docker.
>
>
> -Brandon Wagner
>
> On Fri, Jan 22, 2016 at 7:11 AM, nicolas de loof <nicolas.del...@gmail.com
> > wrote:
>
>> First look into jenkins logs.
>> Also check on ECS a task definition has been created for jenkins-slaves.
>> Also double check ECS nodes can ping your jenkins master URL.
>>
>> 2016-01-21 22:13 GMT+01:00 Brandon Wagner <bmwagne...@gmail.com>:
>>
>>> I'm trying to use the Jenkins AWS EC2 Container Service (ECS) plugin to
>>> deploy Jenkins Slave Containers for builds. I have an ECS cluster setup,
>>> and I have it configured in my Jenkins Configuration. Everything appears to
>>> be good until I try to build a job, restricting to the ecs cloud label I
>>> setup, and it just comes back with "(pending—
>>> Jenkins-Container-Cloud-456...164
>>> <https://jenkins.itsec.aolcloud.net/computer/Jenkins-Container-Cloud-456b6d1601164>is
>>> offline)" .
>>>
>>> Does anyone know how to fix this, or have suggestions on debugging
>>> 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/f9bf24d9-a9e3-46f6-8fba-041b3344bdc7%40googlegroups.com
>>> <https://groups.google.com/d/msgid/jenkinsci-users/f9bf24d9-a9e3-46f6-8fba-041b3344bdc7%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>> 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/kSBWy3gBQbg/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/CANMVJzks3yceTvUxrFd5cGo8tYwSFh%3D00V%3DzL%2BxJVB2kCmi%3DhQ%40mail.gmail.com
>> <https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzks3yceTvUxrFd5cGo8tYwSFh%3D00V%3DzL%2BxJVB2kCmi%3DhQ%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>>
>> 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/CAKgdMg-%2Bs99MCNpwJz99QBs0NTke7EV2Tt%3DWPEj5NZBzjkJaHg%40mail.gmail.com
> <https://groups.google.com/d/msgid/jenkinsci-users/CAKgdMg-%2Bs99MCNpwJz99QBs0NTke7EV2Tt%3DWPEj5NZBzjkJaHg%40mail.gmail.com?utm_medium=email_source=footer>
> .
>
> 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/CANMVJzmdKoB9PZfYNcA6tGMyC2pT5Mg13LP9UMMW%2Bt3FAC1qTA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: AWS ECS Plugin

[nicolas de loof]

First look into jenkins logs.
Also check on ECS a task definition has been created for jenkins-slaves.
Also double check ECS nodes can ping your jenkins master URL.

2016-01-21 22:13 GMT+01:00 Brandon Wagner :

> I'm trying to use the Jenkins AWS EC2 Container Service (ECS) plugin to
> deploy Jenkins Slave Containers for builds. I have an ECS cluster setup,
> and I have it configured in my Jenkins Configuration. Everything appears to
> be good until I try to build a job, restricting to the ecs cloud label I
> setup, and it just comes back with "(pending—
> Jenkins-Container-Cloud-456...164
> is
> offline)" .
>
> Does anyone know how to fix this, or have suggestions on debugging 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/f9bf24d9-a9e3-46f6-8fba-041b3344bdc7%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/CANMVJzks3yceTvUxrFd5cGo8tYwSFh%3D00V%3DzL%2BxJVB2kCmi%3DhQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: "CloudBees Folders Plugin" ... current 2015 thoughts?

[nicolas de loof]

Most plugins have been fixed to support folders, few remain incompatible
I'm not sure there's an up-to-date list of incompatible plugins

2015-12-10 13:59 GMT+01:00 Martin Ba <0xcdcdc...@gmx.at>:

> Hi all!
>
> I was considering taking a look at the free Folders Plugin from Cloudbees,
> but reading a piece back from 2013 I'm a bit scared:
>
> full meassage see:
> https://groups.google.com/forum/#!msg/jenkinsci-users/VcxGHiFvBAY/mDwr_hL-7JsJ
>
> On 28.10.2013 22:55, Daniel Beck wrote to
> jenkinsci-users@googlegroups.com:
> > I started using folders around seven months ago. The following is
> > based on the advantages I experience in using folders, as well as the
> > problems I've encountered. It's not a high level overview. Some of
> > this will probably already be obsolete, but it should still serve...
> > ...
> > That being said, the introduction of folders really wasn't a lot of
> > fun. Some of it is my fault for assuming things would just work to a
> > reasonable degree. I was wrong. Plugins often cannot handle folders!
> > Some have assumptions that break down when using folders, e.g. that
> > all items are immediate children of Jenkins, or that no two jobs have
> > the same name.
> > ...
>
> Is it still true with current Jenkins releases that Folders make trouble
> with many/some/a few plugins? (I'm on 1.625.2 LTS + potentially Folders 5.1
> (Nov/2015).
>
> Thanks,
> Martin
>
> --
> 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/56697733.40405%40gmx.at.
> 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/CANMVJznsK-hxsaqGWKFMh-vJ3TszuckhK1r%3DpbzY7GWyF%2B5vqw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Regarding docker : JENKINS-30113

[nicolas de loof]

Hi,

cloudbees docker custom build environment 1.6.x branch is focussing on evn
issues, especially considering
- we don't want docker host slave env to pollute the container one
- we want env defined by Docker image / Dockerfile to be available for the
build
- we want buildwrappers to be able to inject new env, and extend PATH

1.6.1 you're using is obsolete from this point of view, please try 1.6.4

2015-11-02 6:14 GMT+01:00 Irfan Sayed :

> Thanks Jason.
> OK. let me in detail out all steps which i carried out.
> Created Dockerfile (PFA).
> Created Jenkins Job which will is connected to one UNIX box (using ssh
> port : 22) on which docker daemon is running
>
> as a part of Jenkins job configuration, i choose the option "Build inside
> a Docker container"
> when i started the build , job builds the Dockerfile and image gets
> created successfully.  further, job runs that image in container and now
> that image is ready for use.
> After that, when i am simply running command "java -version" as a part of
> build step and that step is failing because it is not finding that version
> of java which i set as a part of dockerfile.
>
> As per your  comment (if i understand correctly), i am not starting
> container, job itself builds the image from Dockerfile and start the
> container. further, i don't know how to ssh to running container from the
> Jenkins job itself. is there already option in Jenkins job ?
> I have seen option "Start/Stop container " as a build step .. but not
> getting feel of how to use it
>
> Please suggest
>
> Regards
>
>
>
>
>
> On Sun, Nov 1, 2015 at 10:37 PM, Jason Swager  wrote:
>
>> If you're using the Docker plugin (
>> https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin), I found the
>> env vars worked fine when they were setup to be available to incoming .ssh
>> connections.  That sometimes meant using a different config file within the
>> container to prep the variables.
>>
>> A good way to test - don't start the container and use as if directly
>> signed in.  Instead, start the container and SSH into it.  If the vars were
>> missing then, correct the container config until they worked properly.
>> Then they should start working properly as a Jenkins slave too.
>>
>> On Sunday, November 1, 2015 at 8:06:21 AM UTC-8, Irfan Sayed wrote:
>>>
>>> further update:
>>> after lot of digging, i found that whatever environment variables set in
>>> Dockerfile (actually in image created using this dockerfile) are not
>>> available in build section using docker plugin .
>>>
>>> but in reality , we need these variables to be available in the build
>>> section.
>>> In typical use case, lets say i am installing oracle JDK 8, and in the
>>> base image in dockerfile, already openjdk is installed.
>>> in order to use the oracle jdk, will set the environment variable and
>>> set the default jdk to oracle 8
>>> I did that in Dockerfile and i am able to access java version manually
>>> if i try to build the image and run in container
>>>
>>> however, if the same dockerfile built using docker plugin , then those
>>> env variables are not available in build section
>>> is it by design ??
>>>
>>> is there any way where we can allow these variables to be available in
>>> build section ???
>>>
>>> Regards
>>>
>>>
>>> On Sun, Nov 1, 2015 at 3:10 AM, Irfan Sayed  wrote:
>>>
 Hello,

 I tried using docker plugin. I have choose the option : Pull docker
 image from repository
 I have built the entire image and pushed it to private docker registry.
 Using Jenkins job and i am able to pull the image.

 now my assumption is , whatever setting i have done while creating the
 image should be available / intact when i am pulling image from docker
 registry
 but , in reality , it is not happening .
 I have configured maven while creating image but now when i am pulling
 image from registry, jenkins is not able to find mvn command line
 now, i am not getting what is missing

 Manually, if i try to run that image in container, then i am getting
 mvn command line

 please help

 Regards


 On Sat, Oct 31, 2015 at 6:41 AM, Pradeep Kumar Mantha <
 prade...@gmail.com> wrote:

> Even I see the same problem as Irfan, Here we are not expecting
> environment variables from Jenkins.
> We expect whatever the variables/path set in docker file to be
> available to the build script. But currently the variables are being
> overwritten with the jenkins build environment variables, which seems to 
> be
> incorrect.
>
>
> On Tuesday, October 27, 2015 at 11:25:51 PM UTC-7, Irfan Sayed wrote:
>
>> Hi All,
>>
>> I am using cloudbeese custom build environment plugin to create the
>> build environment based on docket container
>> I have created dockerfile and spawning image using container.
>> In the docker 

Re: docker connectivity issue

[nicolas de loof]

Can you run docker commands without setting -H ?
In this case docker will use /var/run/docker.sock unix socket and not rely
on TLS for security, which is the default behavior for access to local
daemon.
docker plugins will work the same in such a setup, and you don't have to
set a docker host in your jenkins configuration but just let plugin access
local daemon.

2015-10-18 20:30 GMT+02:00 Irfan Sayed :

> further update :
>
> here is the docker process and running and it's PID
>
> [root@localhost docker]# ps -ef | grep docker
> root  1623 1  0 12:11 ?00:00:28 /usr/bin/docker -d
> --selinux-enabled
> root  3480  3415  0 12:54 ?00:00:00 bash -c cd
> "/tmp/workspace/docker" && java  -jar slave.jar
> root 12299 11158  0 23:00 pts/200:00:00 grep --color=auto docker
>
> further, if i run following command:
>
> [root@localhost docker]# docker -H=tcp://192.168.102.28:22 images
> Get http://192.168.102.28:22/v1.19/images/json: malformed HTTP response
> "SSH-2.0-OpenSSH_6.4". Are you trying to connect to a TLS-enabled daemon
> without TLS?
>
> regards
>
>
>
>
> On Sun, Oct 18, 2015 at 11:39 PM, Irfan Sayed 
> wrote:
>
>> i have just ssh (using port 22) to connect to docker host which is
>> nothing but slave box
>> this is what i have done.
>>
>> i haven't specified any docker URL. In job configuration, i have just
>> given the path of Dockerfile and trying to build the image from that
>> Dockerfile
>>
>> please suggest
>>
>> Regards
>>
>>
>> On Sun, Oct 18, 2015 at 11:31 PM, Richard Bywater 
>> wrote:
>>
>>> Have you specified the port 22 from that Docker URL or are the plug-ins
>>> doing that as port 22 isn't  right for Docker.
>>>
>>> Richard
>>>
>>> On Sun, 18 Oct 2015 11:22 pm Irfan Sayed  wrote:
>>>

 hi all,

 I am trying to provision the build containers dynamically using docker
 . i have installed jenkins master along with docker plugins . build slave
 is docker host and all are running on unix setup : centos : 6.5

 here is my setup:

 Jenkins master : 1.633
 cloudbees docker build and publish plugin : 1.0.1
 cloudbees docker custom build env plugin : 1.6.1
 docker commons plugin : 1.2
 docker build step : 1.31
 kubernetes plugin : 0.4.1

 I have deployed the docker host and created Dockerfile. i am able to
 build docker image using Dockerfile on the docker host and run in the
 container
 however, from jenkins master , whenever i am trying to connect to
 docker host and build docker image using docker plugin , i am getting
 following error

 Started by user anonymous 
 Building remotely on 192.168.102.28 
  in workspace 
 /tmp/workspace/docker
 $ docker inspect 43728998fde0187a1f0b526fef5e2db9b02796a3
 []
 Build Docker image from /tmp/workspace/docker/Dockerfile ...
 $ docker build --tag 43728998fde0187a1f0b526fef5e2db9b02796a3 --file 
 Dockerfile /tmp/workspace/docker
 Sending build context to Docker daemon 497.2 kB

 Sending build context to Docker daemon
 Post 
 http://192.168.102.28:22/v1.19/build?cgroupparent==0=0===0=Dockerfile=0=0=1=43728998fde0187a1f0b526fef5e2db9b02796a3:
  malformed HTTP response "SSH-2.0-OpenSSH_6.4". Are you trying to connect 
 to a TLS-enabled daemon without TLS?
 FATAL: Failed to build docker image from project 
 Dockerfilejava.lang.RuntimeException 
 :
  Failed to build docker image from project Dockerfile
at 
 com.cloudbees.jenkins.plugins.docker_build_env.Docker.buildImage(Docker.java:121)
  
 
at 
 com.cloudbees.jenkins.plugins.docker_build_env.DockerfileImageSelector.prepareDockerImage(DockerfileImageSelector.java:41)
  
 
at 
 com.cloudbees.jenkins.plugins.docker_build_env.DockerBuildWrapper.setUp(DockerBuildWrapper.java:152)
  
 
at hudson.model.Build$BuildExecution.doRun(Build.java:156) 
 
at 
 hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:537)
  
 
at hudson.model.Run.execute(Run.java:1741) 
 

Re: Jenkins Docker Slaves

[nicolas de loof]

Just an update to let you know I release 1.0-beta-3, and the community vote
<https://t.co/VPvTxDBVjL> ends on Monday 9am PDT

Have a nice week-end

2015-09-22 17:29 GMT+02:00 nicolas de loof <nicolas.del...@gmail.com>:

> Hi folks
>
> during Docker Hack Day, Yoann and I did prototyped a new jenkins plugin, 
> Docker
> slaves plugin <https://github.com/ndeloof/docker-slaves-plugin>
>
> This plugin uses a docker host (or docker swarm cluster) to host build,
> only relying on containers, without any constraint (no sshd, no specific
> user to define), and can also run side containers to host test resources
> (database, webserver, selenium browser, ...).
>
> Yoann recorded a demo <https://www.youtube.com/watch?v=HbwgN0UTTxo> and I
> published a technical explanation
> <http://blog.loof.fr/2015/09/introducing-docker-slaves-jenkins-plugin.html>
> (hope you'll like our accent)
>
> 1.0-beta-1 release is available on experimental update center if you want
> to give it a try.
>
> From a technical point of view, we had to hack / abuse few jenkins APIs,
> maybe this exploratory plugin will help to improve them and help jenkins to
> embrace container paradigm.
>
>
> *Last but not least*, as this plugin is proposed for Docker Hack Day,
>
> *we need you to vote for this project *
>
> on https://www.docker.com/community/hackathon
> - search for "Jenkins Docker Slaves" and vote on tweeter and/or linkedin
> and/or Google+
>
> Would be great a jenkins plugin win the docker hack day, don't you think
> so ?
>
> Cheers,
> Nicolas
>
>

-- 
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%3DaCw-eAdv8e3TSou-u3HxScET9DN3eezExEW12pAoERQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: GIT Time out

[nicolas de loof]

You also should check what makes your git clone operation so long.
Not a good idea to have a huge git repository, time for cleanup ?

2015-09-07 13:08 GMT+02:00 :

> HI
>
> Found the solution
>
> last answer
>
>
> http://stackoverflow.com/questions/19954727/jenkins-time-out-while-fetching-from-github-in-10-mins
>
>
> On Monday, September 7, 2015 at 4:03:24 PM UTC+5:30, thil...@wso2.com
> wrote:
>>
>> hi
>>
>> when i try to build a source code in git i got the following error
>>
>> what am i doing wrong?
>>
>>  > git --version # timeout=10
>>  > git -c core.askpass=true fetch --tags --progress 
>> https://github.com/wso2/carbon-identity +refs/heads/*:refs/remotes/origin/*
>> ERROR: Timeout after 10 minutesERROR 
>> : Error fetching remote 
>> repo 'origin'hudson.plugins.git.GitException 
>> :
>>  Failed to fetch from https://github.com/wso2/carbon-identity
>>  at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:763) 
>> 
>>  at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1012) 
>> 
>>  at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1043) 
>> 
>>  at hudson.scm.SCM.checkout(SCM.java:485) 
>> 
>>  at hudson.model.AbstractProject.checkout(AbstractProject.java:1277) 
>> 
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:610)
>>  
>> 
>>  at 
>> jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) 
>> 
>>  at 
>> hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:532)
>>  
>> 
>>  at hudson.model.Run.execute(Run.java:1741) 
>> 
>>  at hudson.maven.MavenModuleSetBuild.run(MavenModuleSetBuild.java:529) 
>> 
>>  at hudson.model.ResourceController.execute(ResourceController.java:98) 
>> 
>>  at hudson.model.Executor.run(Executor.java:381) 
>> 
>> Caused by: hudson.plugins.git.GitException 
>> :
>>  Command "git -c core.askpass=true fetch --tags --progress 
>> https://github.com/wso2/carbon-identity +refs/heads/*:refs/remotes/origin/*" 
>> returned status code 128:
>> stdout:
>> stderr: remote: Counting objects: 83829, done. [K
>> remote: Compressing objects:   4% (1/22)[K
>> remote: Compressing objects:   9% (2/22)[K
>> remote: Compressing objects:  13% (3/22)[K
>> remote: Compressing objects:  18% (4/22)[K
>> remote: Compressing objects:  22% (5/22)[K
>> remote: Compressing objects:  27% (6/22)[K
>> remote: Compressing objects:  31% (7/22)[K
>>
>> ...
>>
>>
>> Receiving objects:   9% (7565/83829), 17.04 MiB | 164.00 KiB/s
>> Receiving objects:   9% (7568/83829), 17.18 MiB | 185.00 KiB/s
>> Receiving objects:   9% (7571/83829), 17.60 MiB | 247.00 KiB/s
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:1600)
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:1363)
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$300(CliGitAPIImpl.java:61)
>>  at 
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:299)
>>  at hudson.plugins.git.GitSCM.fetchFrom(GitSCM.java:761)
>>  ... 11 more
>> ERROR: nullFinished 
>> : FAILURE
>>
>>
>>
>> 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
> 

Re: 1.625

[nicolas de loof]

I was also confused as I tried to update the weekly docker image

jenkins-ci.org indeed claim latest is 1.625 but download site isn't
up-to-date - I guess we are waiting for some infra cron to rebuild it (tag
was pushed  24 hours ago)


2015-08-19 9:36 GMT+02:00 jenk...@transdata.net:

 I see 1.625 on http://jenkins-ci.org/changelog but can't find it here
 http://mirrors.jenkins-ci.org/war/1.625/jenkins.war
 And http://mirrors.jenkins-ci.org/war/latest/jenkins.war seems to be 1.624

 Anyone else?

 --
 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/00016CD8.55D44E05%40mail.transdata.net
 https://groups.google.com/d/msgid/jenkinsci-users/00016CD8.55D44E05%40mail.transdata.net?utm_medium=emailutm_source=footer
 .
 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/CANMVJznCqbR1SJ%2BydB5jY0akwFXXi-qh_pvn2qwdi-uvSDyoRg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: jenkins on gradle project

[nicolas de loof]

you also can just run a shell script build step to execute gradle wrapper
on your project

2015-08-10 9:56 GMT+02:00 mr m...@protel.net:

 I recommend this https://wiki.jenkins-ci.org/display/JENKINS/Gradle+Plugin


 Am Samstag, 8. August 2015 19:14:36 UTC+2 schrieb nav indian:

 Hi

 I wish to run a gradle based project from my local machine in jenkins.
 any example.

 Thanks
 nav

 --
 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/2682d4af-89aa-462f-b786-690530e5af7e%40googlegroups.com
 https://groups.google.com/d/msgid/jenkinsci-users/2682d4af-89aa-462f-b786-690530e5af7e%40googlegroups.com?utm_medium=emailutm_source=footer
 .

 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-J1D8fdwer7PDyDA-Hc%3DA4vRfPSrESqVRgA_wR_47dQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Re: Build Pipeline plugin and Build Flow plugin

[nicolas de loof]

build graph view do rely on upstreamCause so should handle most relations
between builds
and for the others (including build-flow) do offer an extension point to
discover other relations

2015-07-21 16:44 GMT+02:00 Christoph Kutzinski ku...@gmx.de:

 Thanks!
 I didn't know about
 https://wiki.jenkins-ci.org/display/JENKINS/Build+Graph+View+Plugin

 Can I also define manual triggered steps in a setup of the Build-Flow
 plugin and the build-graphview-plugin like you can do with the build
 pipeline plugin?

 *Gesendet:* Dienstag, 21. Juli 2015 um 14:37 Uhr
 *Von:* nicolas de loof nicolas.del...@gmail.com
 *An:* jenkinsci-users@googlegroups.com jenkinsci-users@googlegroups.com
 
 *Betreff:* Re: Build Pipeline plugin and Build Flow plugin
  build flow did introduce buildgraphview-plugin for this exact use case

 build pipeline only can rendre static and mostly sequential pipelines

 2015-07-21 16:19 GMT+02:00 Christoph Kutzinski ku...@gmx.de:

  Hi,

 I'm trying to set up a CD pipeline with Jenkins where I can

 I) concisely define the relationship (triggers) between the single
 pipeline steps (jobs)
 II) have a nice visualisation of the full pipeline

 The Build Flow plugin is a good fit for I, while the Build Pipeline
 plugin is a nice fit for II.
 However, the Build Pipeline plugin doesn't seem to understand the job
 dependencies defined via the Build Flow plugin.

 Does someone have experiences with similar setups? What is your solution
 for this?


 cheers
 Christoph



 --
 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/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41
 https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41?utm_medium=emailutm_source=footer
 .
 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/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com
 https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 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/trinity-1f3325af-2b1f-4711-80f9-8c1fa13f09ca-1437489871880%403capp-gmx-bs41
 https://groups.google.com/d/msgid/jenkinsci-users/trinity-1f3325af-2b1f-4711-80f9-8c1fa13f09ca-1437489871880%403capp-gmx-bs41?utm_medium=emailutm_source=footer
 .

 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/CANMVJzm6OBmC7pgunTgTjFX8qmdjAjQWxwaw-QHpsNbyoPRX4A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Re: Re: Build Pipeline plugin and Build Flow plugin

[nicolas de loof]

yes, by intention, as the real world CD scenario I've considered aren't
static and can involve various steps depending on runtime context

start a new pipeline is just about re-trigger the initial step (which I
expect to be a git push)
re-run a build could make sense, but then you can just enable retry plugin
on the adequate jobs
manual steps aren't considered by build flow plugin (but fully supported by
workflow)


2015-07-21 17:02 GMT+02:00 Christoph Kutzinski ku...@gmx.de:

 Am I right when saying the the buildgraphview-plugin is a king of 'after
 the fact' view of a pipeline run?
 *I.e. I can see the results of a pipeline afterwards, but I can not
 actively control a pipeline (lie in the Build Pipeline pluing):*
 *- starting a new pipeline run*
 *- re-running a build*
 *- triggering manul steps*

 *Gesendet:* Dienstag, 21. Juli 2015 um 14:45 Uhr
 *Von:* nicolas de loof nicolas.del...@gmail.com
 *An:* jenkinsci-users@googlegroups.com jenkinsci-users@googlegroups.com
 
 *Betreff:* Re: Re: Build Pipeline plugin and Build Flow plugin
  build graph view do rely on upstreamCause so should handle most
 relations between builds
 and for the others (including build-flow) do offer an extension point to
 discover other relations

 2015-07-21 16:44 GMT+02:00 Christoph Kutzinski ku...@gmx.de:

   Thanks!
 I didn't know about
 https://wiki.jenkins-ci.org/display/JENKINS/Build+Graph+View+Plugin

 Can I also define manual triggered steps in a setup of the Build-Flow
 plugin and the build-graphview-plugin like you can do with the build
 pipeline plugin?

 *Gesendet:* Dienstag, 21. Juli 2015 um 14:37 Uhr
 *Von:* nicolas de loof nicolas.del...@gmail.com
 *An:* jenkinsci-users@googlegroups.com 
 jenkinsci-users@googlegroups.com

 *Betreff:* Re: Build Pipeline plugin and Build Flow plugin
  build flow did introduce buildgraphview-plugin for this exact use case

  build pipeline only can rendre static and mostly sequential pipelines

 2015-07-21 16:19 GMT+02:00 Christoph Kutzinski ku...@gmx.de:

  Hi,

 I'm trying to set up a CD pipeline with Jenkins where I can

 I) concisely define the relationship (triggers) between the single
 pipeline steps (jobs)
 II) have a nice visualisation of the full pipeline

 The Build Flow plugin is a good fit for I, while the Build Pipeline
 plugin is a nice fit for II.
 However, the Build Pipeline plugin doesn't seem to understand the job
 dependencies defined via the Build Flow plugin.

 Does someone have experiences with similar setups? What is your solution
 for this?


 cheers
 Christoph



 --
 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/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41
 https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41?utm_medium=emailutm_source=footer
 .
 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/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com
 https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 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/trinity-1f3325af-2b1f-4711-80f9-8c1fa13f09ca-1437489871880%403capp-gmx-bs41
 https://groups.google.com/d/msgid/jenkinsci-users/trinity-1f3325af-2b1f-4711-80f9-8c1fa13f09ca-1437489871880%403capp-gmx-bs41?utm_medium=emailutm_source=footer.


 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/CANMVJzm6OBmC7pgunTgTjFX8qmdjAjQWxwaw-QHpsNbyoPRX4A%40mail.gmail.com
 https://groups.google.com/d/msgid/jenkinsci-users/CANMVJzm6OBmC7pgunTgTjFX8qmdjAjQWxwaw-QHpsNbyoPRX4A%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 For more

Re: Can't figure out how Jenkins GIT Plugin works

[nicolas de loof]

multi-branch support in git-plugin is a poor implementation, and running
the job manually will just rebuild the last commit (so only one branch from
your 3 ones) not all of them, not even considering build history is
irrelevant with branches mixed

If you want actual multi-branch support select a job type which do support
scm-api, for sample
https://wiki.jenkins-ci.org/display/JENKINS/Multi-Branch+Project+Plugin

I'd like we deprecate this is git plugin (which would remove 75% of its
most unmaintainable code) but this would have HUGE impact on user base



2015-07-21 9:15 GMT+02:00 ozcaaa...@gmail.com:

 Hi everyone,

 I have a project on Github which has 3 branches: master, test2, test3 -
 https://github.com/ozcanovunc/jenkins-test/blob/master/test.py. And I'm
 running test.py file in batch command by python test.py command.

- test2 branch : code with error in test.py
- test3 branch : code with error in test.py
- master branch : ok code in test.py

 So when I modify test.py in each branch and build the project I get 3
 builds with 1 success and 2 failures which is fine. But afterwards, when I
 build the project on Jenkins again (with no modifications on codes), I get
 1 build and that is test3 build with failure.

 So is that a bug or something? Where are the 2 other builds? Master and
 test2?


 (And one more thing. I think it's the pretty much the same problem. When I
 modify only test.py in master, then build the project, I get one build with
 success. It doesn't build other branches.)

 Regards,
 Ozcan

 --
 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/9af1cea7-198a-40dc-98e3-71bc372e945d%40googlegroups.com
 https://groups.google.com/d/msgid/jenkinsci-users/9af1cea7-198a-40dc-98e3-71bc372e945d%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 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%3DegK2ikMdh3HwDV9ibdX86sybvO0ntiQ1e%3DW4NqsGhwA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build Pipeline plugin and Build Flow plugin

[nicolas de loof]

Did you considered using workflow plugin ?

2015-07-21 16:37 GMT+02:00 nicolas de loof nicolas.del...@gmail.com:

 build flow did introduce buildgraphview-plugin for this exact use case

 build pipeline only can rendre static and mostly sequential pipelines

 2015-07-21 16:19 GMT+02:00 Christoph Kutzinski ku...@gmx.de:

 Hi,

 I'm trying to set up a CD pipeline with Jenkins where I can

 I) concisely define the relationship (triggers) between the single
 pipeline steps (jobs)
 II) have a nice visualisation of the full pipeline

 The Build Flow plugin is a good fit for I, while the Build Pipeline
 plugin is a nice fit for II.
 However, the Build Pipeline plugin doesn't seem to understand the job
 dependencies defined via the Build Flow plugin.

 Does someone have experiences with similar setups? What is your solution
 for this?


 cheers
 Christoph


 --
 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/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41
 https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41?utm_medium=emailutm_source=footer
 .
 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%3DrnO8MxedwwrWBecgE%3Dz-vJVkAfgy%3DKZ04s8uqCBoAw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Build Pipeline plugin and Build Flow plugin

[nicolas de loof]

build flow did introduce buildgraphview-plugin for this exact use case

build pipeline only can rendre static and mostly sequential pipelines

2015-07-21 16:19 GMT+02:00 Christoph Kutzinski ku...@gmx.de:

 Hi,

 I'm trying to set up a CD pipeline with Jenkins where I can

 I) concisely define the relationship (triggers) between the single
 pipeline steps (jobs)
 II) have a nice visualisation of the full pipeline

 The Build Flow plugin is a good fit for I, while the Build Pipeline plugin
 is a nice fit for II.
 However, the Build Pipeline plugin doesn't seem to understand the job
 dependencies defined via the Build Flow plugin.

 Does someone have experiences with similar setups? What is your solution
 for this?


 cheers
 Christoph


 --
 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/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41
 https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41?utm_medium=emailutm_source=footer
 .
 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/CANMVJzmN%2BY7dUWkSh4cL4HnazzU%3DX2nQnoUhNQyXHKstpRDJmQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Re: Build Pipeline plugin and Build Flow plugin

[nicolas de loof]

oh yes indeed, oss version only has a simplified step vizualisation

2015-07-21 16:42 GMT+02:00 Christoph Kutzinski ku...@gmx.de:

 Yes,
 but it doesn't have any visualisation, either (unless I use Jenkins
 Enterprise), has it?

 *Gesendet:* Dienstag, 21. Juli 2015 um 14:37 Uhr
 *Von:* nicolas de loof nicolas.del...@gmail.com
 *An:* jenkinsci-users@googlegroups.com jenkinsci-users@googlegroups.com
 
 *Betreff:* Re: Build Pipeline plugin and Build Flow plugin
  Did you considered using workflow plugin ?

 2015-07-21 16:37 GMT+02:00 nicolas de loof nicolas.del...@gmail.com:

 build flow did introduce buildgraphview-plugin for this exact use case

 build pipeline only can rendre static and mostly sequential pipelines

 2015-07-21 16:19 GMT+02:00 Christoph Kutzinski ku...@gmx.de:

  Hi,

 I'm trying to set up a CD pipeline with Jenkins where I can

 I) concisely define the relationship (triggers) between the single
 pipeline steps (jobs)
 II) have a nice visualisation of the full pipeline

 The Build Flow plugin is a good fit for I, while the Build Pipeline
 plugin is a nice fit for II.
 However, the Build Pipeline plugin doesn't seem to understand the job
 dependencies defined via the Build Flow plugin.

 Does someone have experiences with similar setups? What is your solution
 for this?


 cheers
 Christoph



 --
 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/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41
 https://groups.google.com/d/msgid/jenkinsci-users/trinity-a06e6a93-82f7-4ef9-b2a1-6f05cb05c735-1437488362066%403capp-gmx-bs41?utm_medium=emailutm_source=footer
 .
 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%3DrnO8MxedwwrWBecgE%3Dz-vJVkAfgy%3DKZ04s8uqCBoAw%40mail.gmail.com
 https://groups.google.com/d/msgid/jenkinsci-users/CANMVJz%3D%3DrnO8MxedwwrWBecgE%3Dz-vJVkAfgy%3DKZ04s8uqCBoAw%40mail.gmail.com?utm_medium=emailutm_source=footer
 .
 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/trinity-66b6d313-9f9c-4a6f-a975-d2550388efd6-1437489730953%403capp-gmx-bs41
 https://groups.google.com/d/msgid/jenkinsci-users/trinity-66b6d313-9f9c-4a6f-a975-d2550388efd6-1437489730953%403capp-gmx-bs41?utm_medium=emailutm_source=footer
 .

 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/CANMVJzneprg3%3De2QUPU%2Ba0aZtHU%3DzZQxnZKqU8Rojeig8qGsYQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Docker-build-and-publish failed to push private repo

[nicolas de loof]

Can you check your $HOME dir for .dockercfg file ? It should have private
registry credentials set by the plugin
Also check for a ~/.docker/config.json, if present then docker will use
this one. You then need docker-commons 1.1 for this to be handled correctly.

2015-07-12 11:39 GMT+02:00 eliran shlomo eliranshl...@gmail.com:

 Hi All,
 After updating docker to latest CentOS version (1.6) the build and publish
 plugin failed to push private repository

 Do you really want to push to public registry? [y/n]: EOF
 Build step 'Docker Build and Publish' marked build as failure


 My thoughts it's because of a user\pass problem but i can't find anywhere to 
 put them (until now i used execute shell and used docker login -u).


 any advise?


 Thanks,

 Eliran

  --
 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/0bef23c5-868d-4b8d-9738-db54aaeae065%40googlegroups.com
 https://groups.google.com/d/msgid/jenkinsci-users/0bef23c5-868d-4b8d-9738-db54aaeae065%40googlegroups.com?utm_medium=emailutm_source=footer
 .
 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/CANMVJzk4SyZBYZzU3ykqw%3Dxqn6KBp%2BtPMqpgxP3vv8V2GoEm1A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

email-ext 2.39.3

[nicolas de loof]

I can see a tag and release commit in
https://github.com/jenkinsci/email-ext-plugin/tree/email-ext-2.39.3 but no
artifact on https://updates.jenkins-ci.org/download/plugins/email-ext/

Anything wrong with this release ?
I'm looking for a fix to JENKINS-25940

-- 
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/CANMVJzkvaHMdZ6yLOMxU9VJzu0h0YRXsc4rK_ykx6os09eapCQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Docker Hack Day contribution

[nicolas de loof]

Hi folks,

during Docker Global Hack Day I worked with Yoann on a Docker+Jenkins
plugin :
https://wiki.jenkins-ci.org/display/JENKINS/Oki+docki+plugin

see https://www.docker.com/community/globalhackday#16

If you like it, please vote for it
https://twitter.com/intent/tweet?hashtags=dockerhackdayoriginal_referer=https%3A%2F%2Fwww.docker.com%2Fcommunity%2Fglobalhackdaytext=I%20voted%20for%20oki-docki%20by%20%40ndeloof%20%40dockertw_p=tweetbuttonurl=https%3A%2F%2Fwww.docker.com%2Fcommunity%2Fglobalhackday%2F14%2F
 !
if you don't, please vote too :)

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: New build flow seems to break many things

[nicolas de loof]

groovy DSL was only a quick and dirty implementation, I planned to have
something more robust (and resumable), but with people to use it as a
development console I don't have any option to change internal design now.
This plugin was considered experimental, and I won't invest much time on it
as I consider it's design broken.


2014-05-02 13:50 GMT+02:00 Greg Dickie g...@justaguy.ca:

 Post commit is nice but is not convenient for us as we have stash hosted
 in the cloud and jenkins behind the firewall (due to some specialized
 build slaves). We'd need to expose jenkins. Doable but should not be
 required IMHO.

 We have a multi-stage build, some parallel stuff as well and build flow
 seemed like a great wrapper to encapsulate everything together.

 I'm not sure about abusing the DSL, that seems more like a feature to
 me ;-)

 Anyway thanks for the info. I appreciate the explanation.

 Greg

 On Fri, 2014-05-02 at 07:45 +0200, nicolas de loof wrote:
  Issue with workspace is people are abusing the DSL and start to code
  build custom steps into build flow, not delegating to jobs.
  build flow was designed to orchestrate (flow) jobs together. The
  fact jenkins needs a workspace to poll scm is another story. I prefer
  post-commit notification anyway
 
 
  2014-05-01 16:05 GMT+02:00 Greg Dickie g...@justaguy.ca:
 
 
  Hi Nicolas,
 
 
 I would like to understand the reason for that design.
  Maybe I'm using it incorrectly but it was doing what we
  needed. Why wouldn't you want SCM polling, artifacts, etc.? Is
  the intention that we create build steps to handle that stuff
  or is build flow not the right way to go for this?
 
 
  Thanks,
  Grg
 
 
  On Thursday, May 1, 2014 1:42:11 AM UTC-4, Nicolas De loof
  wrote:
  yes, build-flow is desgined for orchestration, not as
  a regular job with SCM workspace and all
 
 
  that being said, as I can't find spare time to invest
  on this plugin, feel free to take leadership on it and
  make it evolve your way
 
 
  2014-05-01 0:13 GMT+02:00 Les Mikesell
  lesmi...@gmail.com:
  On Wed, Apr 30, 2014 at 5:05 PM, Tim Jackson
  lost...@gmail.com wrote:
   I agree that .11 is a huge step backwards
  for me.  As far as I can tell, the
   build flow plugin no longer triggers the
  failure event of the email-ext
   plugin.  So I am no longer getting failure
  mails for the overall job.
   Setting up a new job to handle the failure
  mail is redundant and can fail
   itself, thus changing the results.  I am
  more apt to just dump the build
   flow plugin and find a more suitable method.
  
   It is very disappointing to have
  functionality removed.  A lot of us have
   based large amounts of work on what it did.
 
 
  I think the only way to make it do anything is
  to set up one job that
  just polls the SCM and triggers the build-flow
  job, then pass all your
  build parameters around to a final job
  executed by the flow that uses
  the copy artifacts plugin to gather up the
  results of whatever the
  other elements did.   Seems like a lot of
  clutter and a confusing
  process to have to start one job but end up
  with the results in
  another.
 
 
  --
 Les Mikesell
   lesmi...@gmail.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-use...@googlegroups.com.
 
  For more options, visit
  https://groups.google.com/d/optout.
 
 
 
 
 
 
 --
 Greg Dickie
 514-983-5400
 just a guy

 --
 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.
 For more

Re: New build flow seems to break many things

[nicolas de loof]

The DSL keyword implementation is just a dozen lines, so easy to
re-implement and extend.

As I said, I'm giving up with this plugin, so if someone volunteer and want
to resurrect workspace support, all yours


2014-05-02 14:55 GMT+02:00 Les Mikesell lesmikes...@gmail.com:

 On Fri, May 2, 2014 at 7:07 AM, nicolas de loof
 nicolas.del...@gmail.com wrote:
  groovy DSL was only a quick and dirty implementation, I planned to have
  something more robust (and resumable), but with people to use it as a
  development console I don't have any option to change internal design
 now.
  This plugin was considered experimental, and I won't invest much time on
 it
  as I consider it's design broken.
 

 Would there be a way to refactor your groovy classes into something
 that could be used as a library by a generic groovy job where being
 able to do other useful operations would not be considered a bug?   It
 would be nice to be able to run other jobs in parallel with some error
 checking without needing to understand the full jenkins api  or being
 a groovy expert but without being intentionally restricted.

 --
Les Mikesell
  lesmikes...@gmail.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.
 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.
For more options, visit https://groups.google.com/d/optout.