Monday, 2017-05-08

*** jamielennox is now known as jamielennox|away01:50
*** dkranz_ has quit IRC01:58
*** jamielennox|away is now known as jamielennox02:04
*** jroll has quit IRC06:19
*** jrollen has joined #zuul06:21
*** isaacb has joined #zuul06:25
*** smyers has quit IRC09:04
*** bhavik1 has joined #zuul09:07
*** smyers has joined #zuul09:15
*** bhavik1 has quit IRC11:03
*** jkilpatr has joined #zuul12:00
*** jkilpatr has quit IRC12:12
*** dkranz_ has joined #zuul13:23
openstackgerritJames E. Blair proposed openstack-infra/zuul feature/zuulv3: WIP: add configuration documentation  https://review.openstack.org/46332813:48
*** isaacb has quit IRC13:58
*** rcarrill1 is now known as rcarrillocruz14:07
openstackgerritTobias Henkel proposed openstack-infra/nodepool feature/zuulv3: Add max-ready-age to label config  https://review.openstack.org/46333814:15
*** jrollen is now known as jroll14:18
Shrewsmordred: any reason why i can't make your websocket stuff py 3.5 and forward friendly?14:47
Shrews"async def/await" vs. using "@asyncio.coroutine/yield from"14:48
mordredShrews: yah - I'd love that14:49
mordredShrews: I think I was just doing that from originally when the zuul pep8 job was still running on py214:49
mordredShrews: which meant it died on syntax error14:49
mordredShrews: but we run pep8 on py3 now, so we should be fine to go ahead and use the real stuff14:50
Shrewscool14:50
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: WIP: Add web-based console log streaming  https://review.openstack.org/46335315:03
Shrewswow, keynotes are still going on15:04
Shrewsmordred: i took your change and rebased it onto the feature/zuulv3 branch ^^^. will work from that one15:11
*** jkilpatr has joined #zuul15:11
*** jhesketh has quit IRC15:14
*** jhesketh has joined #zuul15:15
*** jkilpatr has quit IRC15:22
dmsimardCrazy question, would it be possible from within openstack_functions.py to prevent a job from firing by embedding logic in there ? Context is advanced filtering beyond what zuul currently offers out of the box.15:52
dmsimardi.e, https://github.com/openstack-infra/project-config/blob/master/zuul/openstack_functions.py15:53
*** jkilpatr has joined #zuul15:54
jlkI wonder if you could have it return early with success.15:55
jlkbut I think those functions are used by job definitions, which is called well after a decision to execute a job has been made15:55
jlkout of curiosity, what type of filtering do you find lacking?15:56
dmsimardjlk: arbitrary logic beyond branch/file filtering15:56
dmsimardi.e, a parent job that knows what child jobs to trigger based on it's result15:56
jlkexample?15:56
dmsimardneed to brb15:57
jlkwell15:57
jlkyou can do that within a pipeline, when you say one job depends on another job15:57
jlkbut that I think only works with success results, rather than failure15:57
*** jkilpatr has quit IRC15:59
jeblairdmsimard: what kind of predicate do you want to make?15:59
openstackgerritDavid Shrewsbury proposed openstack-infra/zuul feature/zuulv3: Fix imports for py3  https://review.openstack.org/46335816:01
jeblair(we're dropping support for the custom functions in v3, as all the things we used it for are handled in other ways, and continuing to support that would be... complex,  so i want to make sure we can express what you want)16:01
*** bhavik1 has joined #zuul16:02
dmsimardjeblair: I was discussing with a colleague that some sort of generic filtering to determine if a job should run or not could be nice16:10
dmsimardjeblair: I wrote some pseudocode to explain what I mean: http://paste.openstack.org/raw/609143/16:10
dmsimardjlk: yeah, I know about parent/child relationship16:10
dmsimardjlk: this one parent, depending on the outcome, could trigger one (or many) out of 15 potential child jobs16:11
dmsimardjlk: a hack I'm not happy with is the parent job setting a "witness" or a "flag" file and then firing all 15 jobs and then exit 0 immediately if the flag file is there -- it'd be wasteful if we end up needing to run just 2 or 3 jobs16:12
jlkthis looks like code that would run on the scheduler or executor rather than a booted node, yeah?16:13
dmsimardif the plan is to prevent a job from running in the first place, it would have to run before the job is scheduled (and a node is booted)16:14
dmsimardI'm not intimately familiar with Zuul's internals so I don't know where something like this would be running16:14
jlknod. We've spent a fair amount of time trying to protect the system from arbitrary user submitted code execution, so this would have to be protected as well.16:15
dmsimardThat's fair, perhaps it could really translate to (in JJB terms) a builder that would run on the executor16:16
jeblairdmsimard: so is this case something like: one job builds up to N packages (but some of those may fail to build but the job will continue), and then one job should run for each package sucessfully built?16:16
dmsimardjeblair: sort of. The real use case is for a RDO "metadata" repository that keeps a registry of every openstack package we have across the different releases. It looks like this: https://github.com/redhat-openstack/rdoinfo/blob/master/rdo.yml16:18
dmsimardIt's largely automated, for example, we will update package versions when there is an upper-constraints update in the requirements repo upstream.16:18
dmsimardSome updates to that repo, since it spans multiple releases (say, newton, ocata and trunk) needs different jobs to be running -- a single commit might contain updates to just one release like it could contain updates to multiple releases16:19
dmsimardSo, you could say, "humans" and have commits only span one release. But, you know, humans :)16:20
jeblairdmsimard: so to generalize, it's more like, jobs should run or not based on the content of the change?16:21
dmsimardjeblair: yeah.16:21
*** bhavik1 has quit IRC16:22
dmsimardjeblair: another thing I was thinking of, is perhaps it should be possible to filter on change labels -- for example, there's "ChangeId", "Depends-On", etc. If I add an arbitrary label, I don't know, "Openstack-Release", maybe I could filter on the values of that field16:23
jlkI thought that the change label thing allowed "extra" keys16:24
dmsimardjlk: yeah maybe this is already possible today, I don't know16:24
jeblairdmsimard: i'd probably stick with having the job exit early if it doesn't need to run -- mostly because even in v2, the custom function handler runs in a very critical section of code and it's not good to slow it down with external dependencies.  but in v3, i wonder if this pattern would work: a really simple stub job which has no nodes and performs the evaluation, and then the real job depends on that.16:25
dmsimardjeblair: yeah in JJB terms, the way I could see things work is to have a builder (with logic in it) and this builder is defined as a filter of the zuul job definition. This builder, since it is a filter, runs on the executor, not on a nodepool node16:26
jlkoh you can do a job that doesn't depend on a node? that'd be useful.16:26
jeblairdmsimard: yeah, a job with no nodes is basically like that16:26
jeblairi didn't anticipate that, but i think they're going to be handy so i'm thinking we should keep that as a possibility.  :)16:27
dmsimardThe problem is in my case there's actually 15 potential different jobs that could be running and firing all 15 if I only end up needing 2 or 3 is incredibly wasteful (spin up, spin down, etc.)16:27
jeblairamusingly, 99% of the tests are jobs with no nodes.  :)16:27
dmsimardRDO doesn't have OSIC-level of capacity :P16:27
jeblairdmsimard: yeah, that's why i think chaining the actual jobs after no-node jobs which perform the eval would help16:28
jeblairit's not a super elegant system though... i'll think about it some more :)16:28
dmsimardsure16:30
jlkI think what jeblair is saying is that you can have one or more "base" jobs that are decision jobs, that use no nodes, and execute right on the zuul system so very little overhead. Your jobs that would consume capacity would depend on those.16:30
jlkso you could make decisions cheaply before spinning up the costly resources.16:30
dmsimardjlk: yeah.16:31
dmsimardthat's the gist of it16:31
jlkjeblair: reading up on canMerge states, looking at the gerrit example. Is that checking votes?16:48
jlkjeblair: Looking at the code, its checking labels for a status of NEED or REJECT16:48
jlkhrm.16:51
jlkNot seeing how a label in the submitRecords can have a 'status' attribute16:51
jlkn/m, found some of the right json docs16:53
jlkright okay, so gerrit is smart enough to tell you whether or not the merge rules have been met. Zuul doesn't necessarily know or care what those rules are, just that gerrit says "good to go".16:54
*** Cibo_ has joined #zuul17:28
*** bhavik1 has joined #zuul17:33
jeblairjlk: yes -- the only smats zuul brings to it is it knows to ignore a category it votes on17:54
*** jkilpatr has joined #zuul17:57
*** bhavik1 has quit IRC18:01
jlkjeblair: okay, I think I've addressed the current feedback, and since there was a number of them I'm going to go ahead and push up a new stack.18:07
adam_ganyone know whats up with the v3 zuul failing changes /w RETRY_LIMIT errors?18:08
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: support github pull request labels  https://review.openstack.org/44451118:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Allow github trigger to match on branches/refs  https://review.openstack.org/44562518:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add cachecontrol to requests to github  https://review.openstack.org/46158718:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Set filter according to PR/Change in URL  https://review.openstack.org/44678218:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add support for requiring github pr head status  https://review.openstack.org/44939018:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Support for dependent pipelines with github  https://review.openstack.org/44529218:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Adds github triggering from status updates  https://review.openstack.org/45384418:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Implement pipeline requirement on github reviews  https://review.openstack.org/45384518:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Configurable SSH access to GitHub  https://review.openstack.org/44403418:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Represent github change ID in status page by PR number  https://review.openstack.org/46071618:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add 'comment' github pull_request event action  https://review.openstack.org/44395918:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Support for github commit status  https://review.openstack.org/44406018:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Better merge message for GitHub pull reqeusts  https://review.openstack.org/44564418:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Test gerrit and github drivers in same tenant  https://review.openstack.org/44825718:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Encapsulate determining the event purpose  https://review.openstack.org/44524218:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Merge pull requests from github reporter  https://review.openstack.org/44446318:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Include exc_info in reporter failure  https://review.openstack.org/46076518:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add support for github enterprise  https://review.openstack.org/44925818:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: GitHub file matching support  https://review.openstack.org/44611318:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Ensure PRs arent rejected for stale negative reviews  https://review.openstack.org/46070018:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add trigger capability on github pr review  https://review.openstack.org/44936518:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Log GitHub API rate limit  https://review.openstack.org/44615018:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Comment on PRs if a remote call to merge a change failed  https://review.openstack.org/46076218:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Actually filter status triggers  https://review.openstack.org/46338518:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Implement github trigger requirement status  https://review.openstack.org/46338618:09
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Implement trigger require/reject-approvals  https://review.openstack.org/46338718:09
*** jkilpatr has quit IRC18:13
*** jkilpatr has joined #zuul18:15
*** Cibo has joined #zuul18:18
*** Cibo_ has quit IRC18:21
jlkd'oh!!! I forgot to pep8 check!18:24
*** jkilpatr has quit IRC18:28
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: support github pull request labels  https://review.openstack.org/44451118:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Allow github trigger to match on branches/refs  https://review.openstack.org/44562518:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add cachecontrol to requests to github  https://review.openstack.org/46158718:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Set filter according to PR/Change in URL  https://review.openstack.org/44678218:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add support for requiring github pr head status  https://review.openstack.org/44939018:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Support for dependent pipelines with github  https://review.openstack.org/44529218:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Implement trigger require/reject-approvals  https://review.openstack.org/46338718:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Adds github triggering from status updates  https://review.openstack.org/45384418:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Implement github trigger requirement status  https://review.openstack.org/46338618:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Implement pipeline requirement on github reviews  https://review.openstack.org/45384518:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Actually filter status triggers  https://review.openstack.org/46338518:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Represent github change ID in status page by PR number  https://review.openstack.org/46071618:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Better merge message for GitHub pull reqeusts  https://review.openstack.org/44564418:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Test gerrit and github drivers in same tenant  https://review.openstack.org/44825718:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Encapsulate determining the event purpose  https://review.openstack.org/44524218:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Include exc_info in reporter failure  https://review.openstack.org/46076518:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add support for github enterprise  https://review.openstack.org/44925818:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: GitHub file matching support  https://review.openstack.org/44611318:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Ensure PRs arent rejected for stale negative reviews  https://review.openstack.org/46070018:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Log GitHub API rate limit  https://review.openstack.org/44615018:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add trigger capability on github pr review  https://review.openstack.org/44936518:33
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Comment on PRs if a remote call to merge a change failed  https://review.openstack.org/46076218:33
*** jkilpatr has joined #zuul18:34
*** jkilpatr has quit IRC18:48
Shrewsadam_g: not sure. nodepool seems to be working properly, so i'm guessing something with zuul itself19:17
Shrewsadam_g: jeblair: pabelanger: No space left on device  <--- zuulv3-dev.o.o19:18
Shrewson /tmp, it would seem, though df reports 93% full19:19
clarkbShrews: what about inodes?19:19
Shrewsclarkb: ah yeah. 100%19:20
*** jkilpatr has joined #zuul19:33
jeblairShrews: neat, what filled it up?20:05
*** jkilpatr has quit IRC20:07
*** Cibo has quit IRC20:09
pabelangerHmm, I can look20:10
pabelangerDAEMON_ARGS="--keep-jobdir"20:10
jeblairoh that'll do it20:10
jeblairprobably we can drop that now?20:11
pabelangerYa, I can comment out now20:11
pabelangerjeblair: I think so20:11
*** jkilpatr has joined #zuul20:12
pabelangerk, commented out, we'll need to restart zuul-executor20:13
pabelangerzuul-executor restarted20:15
pabelangerany objections to remove /tmp zuul files?20:16
jeblairpabelanger: please do20:17
pabelangerokay, purging /tmp20:20
pabelangerokay, tmp purged20:25
jlkOh dammit. I have a test that fails when run with a bunch of other tests, but passes if ran by itself.20:30
*** jkilpatr has quit IRC20:32
*** dkranz_ has quit IRC20:48
*** jkilpatr has joined #zuul21:01
jamielennoxShrews: quick question, have you thought about the streaming protocol emitting json, or <other serializer>?21:13
jamielennoxI'm thinking about rendering this on a web page and i'm probably going to want to seperate timestamps and message and other bits into different elements, and let you do things like hide timestamps21:14
*** jkilpatr has quit IRC21:14
jamielennoxit's a fairly easy protocol, i could always parse it client side, but is there a standard for websocket messages that would split that up?21:14
clarkbjamielennox: if you do do that, my strong suggestion is use an existing format from something like systemd or logstash so that its consumable in other locations with little owrk21:15
clarkb(systemd has json output, logstash is largly json)21:15
clarkbsorry journald21:16
clarkbon the flip side to that wouldn't that make using finger directly a bit more of a pain?21:17
clarkbyou'd have to pass it hrough some parser locally too21:17
clarkb?21:17
Shrewsjamielennox: i have not, but i'm still playing catchup with mordred and jeblair who have thought waaay longer about this than myself21:17
Shrewsbut if we are talking about supporting streaming different logs (which we are), then it would be rather difficult to support all of the various timestamp/message formats, would it not? or am I misunderstanding21:18
clarkbShrews: thats one of the problems we have with logstash, its doable but you hva eto do things like parse 9 different timestamp formats21:19
Shrews*vomit*21:19
jamielennoxclarkb: yea, i don't mind which, and i'm not sure where you'd insert this - i don't think you need to actually change the syslog format, just the thing transporting it to the client21:20
jamielennoxShrews: right, so as you add more files you will need to encode additional stuff right - like which file did this line come from21:20
Shrewsi suspect no one has really thought beyond duplicating jenkins log streaming, tbh21:21
Shrewsat least for an initial version21:21
jeblairwell, one wrinkle is that we want to have the ability to fetch arbitrary logs (like, stream the nova log).  even if we adopted a stricter format for the console log, other logs will have their own format21:23
jamielennoxyea, and i'm not sure where exactly to implement this sort of checking. so with the streamer would we still expect people to telnet and see regular logs?21:23
jamielennoxjeblair: yea, i'm not thinking parse the syslogs or anything, but zuul-console does timestamp + ' | ' + msg today21:24
jamielennoxjust thinking about {'ts': timestamp, 'msg': msg}21:25
jamielennoxso we could add filename and other things later21:25
jeblairmaybe the parsing could happen inside the websocket streamer, so it's unparsed until then, then part of the websocket protocol for this is json?21:26
jamielennoxas you say as we add more things i would expect from the client side to be able to hide timestamps, or only show the streaming logs from X, Y, Z files21:26
jamielennoxjeblair: yea, i'm not coming at this with an answer, just trying to think of what i would ideally want to see as a client and what information you need to make that happen21:27
jamielennoxas it is today i can easily parse out timestamp, just wondering what other information needs to be conveyed in future21:28
jeblairyeah, it's a good suggestion.  i'll continue to mull it over as i recover from jetlag.  :)21:28
Shrewsi'm sort of leaning towards the parsing happening at the client, but I, too, will mull this over a bit21:29
jamielennoxoh, and like anything that is an error message from the actual streamer/telnet would be good to be distinguished from a regular message21:29
jamielennox'err': 'Connection Failed'21:29
*** jkilpatr has joined #zuul22:33
*** jkilpatr has quit IRC22:44
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Allow github trigger to match on branches/refs  https://review.openstack.org/44562523:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add github reporter status_url config option  https://review.openstack.org/44979423:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add cachecontrol to requests to github  https://review.openstack.org/46158723:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add support for requiring github pr head status  https://review.openstack.org/44939023:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Support for github commit status  https://review.openstack.org/44406023:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Merge pull requests from github reporter  https://review.openstack.org/44446323:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Include exc_info in reporter failure  https://review.openstack.org/46076523:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add support for github enterprise  https://review.openstack.org/44925823:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Log GitHub API rate limit  https://review.openstack.org/44615023:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Ensure PRs arent rejected for stale negative reviews  https://review.openstack.org/46070023:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Comment on PRs if a remote call to merge a change failed  https://review.openstack.org/46076223:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: support github pull request labels  https://review.openstack.org/44451123:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Set filter according to PR/Change in URL  https://review.openstack.org/44678223:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Support for dependent pipelines with github  https://review.openstack.org/44529223:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Adds github triggering from status updates  https://review.openstack.org/45384423:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Implement trigger require/reject-approvals  https://review.openstack.org/46338723:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Implement pipeline requirement on github reviews  https://review.openstack.org/45384523:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Implement github trigger requirement status  https://review.openstack.org/46338623:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Actually filter status triggers  https://review.openstack.org/46338523:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Represent github change ID in status page by PR number  https://review.openstack.org/46071623:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Better merge message for GitHub pull reqeusts  https://review.openstack.org/44564423:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Test gerrit and github drivers in same tenant  https://review.openstack.org/44825723:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Encapsulate determining the event purpose  https://review.openstack.org/44524223:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: GitHub file matching support  https://review.openstack.org/44611323:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Add trigger capability on github pr review  https://review.openstack.org/44936523:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Use integration_id with github  https://review.openstack.org/46342023:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Create github client each time it's called.  https://review.openstack.org/46342123:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Decode JSON body once for requests  https://review.openstack.org/46342223:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Refactor integration key loading to always load  https://review.openstack.org/46342323:47
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Save installation ids to a cache and fetch them per project  https://review.openstack.org/46342423:48
openstackgerritJesse Keating proposed openstack-infra/zuul feature/zuulv3: Catch integration key file not found in zuul  https://review.openstack.org/46342523:48

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