Thursday, 2017-01-19

jeblairjlk: the 'zuul' trigger is intended to handle cases like that, though that specific case is not implemented (yet)00:04
jlkyeah, looks like I'd need some sort of event that marks success of a pipeline00:05
jlkjeblair: I'll tell you what I'm trying to solve. Github has the concept of "status" that can be set on the commit(s) of a PR. This is typically what jenkins would set or travis, or zuul. Set to pending as a reporter, set to success on success of the check gate.00:10
jlkjeblair: I'd like our gate pipeline to be triggered by the check pipline completing successfully00:10
jlkand when we set status to success, the webhook event that github sends back doesn't reference the /pull-request/, it references the /commit/, without any breadcrumbs back to which PR(s) has that commit as the head.00:11
jlkso instead of using github set status -> respond to status webhook event   as a round-about way to trigger ourselves, I was hoping to short-circuit it within zuul itself.00:12
mordredjlk: out of curiosity - why have the gate pipeline be triggered by the check? wouldn't that essentially make the gate pipeline triggered by patchset upload and bypass human review?00:15
mordredjlk: (just making sure I grok what you're aiming to accomplish in my brainhole)00:15
jlkNo, because the gate pipeline would have a requirement on the human review being completed00:15
mordredjlk: ahhhhhh. thank you - I grok now00:15
jlk(by a human (with write access) providing a positive review)00:15
jeblairso this is for the case where human review happens before check finishes, but check is still a pre-req for gate00:15
mordredjlk: also - wow, with the event not referencing the pull-request :(00:15
jlkthis may help: https://github.com/BonnyCI/projman/wiki/GitHub-Pull-Request-Check-and-Gate-Design00:16
jlkmordred: yeah, it's weird. THe status belongs to the commit object, not the pull request object00:16
jlkand multiple branches may have that commit object00:16
jlkand even more fun, if you close a PR with a commit that has a status, then re-open it, the commit _still_ has that status, like CI was already done!00:17
mordredjlk: I really with the gh review system was more mature - it's so clearly a v0.100:17
jeblairjlk: aside from the event, does the actual data model also have the status associated with the commit object?00:18
jlkjeblair: yes00:18
jeblairlike, if you okay a commit that is in 2 prs, and you look at both prs, they both say 'ok'...00:18
jlkhttps://developer.github.com/v3/repos/statuses/00:18
jlkjeblair: that's correct00:18
jlkit's _weird_00:18
jlkI'm really kind of tempted to make Zuul drop a positive review instead of status00:19
jeblairjlk: i think the zuul trigger might be an okay thing to do, but also, i feel like being able to respond to that event might be a good thing generally, so i might advocate for the github driver being able to create synthetic events for all prs which contain a commit whose status just changed00:19
jlkbecause that's attached to the PR, and it fits more easily with the "approval" model.00:19
jeblairjlk: that might be a good option too.00:19
jlkit's just a departure from how github works to date.00:19
jlkand it's noisy. Setting status doesn't generate emails, adding a review does00:20
mordredI mean - _also_ dropping a status onto the commit is a way of saying "this commit has been tested" - and it is tru that that commit will have been tested no matter which PR it might be included in00:20
jlkyeah00:21
jlkI proposed doing status + review00:22
jlkand using review as the trigger/requirement00:22
mordredjlk: any thought to just abusing PR tags like ansible does with ansibot? we could also have zuul clear previous vote-tags when someone uploads new patches to a PR (since the reviews don't auto-unset)00:23
* mordred is just saying words now - please feel free to ignore if they are not useful words00:24
jlkTags requires that consumers of the service pre-create the tags, or grant our integration permission to create the tags00:25
mordredah. gotcha00:25
jlkdownside of tags and reviews00:25
jlkthey don't get reset when the pr changes (new code uploaded)00:25
jlkso really, I think we still have to use status as a requirement, or that the positive review was from after the pr head was last changed00:26
jlkif zuul happened to be down when the head changed, or if the hook got dropped somehow, I don't want zuul to be relying on stale data00:26
mordred++00:28
jlk(not even going into how hard this is because each commit can have _multiple_ statuses from multiple providers, and we need a way to scope it down to _which_ status is required)00:28
*** jamielennox|away is now known as jamielennox00:37
*** harlowja has joined #zuul00:52
*** saneax is now known as saneax-_-|AFK01:33
*** adam_g_ has joined #zuul02:40
*** Cibo has quit IRC02:41
*** adam_g has quit IRC02:41
*** saneax-_-|AFK has quit IRC02:41
*** jesusaur has quit IRC02:41
*** rcarrillocruz has quit IRC02:41
*** jamielennox has quit IRC02:41
*** adam_g_ is now known as adam_g02:41
*** Cibo has joined #zuul02:49
*** rcarrillocruz has joined #zuul02:50
*** jesusaur has joined #zuul02:51
*** saneax-_-|AFK has joined #zuul03:10
*** jamielennox|away has joined #zuul03:12
*** jamielennox|away is now known as jamielennox03:12
*** bhavik1 has joined #zuul05:22
*** saneax-_-|AFK is now known as saneax05:24
*** bhavik1 has quit IRC05:29
*** abregman has joined #zuul06:31
*** hashar has joined #zuul07:23
*** isaacb has joined #zuul07:36
*** isaacb has quit IRC08:01
*** hashar is now known as hasharAway08:28
*** openstackgerrit has quit IRC08:33
*** abregman is now known as abregman|mtg08:39
*** isaacb has joined #zuul08:52
*** isaacb has quit IRC08:54
*** isaacb has joined #zuul08:55
*** hasharAway is now known as hashar09:14
*** abregman|mtg is now known as abregman09:27
*** isaacb has quit IRC10:29
*** isaacb has joined #zuul11:31
*** isaacb has quit IRC11:43
*** isaacb has joined #zuul12:42
*** saneax is now known as saneax-_-|AFK12:49
*** hashar has quit IRC13:25
*** hashar has joined #zuul13:25
*** isaacb has quit IRC13:46
*** saneax-_-|AFK is now known as saneax13:47
*** isaacb has joined #zuul13:50
*** isaacb has quit IRC13:51
*** openstackgerrit has joined #zuul14:11
openstackgerritLenny Verkhovsky proposed openstack-infra/nodepool: Fixed typo in info msg  https://review.openstack.org/41843514:11
*** saneax is now known as saneax-_-|AFK14:46
openstackgerritMerged openstack-infra/nodepool: Fixed typo in info msg  https://review.openstack.org/41843514:54
*** bhavik1 has joined #zuul15:14
*** bhavik1 has quit IRC15:19
*** abregman has quit IRC15:48
*** isaacb has joined #zuul15:57
*** isaacb_ has joined #zuul16:24
*** isaacb has quit IRC16:28
*** hashar is now known as hasharAway17:03
openstackgerritJames E. Blair proposed openstack-infra/zuul: Add nodepool integration test script  https://review.openstack.org/42228818:07
*** Shuo has quit IRC18:17
*** isaacb_ has quit IRC18:29
openstackgerritJames E. Blair proposed openstack-infra/zuul: Separate driver interfaces and make abstract  https://review.openstack.org/41855418:36
openstackgerritJames E. Blair proposed openstack-infra/zuul: Re-enable zuultrigger test  https://review.openstack.org/40884818:36
openstackgerritJames E. Blair proposed openstack-infra/zuul: Reorganize connections into drivers  https://review.openstack.org/40884918:36
openstackgerritJames E. Blair proposed openstack-infra/zuul: Add Drivers to documentation  https://review.openstack.org/42280418:36
jeblairjamielennox, jlk, SpamapS, jhesketh, mordred: ^ you may be interested in that stack18:37
jeblairthe documentation change is the only new change, the others are rebases of existing changes to fix a merge conflict18:38
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool: Fix for launched node counting  https://review.openstack.org/42280718:39
SpamapSmmmmmm driver fixes18:40
jeblairclarkb, mordred: should i hold merging the new nodepool launcher stuff from Shrews (421485) for reviews from you or proceed with merges?18:42
openstackgerritJames E. Blair proposed openstack-infra/zuul: Add nodepool integration test script  https://review.openstack.org/42228818:43
jeblairShrews: 422283 and child warrant your attention when you have a moment (not urgent)18:44
clarkbI'd like to read it, I can do that now18:45
Shrewsjeblair: this statement from your spec is a bit hand-wavey: "Nodepool will then decide whether the nodes should be returned to the pool, rebuilt, or deleted according to the type of node and current demand."18:45
Shrewsjeblair: i'm not sure how to determine the return-vs-delete aspect18:46
Shrewsor rebuilt, i guess18:46
jeblairShrews: ah, it was meant to be a fairly forward-thinking statement.  currently, we always delete a used node, but we'd like to support 'nova rebuild' in the future.  and maybe even do other things to nodes after zuul is done with them.  but to keep focus for now, i think we should aim for parity with the current functionality and ignore rebuild for now.  so every 'used' node should be deleted.18:49
jeblairShrews: however, zuul *can* return nodes to us that are not used.18:50
jeblairShrews: so i think every 'ready' node should be put back in the pool for potential re-assignment.18:50
Shrewsjeblair: ok. that definitely simplifies things for the moment18:51
jeblairShrews: (also, 'in-use' should be treated as 'used'.  if we get an 'in-use' node back, it probably means zuul died)18:51
Shrewsjeblair: in-use + unlocked, right?18:52
jeblairShrews: right18:52
Shrewsk18:52
Shrewsjeblair: why do i get "DIB_RELEASE not set correctly" when i run the builder with your --fake option?19:00
*** hasharAway has quit IRC19:01
Shrewsi suspect my nodepool.yaml is b0rked19:01
Shrews  - name: devstack-trusty19:02
Shrews    rebuild-age: 36019:02
Shrews    elements:19:02
Shrews      - ubuntu19:02
Shrews    release: trusty19:02
Shrewsbut IIRC, that worked fine under the real dib19:02
clarkbShrews: is there a traceback? usually I think problems like that have been related to yaml typign issues when trying to emit things to the env which had to be strings19:04
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool: Fix for launched node counting  https://review.openstack.org/42280719:04
Shrewsclarkb: nope, no tb19:05
jeblairyeah, hrm, that looks good to me19:06
Shrewsoh, fake requires it to be 2119:06
jeblairi did just realize that due to a .gitignore, 422284 is missing the nodepool.yaml i wrote19:06
jeblairoh19:06
jeblairyeah, the one i wrote has that19:06
openstackgerritJames E. Blair proposed openstack-infra/nodepool: Add files for zuul-nodepool integration test  https://review.openstack.org/42228419:07
jeblairthat might be why the daemon didn't start up in the integration test :)19:08
Shrewsit should start, but it will just keep complaining and attempting to build19:09
jeblairShrews: i meant the missing file19:09
Shrewsoh19:09
jeblairfixed in latest ps ^19:09
Shrewsjeblair: lgtm now19:11
Shrewsjeblair: also, 422807 had an extraneous : causing failure. removed it19:13
jeblairwhoops19:13
clarkbok I reviewed 421485, left some comments and a +2, will let you decide if worth addressing anything before approving19:15
jeblairclarkb: ++.  i responded with feedback on those.19:20
Shrewsclarkb: thx. i think you're correct on the imageAvailable comment. i'll make the next review change that to query ZK for the list of actually uploaded and ready images.19:23
*** isaacb_ has joined #zuul19:24
Shrewsbecause we can't assume the image is actually available, even if it *is* listed in the config19:24
* Shrews slams head against wall in repentance19:25
jeblairi mean, we can assume... but.... :)19:28
*** openstackgerrit has quit IRC19:33
Shrewsoh for crying out loud... another stray :19:37
* Shrews should just give up on today19:37
*** openstackgerrit has joined #zuul19:37
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool: Fix for launched node counting  https://review.openstack.org/42280719:38
* jlk opens up driver change to look at19:42
jlkjeblair: I meant to ask. That erroneous comment in tests I found yesterday, do you want that fixed on master or the v3 branch?19:42
jlk(or both)19:42
jeblairjlk: let's do both (we have and will do occasional master -> v3 merges, but 2 changes sounds simpler here)19:45
jlkcan do!19:45
*** isaacb_ has quit IRC20:09
openstackgerritDavid Shrewsbury proposed openstack-infra/nodepool: Query ZooKeeper to determine image availability  https://review.openstack.org/42285720:31
Shrewsclarkb: jeblair: that turned out to be much simpler than i expected ^^^20:31
*** hashar has joined #zuul20:35
*** hashar has quit IRC20:35
jeblair++20:42
*** piccobit has joined #zuul21:02
piccobithi there, I've set up a Zuul test system which works fine with Jenkins Freestyle projects, but now I've tried using Jenkins Pipelines and they aren't visible to Zuul. Any hints?21:05
jeblairpiccobit: i've heard that jenkins pipelines are a new construct which is not seen as a job by the gearman plugin for jenkins that zuul uses, so i'm not sure there's anything easy that can be done.  most of us are focused on working on building zuul v3 right now which uses ansible rather than jenkins.21:30
*** piccobit has quit IRC21:49
openstackgerritJesse Keating proposed openstack-infra/zuul: Correct comments in requirement test cases  https://review.openstack.org/42289922:34
openstackgerritJesse Keating proposed openstack-infra/zuul: Correct comments in requirement test cases  https://review.openstack.org/42290022:38
*** piccobit has joined #zuul23:37
*** piccobit has quit IRC23:38
*** piccobit has joined #zuul23:43

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