20:05:04 #startmeeting AnsibleFest Austin: Contributors Summit - Zuul 20:05:04 Meeting started Mon Oct 1 20:05:04 2018 UTC. 20:05:04 This meeting is logged and archived in a public location. 20:05:04 The chair is cybette. Information about MeetBot at http://wiki.debian.org/MeetBot. 20:05:04 Useful Commands: #action #agreed #halp #info #idea #link #topic. 20:05:04 The meeting name has been set to 'ansiblefest_austin:_contributors_summit_-_zuul' 20:05:26 #info bluejeans link https://bluejeans.com/7025862841/ 20:06:02 #info etherpad link https://etherpad.openstack.org/p/ansible-summit-october-2018-zuul 20:07:42 can people hear us on bluejeans 20:07:54 Shrews: ^ 20:07:55 no 20:08:07 good :) 20:10:31 hard to hear monty 20:11:21 :-P 20:23:24 bcoca: etherpad is https://etherpad.openstack.org/p/ansible-summit-october-2018-zuul -- the "core" question we had was the first one in the pad about carrying patched modules, we're answering the question from someone in the room right now 20:25:37 msot of those dont seem as much 'forks' as 'disabled' 20:35:39 if they dont report quota correctly .. do they report billing correctly? 20:36:07 yes 20:36:24 mr glorious 20:36:44 sorry over here :) 20:36:47 im sorry was there a question? 20:36:53 there is about to be :) 20:37:00 ah, yes read that 20:47:28 cannot hear 20:51:09 bcoca: how about now? 20:51:21 better 21:02:02 i wish we could build that for roles 21:02:16 so users can have 'local patch' to external role and 'reapply on update' 21:03:02 but only systems i know do that are bsd ports/gentoo ebuilds 21:05:18 I am working on it now! 21:05:24 and failing! 21:05:30 not easy 21:05:46 both those systems require a 'version trailing patches' 21:06:16 so if you have a 2.3.1 patch you'll need a new one once 2.3.2 is out (most of the time) 21:16:14 i've spent 15yrs trying to forget perforce 21:16:42 General reminder, please ensure actions are being tracked with `#info` or on Etherpad 21:19:04 perforce was the best thing since sliced bread 21:19:07 haha 21:19:34 not imho 21:19:37 moved from it to github, luckily we didn't care about history or anything, we just wanted it to go away 21:20:03 o/ 21:20:07 jlk: https://zuul-ci.org/docs/zuul/developer/specs/container-build-resources.html#git-repo-sync 21:20:24 jlk: the code blocks in that section seem to work 21:22:44 corvus: ah right. I went down that path too, figuring out how to implement something for git that wasn't ssh, that was also terrible. 21:22:50 I'm glad this works for what it does 21:23:08 jlk: i mean, that's about all the testing i've done, but at least that much didn't not work :) 21:24:26 lol truth 21:34:50 #info there's a Zuul booth at AnsibleFest (4th floor, booth 402) 21:36:55 #info "Zuul v3 For Gating": https://www.youtube.com/watch?v=6177329H4Tg 21:36:57 #info "Zuul Testing the Future": https://www.youtube.com/watch?v=KXh0sh3ETkQ 21:45:20 15 min left for the session 21:46:39 * Shrews departs 21:46:51 Shrews: o/ 21:49:35 #info Zuul session at AnsibleFest https://agenda.fest.ansible.com/SessionDetail.aspx?id=482140 21:51:06 #info Another Zuul session at AnsibleFest https://agenda.fest.ansible.com/SessionDetail.aspx?id=482019 22:01:25 #endmeeting