> It must not break any existing downstream system as well as the upstream > pipelines. So all implementations should be disabled by default along with > proper > switches.
Agreed. There is a feature flag class that Chetan introduced when I introduced a breaking change (sorry) a few months ago that should be useful here. > It would be better to have a new separate (openwhisk) CI pipeline for the > changes. Do you mean a new Jenkins child which toggles on the related switches? This makes sense. -r
