18:01:03 #startmeeting 18:01:03 Let the Jenkins meeting commence! 18:01:11 #chair danielbeck kohsuke hare_brain 18:01:11 Current chairs: danielbeck hare_brain kohsuke rtyler 18:01:15 hi all 18:01:19 #topic Last meeting actions 18:01:23 hello 18:01:35 there really weren't any, just ogondza pushing the LTS RC 18:01:41 which I'm pretty sure I saw that he did 18:01:53 of course my days blur together a bit 18:02:14 * rtyler taps foot 18:02:16 alright moving on 18:02:24 #topic LTS status check 18:02:32 without ogondza, not sure what we can really discuss here 18:02:57 dunno 18:03:16 we can all just close eyes and meditate for 15 secs for world peace 18:03:24 I tested it a bit, does not qualify as RC testing though 18:03:59 Not sure if we can release without +1 from Oliver 18:04:23 Is anybody waiting for the release? 18:04:49 while we're meditating, i'll brb 18:06:00 Asked my colleagues just in case 18:06:34 ogondza: o/ 18:06:51 sorry, have we started already? 18:06:53 We're actually at the "LTS Status check" topic 18:07:00 sorry, stale connection 18:07:00 So the floor is yours 18:07:19 the testing looks good 18:07:26 I have heard no complains 18:07:38 I have discovered no issues on my test instance 18:07:44 oleg-nenashev: cool 18:07:53 ship it? 18:08:00 in that case, I thing we are ready to, well, ship it 18:08:13 think, I mean 18:08:32 BTW, we have a pail of new tests contributed by students and no new ATH failures 18:08:41 ATH tests 18:09:01 Yay 18:09:05 So a release is good to go, right? 18:09:07 #action kohsuke, please release 2.60.2 18:09:14 yes, sir 18:09:15 aye aye captain 18:09:27 yey 18:09:27 Then let's move on... 18:09:41 #topic Deprecate "jenkins" official docker image (that we don't control) and "jenkinsci/*" and start deploying our own stuff under "jenkins/*" 18:09:50 this is ndeloof's topic, want to introduce it ndeloof ? 18:09:55 right 18:10:01 so we have "jenkins" official image 18:10:06 we don't control this 18:10:17 #info http://hub.docker.com/_/jenkins 18:10:20 need a manual validation (PR) on docker's repository 18:10:32 +1 for doing it 18:10:43 so, can't guarantee LTS release delay in case of 0-day security issue (worst scenario) 18:10:56 docker used to be reactive, anyway we don't like this, do we ? 18:11:10 that situation isn't a hypothetical 18:11:16 yeah 18:11:17 Does this require some release process updates? IOW, docker image creation should be a part of the release process just like deb,rpm,etc, right? 18:11:20 we also publish under jenkinsci/* various images, including weekly and LTS 18:11:24 it has happened with every major core security release over the 6-9 months that I havfef watched 18:11:34 kohsuke: it already is 18:11:39 oh ok 18:11:42 great 18:11:50 kohsuke: but the "official" docker image MUST have a manual pull request to a repository owned by Docker, Inc. 18:11:56 yes indeed 18:11:57 Yes, that part I know 18:12:02 I think we need to just get rid of the Docker's one. They can set an alias 18:12:06 so we publish under jenkinsci/* registry 18:12:18 they can't. I've asked for it 18:12:27 they plan to implement this "some time" 18:12:34 heh 18:12:47 about official image we can DEPRECATE it 18:12:51 elastic did as well 18:13:03 Is the docker hub access problem for the infra team solved? 18:13:08 but as part of this dicussion, I also suggest we move to "jenkins" registry 18:13:20 just like we moved from jenkins-ci.org to jenkins.io 18:13:27 ndeloof: there is no way we can automatically redirect users from jenkinsci/jenkins to jenkins/jenkins is there? 18:13:33 we can move from jenkinsci/* to jenkins/* 18:13:50 no there's no official way 18:14:01 they have a prototype for it they plan to experiment on "some" images 18:14:09 I can ask we become such beta testers 18:14:10 "some time" :P 18:14:15 I don't want to be a beta tester 18:14:26 this is a critical core distribution path 18:14:31 we can publish on both for some time 18:14:36 * rtyler nods 18:14:40 we probably should do the same for official one 18:14:44 Works for me 18:14:51 and include a deprecation message, both in description and entrypoint script 18:15:00 I will also create jenkins/agent-base and jenkins/jnlp-agent then 18:15:11 Do we own the 'jenkins' org in Docker Hub? 18:15:13 ndeloof: I think we should publish to both, we can start to advertise the jenkins/jenkins on jenkins.io and then when Docker fixes "rename" or "move" we can get rid of jenkinsci/jenkins 18:15:15 they already exists. Those are automated builds 18:15:30 we own it 18:15:37 at least I do, jenkinsadmin, rtyler 18:15:51 it was reserved, I've asked for it 18:16:10 I have access to both, yes 18:16:53 I've setup automated builds for slaves/ssh-slaves and jnlp-slaves docker images from github 18:17:05 my primary requirement is that users accessing/relying on jenkinsci/jenkins don't have their updates disrupted, so for me, we wouldn't be able to shutdown jenkinsci/jenkins until Docker Hub supports a "rename" or "redirect" type feature 18:17:28 (one key user for jenkinsci/jenkins is ci.jenkins.io :)) 18:17:32 this issue already exists for people using official image. There's tons of them 18:17:47 but I also agree we should update the README with a "Deprecation" notice, but continue supporting it "best effort" 18:18:04 we can push on both, this is just about scripting 18:18:10 I also suggest we sign our images 18:18:32 that's a separate issue 18:18:40 let's focus on the topic at hand 18:18:43 ok 18:18:50 are there any objections to making a deprecation notice on the "jenkins" official image? 18:19:19 * rtyler starts his stop watch 18:20:03 no 18:20:07 going once 18:20:10 fine for me 18:20:19 for info : https://github.com/docker-library/docs/pull/948 18:20:29 #agreed no objections to noting the "jenkins" official image as deprecated 18:20:45 they just ask we push 2.60.x and document no further update will be released here 18:21:03 honestly, I don't think that's good enough, I think we should still keep it updated for some time 18:21:09 we'll need to write a blog post about this too 18:21:32 #action rtyler to work with ndeloof on communicating the deprecation of the "jenkins" image 18:21:38 I suggest we also include a warning notice in the entrypoint script 18:21:53 but let's discuss this later 18:21:56 * rtyler nods 18:22:20 are there any objections to double-publishing key images to jenkinsci/ and jenkins/ ? 18:23:07 beep boop beep boop 18:23:19 no 18:23:36 maybe we should push a "ci.org" image to "jenkins" registry, just for the joke ? 18:23:37 +1 18:23:38 ndeloof: would you be okay with raising this topic again in 6 months and perhaps Docker Hub will support "moves" or "redirects" at that point and we could then deprecate jenkinsci 18:23:43 ? 18:23:52 works for me 18:23:56 +1 was for double-pushing 18:24:00 I'll ask them for schedule 18:24:05 at least I know who to ask now 18:24:09 #agreed we will start double-publishing key images for jenkinsci/ and jenkins/ orgs on dockerhub 18:24:30 rtyler ndeloof: Can I get access to jenkins org to setup Agent images? 18:24:31 #action ndeloof to raise the topic of moving/deprecating the jenkinsci org on DockerHub in 6 months or so 18:24:44 oleg-nenashev: i'll handle that after the meeting :) 18:24:50 ty 18:24:59 they're already setup 18:25:03 as automated builds 18:25:07 ndeloof: do you think this is enough house-keeping on our docker images for today? or are there other aspects we should discuss? 18:25:12 https://hub.docker.com/r/jenkins/jnlp-slave/ 18:25:20 https://hub.docker.com/r/jenkins/ssh-slave/ 18:25:23 ndeloof: "slave" must die 18:25:37 ok. Then let's rename 18:25:38 #action rtyler to map all ther existing jenkinsci users over to the jenkins org 18:25:44 So I want to change them and deprecate the old ones 18:25:56 anything else for this topic today ndeloof? 18:26:02 looks good to me 18:26:10 we can continue to discuss the things we need to do afterward in #jenkins 18:26:22 great, thanks for bringing this topic up ndeloof 18:26:23 right 18:26:41 that looks like it for today, so... 18:26:43 #topic Next meeting 18:26:51 have to leave for dinner with wife's familly, thanks folks 18:27:06 my calendar says August 2nd I don't think there are any major holidays then 18:27:30 #info Next meeting August 2nd, 18:00 UTC 18:27:32 #endmeeting