18:00:03 #startmeeting 18:00:03 Let the Jenkins meeting commence! 18:00:05 \o/ 18:00:09 #topic Last meeting actions 18:00:28 kohsuke did release 2.60.2 \o/ 18:00:52 around the dockerhub changes we discussed last time 18:01:01 I have given everybody access that had access before (IIRC) 18:01:16 but I have not yet finished collaborating with ndeloof on a blog post about the change 18:01:29 I know he started a draft, but I haven't seen it opened as a pull request against jenkins.io 18:01:47 that's it for the last meeting actions 18:01:57 #topic LTS status check 18:02:19 it seems that ogondza isn't here 18:02:23 :( 18:02:27 are there any other folks that could update on the LTS status? 18:02:57 Some fixes have been backported, but I am not sure the backporing is finished 18:03:09 danielbeck: do you happen to know/ 18:03:16 I see some lts-candidate tickets without .3 decision 18:03:41 #info https://groups.google.com/forum/#!topic/jenkinsci-dev/3Vz_Db-rNzk 18:04:36 JENKINS-45057 sucks 18:04:46 * rtyler opens up the ticket 18:05:02 oh that one 18:05:03 So maybe we want to consider landing a fix from jglick or stephenc into .3 18:05:17 it doesn't look like a fix has even landed in a weekly for that yet 18:06:19 rtyler: we have 2 pending PRs 18:06:23 I hope to land one 18:06:34 do you recall from the schedule when .3 is supposed to be? 18:06:40 Anyway, we need Oliver to make decisions, so I propose to take it offline 18:06:50 .3 should be out in 2 weeks 18:06:55 ah, so there's time 18:07:19 oleg-nenashev: but regardless of what oliver thinks, a fix still needs to make its way into a weekly first 18:07:21 Yep. Usually ogondza releases RCs on Thursdays after the governance meetings 18:07:22 right? 18:07:27 +/- 18:07:42 Once we merge fix to the master, we COULD backport it to RC 18:07:49 Not an ideal case, of course 18:07:59 gotcha 18:08:19 So let's take it offline 18:08:20 I believe .3 before KK gets back from vacation 18:08:34 KK is not needed for RC 18:08:38 fair enough, just don't want it to get lost with everybody taking their summer vacations :) 18:08:46 heh 18:09:04 I'm surprised anybody from europe is here right now, it's august, that's vacation month isn't it? :P 18:09:05 #action oleg_nenashev to follow-up on JENKINS-45057 in MLs 18:09:20 Well, oleg-nenashev doesn't know the word vacation 18:09:25 heh 18:09:27 Yeah, it's a dead season in Europe 18:09:32 I already had mine :) 18:09:38 Next one is after JW 18:09:53 alright, that's a good enough segue 18:09:56 alyssat_: you awake? :D 18:10:02 #topic Jenkins World organization/status update 18:10:10 hello 18:10:22 I know that I have seen some of the Jenkins project's booth stuff, but I figured you could update folks on the activities today alyssat_ 18:10:27 we have a bunch planned :-! 18:10:37 A quick update to Jenkins World 18:10:47 1,175 registrations at the moment. Jenkins World consist of 5 tracks: 3 community tracks, and 2 DevOps tracks. 60+ sessions, 16+ trainings workshops, plus onsite Jenkins certification. 18:11:16 wrt community activities, includes: Contributor summit info# https://www.meetup.com/jenkinsmeetup/events/241213280/. Currently 72 rsvps. 18:11:31 #info https://www.meetup.com/jenkinsmeetup/events/241213280/ 18:11:32 info# https://www.eventbrite.com/e/2017-jenkins-contributor-appreciation-evening-tickets-32591665549. Jenkins Appreciation evening at Autodesk Gallery If any one here is going to Jenkins World and haven't RSVP'd for the party pls do so. 18:11:42 oh right 18:11:51 * rtyler tries to remember if he already RSVPed 18:11:59 * oleg-nenashev too 18:12:04 #info Jenkins World 2017 is in San Francisco the week of August 28th 18:12:07 pls do if you haven't 18:12:15 #info https://www.cloudbees.com/jenkinsworld/awards The inaugural Jenkins Community Awards. Koshuke will announce and publicly recognize the 3 folks who has done great work for the Jenkins project in the areas of advocacy, security and contributions. All nominees were excellent contenders, it was not easy for the committee to vote on this. 18:13:24 alyssat_: what about the project's booth, can you share the plan with that? 18:13:31 wrt Jenkins project booth, on the expo floor - we will have 18:13:31 Ask the Experts as usual, panel consist of 19 volunteers which includes frequent contributors, JAM organizers and board members. 18:14:12 I will write a blog to highlight our experts and their areas of expertise shortly. 18:14:35 alyssat_: I think a number of folks here are signed up for expert duty 18:14:44 alyssat_: anything besides our smiling faces and maybe a laptop we should bring? 18:14:48 and based on last year's success, at lunch time, there will ten 15-min demos showcasing related topics like Docker, Pipeline, Blue Ocean, Git, etc. Blog to follow as well 18:15:39 I don't think so. we'll have t-shirts for our experts and goodies 18:16:09 ooooOooooo 18:16:15 new at the booth this year is PR corner - this will be a dedicated area within the booth where danielbeck (leading this effort) will help show attendees how to do a PR or complete one. The goal is to get new blood to participate in the Jenkins project. 18:16:45 those are the highlights for JW 18:17:10 any questions for alyssat_ on the topic of Jenkins World? 18:17:47 hope to see everyone here at the conf 18:17:52 * rtyler watches the clock tick 18:17:57 * schristou is excited! 18:17:58 oh that's a cool idea re: the PR corner 18:18:01 I like that! 18:18:11 Any chance we discuss JAMbassador by the contributor summit? 18:18:23 Seems this thread is dead 18:18:35 we need to revive this for sure 18:18:43 the latter part of the day of the contributor summit is open-ended 18:18:51 yep 18:19:35 oleg-nenashev: let's talk off line on this some more 18:19:38 anything else? 18:19:52 nothing from me 18:20:06 #topic Infra status update 18:20:12 this should be short and sweet 18:20:29 olblak and I (mostly him) have continued to move stuff over to Azure and Kubernetes 18:21:01 we hit a snag with upgrading our Kubernetes cluster, since it's one of those pieces of technology that's best upgraded with a blue/green deployment rather than trying to update different parts of the cluster 18:21:17 when he's back in the office, we should be able to wrap that all up by Jenkins World and move a few more services over 18:21:48 we've also recently opened the flood-gates for all plugins under github.com/jenkinsci on https://ci.jenkins.io which seems to be going very well! 18:22:14 I've seen a lot of developers taking advantage of it, and the built-in cross-platform testing the `buildPlugin()` method provides 18:22:29 and the only other thing I wanted to bring up 18:23:02 #info There is an infra status meeting every monday at 19:30 UTC on jenkins.io/hangout 18:23:10 any questions before I move on 18:23:55 * rtyler watches the clock tick 18:24:37 Do we know what happened with changelogs on Monday? 18:24:51 something happened with changelogs on monday/ 18:24:53 I mean the weekly release changelog publishing glitch. CC danielbeck 18:24:56 oh, the delay 18:25:21 yeah, when I made some changes to how jenkins.io gets shipped off to production, I didn't take into consideration the script on the server side which unpackes the generated site 18:25:25 I fixed that yesterday 18:25:30 thanks! 18:25:42 I haven't taken a look in a while; did anyone get a chance to poke at the board election setup? 18:25:46 This time the community rating was important due to JENKINS-45895 18:25:54 Yeah, election... 18:26:01 orrc: that's dependent on the kubernetes work that olblak is doing 18:26:15 he's already taken the original work from ndeloof and prepared it to actually run "in real life" 18:26:24 Nice 18:26:25 just needs to be deployed properly with storage behind it 18:26:34 right now account-app is effectively stateless (state is really in LDAP) 18:26:41 the election stuff needs a reliable local disk 18:26:58 https://issues.jenkins-ci.org/browse/INFRA-1127 FWIW 18:27:34 my mental milestone is that once the bloody app is deployed and I can actually /operate/ the election process, then we can do the needful with candidacy/etc 18:28:06 for better or worse, part of the reason this took a while is that olblak had to do a bit more java than he, or I, had anticipated to get this in shippable shape 18:28:15 anything else? 18:28:49 alright, i'm gonna keep moving us along 18:29:05 #topic Jenkins mark usage request from CloudBees for CloudBees Jenkins Advisor 18:29:08 #info https://groups.google.com/forum/#!msg/jenkinsci-dev/PoxnVCKa9NM/2F2iLlDuBwAJ 18:29:32 this was proposed on the dev list already by kohsuke, who is asleep on the other side of the world right now :) 18:29:38 haha 18:30:04 nobody's responded on the dev list about the topic, are there any questions I can answer? 18:30:16 * oleg-nenashev abstains 18:30:19 I read the request, and I am +1 to it. 18:30:49 meets our past standards for usage of the mark AFAICT. 18:30:55 I was unable to find any overlaps with existing naming in the internet though 18:31:16 a concern was raised to me privately about advisor being close to "advisory" 18:31:40 insofar that the individual was concerned confusion with Jenkins security advisories 18:31:47 Also Advisor and Ambassador if alyssat_ plans to stick to that name 18:32:04 But it's not something really important 18:32:11 hm. neither of those seem like a big deal to me. 18:32:18 personally, I don't think this is going to be a concern since our previous conditions with CloudBees have been that "subsets" of these marks are not acceptable usages 18:32:38 i.e. CloudBees messaging should always use the full mark "CloudBees Jenkins Advisor" and never a subset thereof 18:32:57 alyssat_ and her boss are on the hook for policing and enforcement :) 18:33:12 :) that's correct 18:33:38 Seems ok 18:33:46 Iā€™m ok with it. +1. 18:34:14 any other questions I can answer? 18:35:12 #agreed "CloudBees Jenkins Advisor" sub-license granted with the previous conditions which have been applied to other sub-licenses 18:35:41 #action alyssat_ to update the https://wiki.jenkins.io/display/JENKINS/Approved+Trademark+Usage page accordingly 18:36:26 ogondza: welcome! we already discussed some LTS things. 18:36:38 if there are specific points you wish to discuss, I can bring the topic back 18:36:39 rtyler I don't have access to update the page. 18:36:50 Gimme access and i'll be happy to do it :) 18:36:51 alyssat_: alright, we'll figure that out later 18:37:45 #topic Deprecate Remoting CLI1/JNLP1/JNLP2/JNLP3 protocol 18:37:49 oleg-nenashev: you're up buddy 18:37:54 #info https://groups.google.com/forum/#!topic/jenkinsci-dev/sN2wHHFOJPg 18:38:14 So I need approval for a potentially breaking change 18:38:54 I am going to use approach similar to Java 8, and the breakage is actually possible only in the case of custom packaging and legacy infra 18:39:43 I have got +1s from batmat and stephenc, but I am ready to answer questions if any 18:40:15 oleg-nenashev: the email subject says JNLP1/2 the meeting topic says 1/2/3 18:40:17 * oleg-nenashev noticed "age cases" in the proposal text :( 18:40:19 I'm a little confused 18:40:38 rtyler: JNLP3 is already deprecated. We just need to do it explicit in Jenkins UI 18:40:51 ah 18:41:21 I think this is an overall positive change so I'm an enthusiastic +1 18:41:23 It has been deprecated by https://github.com/jenkinsci/remoting/commit/fe2587b7f9d78334e0ab05ab0b95f39b4b600a25 18:41:40 oleg-nenashev: is this something that should be communicated like the java 8 change on the blog and users list like batmat did? 18:41:59 rtyler: Yes, I am going to write a blog post 18:42:22 Go for it 18:42:23 +1 18:42:23 I also have a long-standing Remoting Subproject branch, which will aggregate blogposts and docs 18:42:41 Remoting subproject will be released as well this week 18:42:55 If I pass the review by rtyler of course :) 18:43:18 i'm sure what you've written will be perfectly fine 18:43:51 any other concerns for oleg-nenashev about his proposal? 18:45:03 quiet group today :P 18:45:12 FYI Remoting will be also updated to Java 8 soon 18:45:15 maybe everybody is busy making their presentations for Jenkins World 18:45:43 šŸ˜„ 18:46:04 empty comment? 18:46:17 heh 18:46:31 (smiley face) 18:46:37 #agreed Deprecate Remoting CLI1/JNLP1/JNLP2/JNLP3 protocol 18:46:55 #action oleg-nenashev to write a blog post to communicate changes to users when necessary 18:46:55 #action oleg_nenashev to deliver docs and blog posts 18:46:58 hah 18:47:00 jinx! 18:47:22 will do it anyway 18:47:36 #info https://github.com/jenkinsci/jenkins/pull/2950 is the pull request for those who may be interested in the changes 18:47:43 thanks oleg-nenashev 18:47:46 #topic Next meeting 18:48:12 looks like August 16th is the next scheduled time 18:48:33 #info next meeting August 16th, 18:00 UTC 18:48:40 #endmeeting