14:00:48 <hhorak> #startmeeting SCLo SIG sync-up (2017-02-21)
14:00:48 <centbot> Meeting started Tue Feb 21 14:00:48 2017 UTC.  The chair is hhorak. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:00:48 <centbot> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:00:52 <hhorak> #meetingname sclo-sig-syncup
14:00:52 <centbot> The meeting name has been set to 'sclo-sig-syncup'
14:00:55 <hhorak> hello
14:01:01 <jstanek> hey there
14:01:36 <pvalena> hi
14:03:55 <hhorak> First thing first, thanks to RemiFedora for updating https://wiki.centos.org/SpecialInterestGroup/SCLo/CollectionsList
14:04:09 <hhorak> #action hhorak to take a look and verify ^
14:05:15 <RemiFedora> I also add a link to upstream page, so with upstream list of all "rh" scl with date (published / retired)
14:05:42 <pvalena> from my brief look I have some questions about the comments and deps- in case of rh-ror42: how did that happen? I do not know of such issues :)
14:06:04 <RemiFedora> sadly this list doesn't use the scl name (e.g. "MySql 5.7" vs "rh-mysql57")
14:06:52 <hhorak> RemiFedora: good idea
14:08:18 <hhorak> pvalena: that's some older comment probably, checking ci status now
14:08:46 <pvalena> it should depend only on nodejs4 :)
14:11:00 <hhorak> pvalena: IIRC first builds depended on nodejs010, which depended on v8314..
14:11:05 <jirkade> gwd: last time we discussed it you said we'd need to figure out the details, but I didn't have time to discuss it any further at that time
14:11:08 <hhorak> pvalena: but we can fix this as well..
14:11:45 <pvalena> great :)
14:12:24 <jirkade> gwd: I guess it's about tags, branches, and similar stuff... no idea what building a package for virtsig is all about
14:13:26 * hhorak thinking about how to share CI status on the wiki page.. I guess we can leverage https://wiki.jenkins-ci.org/display/JENKINS/Embeddable+Build+Status+Plugin
14:15:31 <jirkade> gwd: "I think then we just need to sort out the technicalities" is what you said
14:17:48 * hhorak cannot find plugins list for ci.. will try later..
14:18:15 <hhorak> anyway, I think I never talked publicly about changes in testing that happened some time ago..
14:18:22 <hhorak> we now test not only CBS tags: https://ci.centos.org/view/SCLo-pkgs-cbs/
14:18:40 <hhorak> but also packages on mirror and buildlogs, separately: https://ci.centos.org/view/SCLo-pkg-mirror/
14:19:26 <hhorak> you might see some red buttons, it is sometimes only caused by failing cico (no available machine), but sometimes it can be real issue
14:19:49 <hhorak> if anybody would like to help with debugging this (if it is a real issue), please, do :)
14:20:02 * hhorak fails to find time for it...
14:23:02 <hhorak> ok, anything else anybody?
14:26:04 <hhorak> No issues with SCLo? I wonder :)
14:28:07 <hhorak> Actually one more thing on my end, if bstinson is around...
14:28:50 <bstinson> hhorak: hi, what can i help with?
14:31:01 <hhorak> bstinson: Hi, I'm thinking about changing the cico call settings, currently we try to get a node every minute 5 times.. but sometimes we don't get any and the test fails.. maybe doing it every 3m would be more successful? or any other recommendations?
14:31:22 <hhorak> bstinson: also thinking about not being too tough for CI with our tests..
14:32:57 <bstinson> you might try to match the current rate limit (5 machines/5 minutes)
14:33:10 <bstinson> hhorak: what do you mean by 'too tough'?
14:33:57 <hhorak> bstinson: I'm just thinking about number of tests we have, so it may have some impact on whole ci..
14:34:25 <hhorak> so just want to be conscious for others..
14:35:42 <bstinson> let's not limit your testing though, we want more not less! we can probably discuss having you folks move to a different workspace instead of slave01
14:39:46 <hhorak> bstinson: maybe it would just be enough to re-test if the test failed (after few hours).. I'll take a look whether there is some option for that in the jenkins..
14:40:55 <hhorak> bstinson: anyway, if already talking to you -- do we have a jenkins plugin list available somewhere? I was looking for https://wiki.jenkins-ci.org/display/JENKINS/Embeddable+Build+Status+Plugin but don't know how to figure out whether it is available or not..
14:42:20 <bstinson> hhorak, happy to work together 1:1 to do some of the scheduling let me see if i can send you some suggestions
14:42:28 <Dominic> hhorak: the build status plugin's there, click a job and there's an Embeddable Build Status link on the left
14:42:46 <bstinson> https://ci.centos.org/job/SCLo-container-mysql-rh/badge/
14:42:48 <bstinson> ^for example
14:43:35 <hhorak> bstinson: Dominic: aaah, thanks, I was looking at wrong place... :)
14:43:40 <hhorak> awesome
14:44:31 <hhorak> bstinson: ok, any suggestions welcome :)
14:45:55 <hhorak> bstinson: just found "Retry build after failure" between build steps, I might try that one..
14:46:32 <hguemar> Evolution: if you need the aarch64 node, you can scratch it, I can postpone openstack ocata testing to a later time
14:47:03 <bstinson> hhorak: can you remind me where your jjb templates are?
14:47:13 <_ari_> kbsingh: ping
14:47:20 * hguemar currently in Atlanta so not a good time for testing stuff carefully
14:47:29 <hhorak> bstinson: https://github.com/sclorg/sclo-ci-tests/tree/master/jenkins
14:47:39 <bstinson> perfect, thanks!
14:52:31 <hhorak> well, the time for the sclo is almost up, so last call for anybody...
14:58:07 <hhorak> if no, then thanks all, and see you next time!
14:58:10 <hhorak> #endmeeting