Friday, 2017-09-08

*** electrofelix has joined #openstack-jjb08:38
*** hashar has joined #openstack-jjb09:01
*** hashar has quit IRC13:28
*** hashar has joined #openstack-jjb13:28
waynrwooo i actually remember the meeting13:47
waynrhelps that i'm two timezones closer to UTC13:47
zxiironice13:48
zxiiroelectrofelix: we meeting today?13:48
electrofelixsounds like it13:50
electrofelixI've been distracted, working on getting a DevOpsDays Conference going locally13:50
zxiirooh nice. I signed up for the online one13:50
waynrthis old engineer i used to work with always refused to say the word "meeting"13:50
waynrinstead he always said the word "beating"13:50
waynr"time for a beating"13:50
zxiirothat sounds less fun and 'meeting' is already not that fun haha13:51
zxiirofun sounding13:51
waynrwell i'm a judoka so in the right context a beating is actually quite fun ;)13:51
waynrelectrofelix: nice! I volunteered at the portland devopsdays conference a couple months ago13:51
zxiiroI guess that makes sense in that case13:52
zxiiroalright should we start since we're all here anyway?13:52
waynrsure13:52
zxiiro#startmeeting jjb13:53
openstackMeeting started Fri Sep  8 13:53:14 2017 UTC and is due to finish in 60 minutes.  The chair is zxiiro. Information about MeetBot at http://wiki.debian.org/MeetBot.13:53
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.13:53
openstackThe meeting name has been set to 'jjb'13:53
zxiiro#chair waynr electrofelix13:53
openstackCurrent chairs: electrofelix waynr zxiiro13:53
zxiiro#topic jjb-2.013:53
zxiiroI guess this is really our only topic at the moment unless someone else wants us to discuss something later?13:54
zxiiroelectrofelix: so I think we should get this https://review.openstack.org/333076 landed asap before another patch is merged that breaks this again.13:54
waynrhmm wasn't there someone else were were considering as a jjb core a month or two ago? did that ever happen?13:54
waynrs/er w/ w/13:55
electrofelixI was hoping to understand the purpose of the __deepcopy__ a bit more13:56
zxiirojust looked at the last meetings notes I don't see it13:56
zxiiro#info zxiiro thinks https://review.openstack.org/333076 should land asap13:56
zxiiro#info electrofelix wants to understand the purpose of __deepcopy__ a bit more13:57
zxiiro#action electrofelix to review https://review.openstack.org/33307613:57
zxiiroelectrofelix: ok13:57
waynr#info waynr also thinks https://review.openstack.org/333076 should land sooner rather than later13:57
zxiiro#link https://review.openstack.org/#/q/status:open+project:openstack-infra/jenkins-job-builder+branch:master+topic:2.0-config-format 2.0 config format13:58
zxiirowaynr: electrofelix: ^ I think we decided to go with this? if so we should probably merge those patches13:58
zxiirolooks like there's a few merge conflicts for 3 of the patches. I can look into fixing that13:58
zxiiro#action zxiiro to resolve merge conflicts in https://review.openstack.org/#/q/status:open+project:openstack-infra/jenkins-job-builder+branch:master+topic:2.0-config-format13:59
waynri can review those patches13:59
waynrmight need reminders occasionally though ;)14:00
electrofelixzxiiro: I'm go with that, I'll start reviewing and will look out for the updates14:00
zxiirosounds good14:00
zxiiro#action electrofelix & waynr to review 2.0-config-format patches14:00
zxiiro#link https://etherpad.openstack.org/p/jjb_api_v2.0 EtherPad of JJB 2.0 items14:00
zxiirook i think this is the last thing... electrofelix, waynr anything from the etherpad we want  to discuss?14:01
electrofelixwaynr: can you help me understand what's happening with __deepcopy__, what changed to require it?14:01
electrofelixguess we can discuss after the meeting14:01
waynryeah i can go over that with you14:02
waynrduring meeting or not14:02
zxiiroyeah we can talk about that now too14:02
zxiiroelectrofelix: there was an email thread about it14:02
waynri have to look it over again myself actually but i remember thinking it looked legit14:02
electrofelixwaynr: was it not added recently?14:04
zxiiroelectrofelix: the jinja patch needs it. Let me look up the email thread...14:04
electrofelixah found it14:04
zxiiroelectrofelix: oh? you got it? ok14:04
*** openstackgerrit has joined #openstack-jjb14:09
openstackgerritThanh Ha proposed openstack-infra/jenkins-job-builder master: Default groovy-postbuild to newest plugin format  https://review.openstack.org/47837214:09
openstackgerritThanh Ha proposed openstack-infra/jenkins-job-builder master: Default slack to newest plugin config format  https://review.openstack.org/47866914:11
openstackgerritThanh Ha proposed openstack-infra/jenkins-job-builder master: Default conditional-publisher to newest plugin format  https://review.openstack.org/47837814:12
zxiiroelectrofelix: waynr alright I fixed the 3 merge conflicts in the meantime.14:13
zxiiroanything else we want to discuss during the meeting?14:13
zxiiroelectrofelix: I think the only other thing for JJB 2.0 is you mentioned you wanted to redo the config plugin system. Any progress on that?14:14
electrofelixyes, just not quite ready with the second patch, I almost forgot I had a question on it before I made a change14:17
electrofelixhttps://github.com/openstack-infra/jenkins-job-builder/blob/master/jenkins_jobs/modules/helpers.py#L49014:19
electrofelixwith the changes we've made to get plugin configuration information from specific plugin sections, I think this __future__ section should be dropped for the v2 release for individual plugin behaviour and instead added to the two plugins it affects14:20
zxiiroagreed. I think that's the right thing to do14:20
zxiirowaynr: ^14:21
electrofelixas in a) switch it to default to taking the order from the yaml, and b) place the ability to use the old behaviour under "[plugin 'trigger_parameter...'] use_old_param_order = True"14:21
electrofelixor something like that, that was the last thing blocking ensuring that only the 'plugins' namespace needed to be passed to the plugins14:21
waynrthat sounds good to me14:23
waynrwell it'll break JJB for my ex coworkers but all they will have to do is avoid upgrading or chang their config files14:24
electrofelixwere they using that option?14:24
zxiiro#info electrofelix asks if we should move param order setting to inside plugin sections for V214:25
electrofelixor rather were they using trigger parameterized plugins and relying on the old behaviour of using the order defined in the code for the precedence of the parameters?14:25
zxiiro#agreed We will move the param order config into plugins section.14:25
waynroh wait14:25
waynrnevermind, i was confused...i was misremembering something and misreading what you wrote14:26
waynrit won't break anything for excoworkers of mine14:26
electrofelixas in predefined-parameters would be overridden by current-parameters even if the yaml put it afterwards14:26
electrofelixyeah, I just realised it might cause you to think I meant about the project params precedence order ;)14:27
waynryah i see what you mean now14:27
zxiiroelectrofelix: I feel confused now. so currently if someone lists a parameter last it will take precedence over the same parameter if it's defined above?14:30
zxiiroelectrofelix: so with the change what happens?14:30
zxiiroelectrofelix: it will take the first defined parameter listed?14:30
electrofelixzxiiro: in the trigger parameter plugins, the original code hardcoded the order the XML was emitted for each of the possible settings, however Jenkins allowed you to order them to control which ones would override others and thus control the value of the parameter passed to the triggered build14:32
electrofelixso a user might assume that they could order the yaml definition for that plugin in the same way to decide that the can pass through 'current-parameters', and then override a single parameter by placing the 'predefined-parameter' block afterwards14:33
electrofelixunfortunately this was not supported by the code at the time and instead it would enforce a specific order https://github.com/openstack-infra/jenkins-job-builder/blob/master/jenkins_jobs/modules/helpers.py#L475-L48614:33
zxiiroelectrofelix: oh i see. ok understood14:34
electrofelixSo to change it to allow it to be controlled based on the order the user would specify to match what jenkins allowed, and at the same time not break any existing ones needed to allow switching between old hardcoded order and new user defined order14:34
electrofelix;)14:34
zxiiroi think i never noticed this because i almost exclusively use only string parameters14:35
waynrdo you pass parameters to downstream jobs?14:36
zxiiroyes14:36
zxiiroin that case i almost exclusively run only paramters from property files14:37
waynrwell anyway i agree with dispensing with the __future__ config section in favor of the plugin specific config section14:39
zxiiroYeah. As long as we document it. I think it's fair game for V214:40
zxiirook anything else to discuss? If I'm correct I think V2 is just blocked on 3 things at the moment:14:41
zxiiro1) YAML Parser patch14:41
zxiiro2) Plugin namespace config14:41
zxiiro3) 2.0-config-format14:41
zxiirowhich all have action items so I think we're on track to getting 2.0 out.14:41
zxiiroif we can get 1) and 3) merged soon we'll be a little closer.14:42
zxiiroelectrofelix: think you can get YAML Parser patch in today? should we try to iron it out now that everyone's here?14:42
zxiiro#action electrofelix to continue working on plugin namespace config patch14:43
electrofelixjust approved, I'd been experimenting with it as we talked and read back over the email thread as well14:44
zxiiroawesome14:44
zxiiroalright if there's nothing else I guess we can end the meeting?14:44
waynr+114:45
electrofelixI think I'm good with all of the reviews for '3', so I'll try to get something up soon for '2'14:45
zxiirogreat. sounds good14:45
zxiiro#endmeeting14:46
openstackMeeting ended Fri Sep  8 14:46:01 2017 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)14:46
openstackMinutes:        http://eavesdrop.openstack.org/meetings/jjb/2017/jjb.2017-09-08-13.53.html14:46
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/jjb/2017/jjb.2017-09-08-13.53.txt14:46
openstackLog:            http://eavesdrop.openstack.org/meetings/jjb/2017/jjb.2017-09-08-13.53.log.html14:46
zxiirowaynr: electrofelix: if nothing else comes up my gut feeling is we can probably do a 2.0 beta release next meeting and maybe a final release by next month?14:46
electrofelixI'll grab the champegne14:46
waynrwoooo14:47
openstackgerritThanh Ha proposed openstack-infra/jenkins-job-builder master: Allow update to provide plugin_info via yaml  https://review.openstack.org/32672214:52
openstackgerritMerged openstack-infra/jenkins-job-builder master: Move macro expansion into YamlParser.  https://review.openstack.org/33307615:41
*** hashar is now known as hasharAway15:45
waynrwoo15:46
*** electrofelix has quit IRC17:50
*** yland has joined #openstack-jjb18:18
*** yland is now known as Guest6451818:18
*** hasharAway has quit IRC18:28
*** hashar has joined #openstack-jjb18:29
*** hashar has quit IRC20:32

Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!