On 01/09/2017 08:33 PM, Mainzer, Gal wrote: > Maybe not as a gate job but more of a periodic that runs every 4-6 hours.
well, if you put it like this, we already have it right? except we run every 24 hours, not 4-6. I'm leery to bump our openstack csit jobs to a quicker cadence because each job takes ~90m (and it's growing). And we have a significant number of them. Our infra is sometimes pretty saturated as it is. Maybe we can pick just one of these jobs to run at a higher frequency. That would at least give us a shorter time frame to search for patches, when we get a regression. > > At this stage, those jobs are stable enough (and if not we are really close > to that point) for a single failure to state > that there is a regression. All we need to agree is that if that cloud suite > is failing - all relevant project should stop > merging (even as a process and not by a gerrit mechanic lock) until we are > back from regression. we aren't totally stable enough yet, imho. We are very close though. <devils advocate> however convincing these dependent projects to stop merging is asking a lot. Who says md-sal or controller gives a hoot about the "cloud" stuff working for opendaylight. maybe other ODL projects are still working fine and the assumption is our cloud projects are the projects that need to fix themselves, while everyone else can continue to do work. </devils advocate> > We can add additional job that with a single click, will collect all commits > from all relevant projects that are suspected > - as Jamo said, ~15 are dependent. This will reduce our analysis time by even > maybe reverting suspected commits just to > come back from the regression and release the "lock". this would be super cool. > Without proper dashboard I'm not really expecting all projects to monitor > this, but at first stage we can monitor that job > (like we do today) and send critical mail on certain failures. our poor man's dashboard is just the regular jenkins job landing page. We need to get things coming back blue on a consistent basis first, because every time I look it's mostly red and yellow. JamO > Sent from my iPhone > > On 10 Jan 2017, at 1:31, Robert Varga <n...@hq.sk> wrote: > >> On 01/09/2017 10:37 PM, Jamo Luhrsen wrote: so you mean to have this "cloud >> suite" run as a gating job on gerrit patches >> for all projects that our "ODL for openstack" needs, I think. That would be >> nice, but we would need to convince a lot >> of projects to do it. Looks like at least 12 projects are dependencies for >> netvirt: >> >> controller,dlux,genius,infrautils,mdsal,netconf,neutron,odlparent,openflowplugin,ovsdb,sfc,yangtools > > Judging from how long it takes for -autorelease and -distcheck to stabilize > for each release, I would hate to see such a > job gate offset-0 patches. > > In this particular set of projects, there is a history of breakage happening > on OFP/OVSDB and OVSDB/SFC (I think) > boundaries. > > Just my .02, Robert > _______________________________________________ controller-dev mailing list controller-dev@lists.opendaylight.org https://lists.opendaylight.org/mailman/listinfo/controller-dev
