Re: access to jenkins docker hub group

[Kohsuke Kawaguchi]

I think this conversation belongs to the dev list.

I vaguely recall working on Dockerfile to create a Jenkins image, but I can't find it, and in any case I thought you had one already, so I think we should base this effort on yours.

I agree that having the versioned tag on jenkinsci/jenkinsci in https://registry.hub.docker.com/repos/jenkinsci/ would be great. When you have the Dockerfile, let me know so that I can integrate that to the release process.

2014-07-21 3:22 GMT+02:00 Michael Neale <mne...@cloudbees.com>:

Great - thanks. 

BTW the "docker" jenkins image is in process - we agreed that LTS made sense there - but I would like to have a latest one in the jenkins namespace - are you aware of anyone setting that up? We can run the build if necessary - but would be nice to have a weekly-ish jenkins/master image or similar (not sure of name)

On Fri, Jul 18, 2014 at 10:25 PM, Kohsuke Kawaguchi <kkawa...@cloudbees.com> wrote:

Done.

2014-07-18 5:31 GMT+03:00 Michael Neale <mne...@cloudbees.com>:

Can you add me? 

--
Kohsuke Kawaguchi

--
Kohsuke Kawaguchi

[Michael Neale]

Hi All. 

Docker have an "official" build repository of images (hub.docker.com sometimes features them). These are the images you can get by running "docker pull redis" - ie global namespace. The idea being that they are a neat place to start - for people either new to docker or new to the tool they want to run.

As of today there is version of jenkins in this docker repository which is a vanilla ubuntu (14.04) running jenkins LTS. 

https://github.com/cloudbees/jenkins-ci.org-docker - is the source. 

This also includes some basic dev tooling on the assumption that people will want to run builds inside the container (as well as slaves - it can do slaves as the slave jnlp port is fixed - necessary for docker to forward the port - it can't be dynamically assigned - hence the init.groovy - that is all it does). 

docker run -p 8080:8080 jenkins - is the minimal needed to run it (and you will have LTS jenkins)

LTS was picked as the process for updates to the official repositories is not compatible with a high frequency releases (basically a PR has to be issued and reviewed to the "stackbrew" system) - but LTS is perfect. 

I would like to look at doing a very similar image for weekly releases that is published to the jenkinsci hub group - this would be published with each release, but based on pretty much the same image but non LTS. 

Happy to discuss more, Nicolas suggested we could shift to Oracle JDK (as that is more common) - currently it is JDK, and perhaps should not bundle maven with it and so on (I do like using OS packages where possible as it makes it easy for the user to upgrade locally in place - it is perfectly reasonable to have a Dockerfile that says "FROM jenkins" and add your own deps, update and so on). 

Please do fork and send pull requests, this is not immutable and generally easy to change - only a PR is needed to update it. 

[Kanstantsin Shautsou]

We got a reasonable question from IRC about official jenkins image:  "@amouat I'm just wondering if it's still being developed - there are a lot of open issues and no commits for around 2 months"

In addition i have the next questions:

1) Why official Jenkins docker image ends to CloudBees repositories?

2) Where is wiki page with description?

[Michael Neale]

Being fixed https://twitter.com/ndeloof/status/575351076280471552

--
You received this message because you are subscribed to a topic in the Google Groups "Jenkins Developers" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/jenkinsci-dev/tIrviKHXbJE/unsubscribe.
To unsubscribe from this group and all its topics, send an email to jenkinsci-de...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/1fc501af-35aa-44e5-b5c6-37d716cc69fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael Neale]

I think it was moving to the official Java base image (not sure what that uses)

On Wed, 11 Mar 2015 at 7:38 am Adrian Mouat <adrian...@gmail.com> wrote:

Thanks for looking into this.

FWIW, you probably won't be able to use the Oracle JDK due to licensing issues.

[nicolas de loof]

Yes, I used official Java image, as Docker team rejected use of Oracle JDK in an official due to redistribution restriction. Something odd imho as they already distribute it on dockerhub via many custom image users have pushed as trusted builds - they just didn't manually checked.

--
You received this message because you are subscribed to the Google Groups "Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-de...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CAKVMTi6oJS2bRJF5vMXTtFCMVfjARci9RzC4-c5Kw0Fn2r%2Bp1w%40mail.gmail.com.

[Michael Neale]

I think trusted builds (a misnomer - as they have admitted) are more the responsibility of original Dockerfile authors - while official images have the "blessing" (in an app-store sense) of Docker Inc - hence they are trying to do the right thing. 

To view this discussion on the web visit https://groups.google.com/d/msgid/jenkinsci-dev/CANMVJzkoRO%2BHy5XhN%2BJ0UShX_V-%2BaGe2aRXZ3%3D4Xsbtq2yjwAQ%40mail.gmail.com.