[06:52:33] <wikibugs>	 10Phabricator, 06Project-Admins, 06Developer-Relations (Jul-Sep-2016), 07RfC: Abandon (or at least strongly simplify) project creation policy - https://phabricator.wikimedia.org/T139210#2631699 (10Qgil) I would still keep our simple process to request #project-admins permissions. Requesting this once by po...
[12:01:02] <wikibugs>	 10Phabricator, 06Project-Admins, 06Developer-Relations (Jul-Sep-2016), 07RfC: Abandon (or at least strongly simplify) project creation policy - https://phabricator.wikimedia.org/T139210#2632519 (10Aklapper) That makes sense, but regarding #1: Does that mean we hand out permissions to everybody and anybody...
[15:18:43] <paladox>	 qchris_ hi, i got another change upstream merged https://gerrit-review.googlesource.com/#/c/86011/ :)
[15:31:22] <paladox>	 qchris_ My other patch has also been merged https://gerrit-review.googlesource.com/#/c/85340/ :) yay
[18:42:52] <wikibugs>	 10Phabricator, 06Project-Admins, 06Developer-Relations (Jul-Sep-2016), 07RfC: Abandon (or at least strongly simplify) project creation policy - https://phabricator.wikimedia.org/T139210#2634134 (10mmodell) >>! In T139210#2630745, @Aklapper wrote: > Regarding the permissions tied to #Project-Admins and its...
[18:52:07] <ottomata>	 hiyaa, ok i'm ready to try to make diffusion work with jenkins
[18:52:13] <ottomata>	 looking for some documentation
[18:53:14] <ottomata>	 is there a way i can configure the command that is run to launch a test job?
[18:57:13] <ottomata>	 twentyafterfour: ^
[18:58:04] <paladox>	 ottomata we use https://phabricator.wikimedia.org/harbormaster/
[18:58:11] <paladox>	 for jenkins on differential :)
[18:58:15] <paladox>	 and hi
[18:58:59] <ottomata>	 hiya
[18:59:01] <ottomata>	 cool!
[18:59:04] <ottomata>	 yeah browsing around here
[18:59:15] <ottomata>	 can i configure my repo's test jobs to run a specific command for tests?
[18:59:46] <paladox>	 Currently i doint think that is supported
[18:59:51] <ottomata>	 oh
[18:59:51] <ottomata>	 hm
[18:59:56] <ottomata>	 i see my repo has been given the tag https://phabricator.wikimedia.org/tag/meta-ci-jessie/
[19:00:04] <ottomata>	 so, builds are trying to happen, but failing
[19:00:11] <ottomata>	 i guess i have to make npm test just do all the things
[19:00:12] <ottomata>	 ok
[19:00:35] <twentyafterfour>	 ottomata: what do you need to change about the test command?  The goal is to use standard test entry points.
[19:01:03] <ottomata>	 well, i need to install kafka for my tess
[19:01:04] <ottomata>	 tests
[19:01:06] <paladox>	 brb
[19:01:23] <twentyafterfour>	 yeah I saw that
[19:01:30] <ottomata>	 its done like this for change-prop and travis
[19:01:30] <ottomata>	 https://github.com/wikimedia/change-propagation/blob/master/.travis.yml#L11
[19:01:38] <ottomata>	 so, i could move thatinto a helper .sh script
[19:01:45] <ottomata>	 and just have  npm test do all the things
[19:01:51] <ottomata>	 which i guess is fine
[19:02:02] <twentyafterfour>	 I was looking at the way travis does it. Would be cool to support something like the .travis.yml
[19:02:03] <ottomata>	 but it means that npm test always has to run on a clean VM
[19:02:07] <ottomata>	 which is not true when I run tests locally
[19:02:11] <ottomata>	 that's fine, cause I can work around it
[19:02:22] <ottomata>	 yeah, something to let you configure the test build
[19:03:30] <ottomata>	 twentyafterfour:  should I just make npm test do all that stuff for now?
[19:03:41] <twentyafterfour>	 yeah that's probably easiest...
[19:04:06] <ottomata>	 k will try it
[19:04:10] <ottomata>	 as a differential.... :)
[19:05:21] <twentyafterfour>	 fwiw, .arclint and .arcunit config files allow you to infinitely customize the CI build process, however, I haven't been able to make them work properly on nodepool
[19:06:15] <ottomata>	 oh hm
[19:10:04] <ottomata>	 yeah that would be cool
[19:24:58] <ottomata>	 twentyafterfour:  not sure what is happening here
[19:24:59] <ottomata>	 https://integration.wikimedia.org/ci/job/phabricator-jessie-diffs/103/console
[19:25:05] <ottomata>	 it looks like its missing a build step
[19:25:47] <ottomata>	 hmm, agh, outta battery, gotta run home
[19:25:48] <ottomata>	 back in a bit
[19:26:01] <ottomata>	 am trying to build this differ https://phabricator.wikimedia.org/D348
[19:29:49] <mutante>	 does grrrit-wm require kubernetes?
[19:30:08] <mutante>	 could it technically be moved to the prod gerrit host?
[19:30:15] <mutante>	 (then we could auto-restart it when gerrit restarts)
[19:30:46] <twentyafterfour>	 mutante: probably could run anywhere
[19:31:02] <twentyafterfour>	 it just needs access to gerrit's ssh port right?
[19:31:08] <paladox>	 Yep using the npm run-script start
[19:31:12] <mutante>	 hmm.. i'm thinking if running it in prod makes sense or not
[19:31:21] <mutante>	 but just because that makes it possible to auto-restart it
[19:31:34] <mutante>	 and not have to manually do it
[19:32:06] <mutante>	 access to it would then be combined with the gerrit admin group