CATS errand missing about cf-deployment

[cf-gitbot]

We have created an issue in Pivotal Tracker to manage this:

https://www.pivotaltracker.com/story/show/140759143

The labels on this github issue will be updated when the story is started.

[dsabeti]

Hi @tscolari.

Have you seen our concourse task for running CATs? It's the way to run CATs that the Release Integration team is supporting. Would this meet your team's needs, or is there a reason that you need an errand specifically?

For context, one of the positions cf-deployment is taking is that CATs is for developer teams to validate their code changes -- not for deployers who want to validate their configuration. That's why we want to support a concourse task instead of a BOSH errand.

[tscolari]

Hello @dsabeti

That should work for us.
It does require a bit more of setup (e.g. parsing credentials into the json file), but it will do for us :)
We atm are still pushing the cf-release and running the errand, but we've added a chore to migrate to the concourse task.

Many thanks!

[bingosummer]

@dsabeti Does it make sense to add an ops file to add a CATS errand?

[dsabeti]

@bingosummer, you could always write such an ops-file for yourself, but I probably wouldn't want to add it to cf-deployment. As I said, I see it as a test suite for the CF development teams, who primarily use Concourse.

However, I'd be interested to hear how you'd like to run CATs -- are you using the test suite to validate changes to the releases themselves, or do you want to validate the functionality of a particular deployment? What tooling are you (Concourse, Travis, errands, etc.) are you currently using to run CATs?

[bingosummer]

Thanks @dsabeti .
To verify the PR #191 , I use https://github.com/cloudfoundry/cats-concourse-task to run CATs. But to provide credentials for integration-config, I have to make some changes to provide credentials directly instead of the integration-config repo.

Agreed with you. I can write ops-file by myself if someone in my team prefers the errand.