Re: Proposal to Change CATs Ownership
We had a series of meetings to figure out a good path for CATs that ranged
from multiple teams to smaller groups. We met most recently to address
concerns that include the following:
• Workflow and Release Bumping Issues: CATs relies on calls to specific
versions of CC API to run successfully. The CAPI CI currently bumps
cloud_controller_ng within capi-release, and on a successful run of CATs
(which lives on cf-release develop), capi-release then gets bumped in
cf-release develop. This leads to a "chicken and egg" scenario, in that
when changes are made to both CATs and CC, both cf-release and capi
pipelines are broken until a manual fix is made.
• In a world where cf-release no longer exists, how do we ensure CATs uses
the correct versions of the CF CLI and CC API?
tl;dr: Though not all of the CATs test the CC API explicitly, they all make
use of the CC API and therefore make CC a choke point. Having CATs as a
separate release may be a good idea, but doesn't necessarily address the
strong coupling issues.
We'd like to know if there are specific cases in which this will be
detrimental to other projects' workflows before moving forward.
On Wed, Mar 23, 2016 at 4:08 AM, Michael Fraenkel <
Can you explain why CATs should live under CAPI?CATs now represents acceptance test for all of the Cloud Foundry function
driven mainly via the CLI.Tieing this to any one release seems a bit artificial.
CATs is about testing the aggregation of all the various releases not just