| *** rfolco_ has joined #openstack-third-party-ci | 00:39 | |
| *** rfolco_ has quit IRC | 00:50 | |
| *** Apoorva_ has joined #openstack-third-party-ci | 01:25 | |
| *** Apoorva has quit IRC | 01:29 | |
| *** Apoorva_ has quit IRC | 01:30 | |
| *** asselin has quit IRC | 02:03 | |
| *** rfolco_ has joined #openstack-third-party-ci | 11:41 | |
| *** thiagop has joined #openstack-third-party-ci | 12:54 | |
| *** thiagop has quit IRC | 13:09 | |
| *** thiagop has joined #openstack-third-party-ci | 13:11 | |
| *** wznoinsk has joined #openstack-third-party-ci | 13:56 | |
| wznoinsk | hi all, what's the purpose of this # ? | 13:56 |
|---|---|---|
| wznoinsk | do you post issues here when you see them in 3rd party CIs? | 13:57 |
| wznoinsk | how do you verify your CIs is giving true results? ci-watch or else? | 14:02 |
| mmedvede | wznoinsk: this channel is for third-party operators to discuss any topics | 14:16 |
| mmedvede | wznoinsk: but you can still use #openstack-infra | 14:17 |
| mmedvede | I do not think there is a vetted tool to determine stability of CI. Any voting history would do. ci-watch is one way you can check your CI against upstream and others | 14:19 |
| wznoinsk | I was wondering how different operators use, what logic etc. for that, I don't think there can be any single rule for that, each CI tests different features hence may break at different times | 14:22 |
| *** Apoorva has joined #openstack-third-party-ci | 16:42 | |
| *** Apoorva has quit IRC | 17:21 | |
| *** Apoorva has joined #openstack-third-party-ci | 17:22 | |
| *** openstackgerrit_ has joined #openstack-third-party-ci | 20:35 | |
| *** openstackgerrit_ has quit IRC | 20:36 | |
| *** Apoorva_ has joined #openstack-third-party-ci | 22:06 | |
| *** Apoorva has quit IRC | 22:09 | |
| *** rfolco_ has quit IRC | 22:15 | |
| *** Apoorva_ has quit IRC | 22:43 | |
| *** Apoorva has joined #openstack-third-party-ci | 22:44 | |
| *** thiagop has quit IRC | 23:39 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!