-
Story
-
Resolution: Done
-
Undefined
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
None
-
None
-
None
-
NetObserv - Sprint 263, NetObserv - Sprint 264, NetObserv - Sprint 265
We could create a cron trigger that works on the main branch, in addition to the ones on the downstream builds. This would be helpful as main branch changes much more often than downstream builds, this is where it would help more to catch any regression at the earliest.
We may leave this job working all the time, and only turn on the one on downstream build after cutting branches for a release.