15:00:28 #startmeeting third-party 15:00:29 Meeting started Mon Dec 12 15:00:28 2016 UTC and is due to finish in 60 minutes. The chair is lennyb. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:30 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:32 The meeting name has been set to 'third_party' 15:00:39 Hello 15:00:51 o/ 15:01:10 hi mmedvede, how are you? 15:02:27 I am good lennyb 15:03:18 anything you want to discuss? 15:03:58 hello, lennyb mmedvede.:) 15:04:12 lennyb: nope :), just here to help if anyone has questions I can answer 15:04:29 I have a question. 15:04:34 hello watanabe_isao, how are you? Is there anything to want to ask/discuss/share? 15:04:48 watanabe_isao, go ahead 15:05:19 What do I need to do to add another hook into devstack_gate? 15:05:33 I mean the necessary process 15:06:05 watanabe_isao: are you asking about how to land a patch that enables more hooks in d-g? 15:06:19 mmedvede, yes. 15:06:41 correctly I am doing this: https://review.openstack.org/#/c/368554/ 15:07:13 I saw several attempts to add hooks in d-g (mainly because post_test_hook was not doing what it seemed it should be) 15:07:15 But seems like just post a patch is not enough. 15:07:46 mmedvede, Ooo.. 15:08:30 watanabe_isao: in the past, the answer was not to add more hooks, as the functionality can be realized outside d-g 15:08:38 * mmedvede checks the linked patch 15:08:46 watanabe_isao, why can't you use clark's suggestion? 15:10:07 lennyb, I don't quit get what should I do with the job by the suggestion. 15:11:19 watanabe_isao: there is a point in your CI where you call devstack-gate script, correct? So clarkb suggest you add your cleanup code _after_ you call the d-g script 15:11:30 good morning 15:11:51 watanabe_isao, as I understand you need to run some scripts after job, so why cant you do it in the CI? 15:12:07 asselin, it's 17:00pm :) 15:12:20 asselin, hi, thanks for joinng 15:12:58 :) 15:14:32 watanabe_isao, we are for example cleaning MACs from ovs after the jobs is finished. 15:15:02 lennyb, because after post_test_hook the job failed and stop to run any more, in my understanding. BTW, I did not found a cleanup hook 15:15:34 good evening asselin, it is 0:15 here.:) 15:15:57 that's very very early morning for you :p 15:16:05 watanabe_isao, you can add it in publisher section that is always running 15:16:25 ++ for adding in publisher of jenkins (if you do use jenkins) 15:16:28 lennyb, yes 15:16:49 you can configure publisher to always run, no matter if the job has failed or not 15:17:15 lennyb, do you have any example about that? I mean run some script at publisher. 15:17:15 I thought there were also post-build tasks....is that the same as publisher? 15:18:24 watanabe_isao, #link https://github.com/openstack/networking-mlnx it's our CI 15:18:42 watanabe_isao, ops, wait 15:18:50 I think publishers interpreted as post-build tasks by jjb 15:19:40 watanabe_isao, #link https://github.com/Mellanox/mlnx-project-config 15:21:12 watanabe_isao, publishers #link https://github.com/Mellanox/mlnx-project-config/blob/68d1b3b4492409522b4ee82745525ef0a5a461e9/jenkins/jobs/macros.yaml#L30 15:22:58 watanabe_isao, this is for JJB and Common CI solution by dear asselin 15:23:09 lennyb, thank you very much. I have tried once to run script at publisher, but it failed. 15:23:40 lennyb, I'll try this. 15:24:00 watanabe_isao, good luck. 15:24:21 Any other issues/questions/wishes for a New Year to come? 15:27:48 If there is nothing else I propose to close this meeting. 15:28:18 +1 15:28:32 night-night lennyb mmedvede asselin.:) 15:28:39 watanabe_isao, asselin,mmedvede thanks. See you next week 15:28:43 :) morning for me too 15:28:48 bye 15:29:00 see you 15:29:05 #endmeeting