November 8, 2014 
< | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | >
November 8, 2014 [01:22:27] <Camel> is there a good way in gerrit to associate a set of changes in different projects?[01:23:44] *** pedroalvarez has joined #gerrit[01:23:58] <Camel> at $DAYJOB, commits are in JIRA-###: Subject [{1..i}/i] format, so jenkins + gerrit trigger is kind of useless in many cases[01:35:11] *** teran has joined #gerrit[01:58:16] <pedahzur> Camel: Why is jenkins + gerrit trigger useless (sorry, not following train of thought)[02:02:36] <Camel> When people make interdependent changes, one part will not build on its own[02:03:37] <Camel> I am searching for a way to group the changes, perhaps in a way stream-events can publish[02:04:18] <Camel> Ideally the gerrit-trigger plugin would[02:04:45] <Camel> Make the association, but it would likely require doing expensive queries[02:16:19] *** wenlock has quit IRC[02:22:02] *** sbadia has quit IRC[02:22:11] *** jhuntley has quit IRC[02:22:13] *** freebeerz has quit IRC[02:22:18] *** jhuntley has joined #gerrit[02:22:43] *** sbadia has joined #gerrit[02:22:54] *** freebeerz has joined #gerrit[02:24:16] <pedahzur> Camel: Yeah, gerrit trigger is pretty much a build-each-review paradigm. I know there is a way to have "related changes" in Gerrit, but that doesn't do any build grouping.[02:24:55] *** teran has quit IRC[02:25:18] <Camel> could a gerrit plugin do something like that, though?[02:25:23] *** teran has joined #gerrit[02:27:00] <pedahzur> Camel: Possibly, but like you say, it would require expensive queries. Basically looking through each and every commit every time it gets a commit to find other reviews with certain tags, ticket numbers, etc.[02:30:37] <Camel> well it'd only need to consider open changes from the same author, so it shouldn't be too expensive to do[02:30:46] *** teran_ has joined #gerrit[02:31:16] <Camel> but doing that across a network is pretty expensive[02:32:58] *** teran has quit IRC[02:47:59] *** teran_ has quit IRC[03:36:40] <pedahzur> Well, if it was a gerrit plugin, it could query locally, then delivery some kind of message in the notification stream.[03:36:58] *** Vampire0_ has joined #gerrit[03:37:48] <pedahzur> Camel: ^^[03:40:34] *** Vampire0 has quit IRC[08:22:29] *** jhuntley has quit IRC[08:27:53] *** pedahzur has quit IRC[08:33:06] *** qchris has joined #gerrit[11:04:18] *** Vampire0_ is now known as Vampire0[11:47:03] *** dougsland has quit IRC[11:58:41] *** teran has joined #gerrit[12:41:17] *** teran has quit IRC[12:43:33] *** teran has joined #gerrit[13:02:46] *** teran has quit IRC[13:09:31] *** teran has joined #gerrit[13:13:31] *** teran has quit IRC[13:46:49] *** qchris is now known as qchris_away[14:37:35] *** teran has joined #gerrit[15:03:32] *** teran has quit IRC[15:04:56] <jkt> Camel: you're looking for openstack's zuul[17:40:19] *** jhuntley has joined #gerrit[18:11:25] *** patrickg has joined #gerrit[18:20:19] *** teran has joined #gerrit[19:20:13] *** teran has quit IRC[19:54:26] *** qchris_away is now known as qchris[23:59:33] *** denizt_ has joined #gerrit[23:59:33] *** denizt has joined #gerrit