Enhance the ploigos-software-factory-operator test pipeline

[dwinchell]

It should:

1. Clean up any hanging resources from failed runs
2. Install the operator from scratch into the tssc.rht-set.com cluster
3. Create a TsscPlatform
4. Create a TsscPipeline
5. Verify that the pipeline created in Jenkins to build the reference app is green
6. Clean up created resources

There is an existing pipeline in Travis: https://travis-ci.com/github/ploigos/ploigos-software-factory-operator/

[andykrohg]

We're currently doing steps 1,2,3, and 6 in Travis (.travis.yml), though in random RHPDS clusters instead of the incubator cluster. Because of the recently-instituted upper limits on free tier Travis builds, we'll eventually need to migrate this to something else anyway, but the implementation could be used as a starting point for what comes next.

[dwinchell]

@andykrohg I am working on this one. I think our least bad alternative to Travis right now is Jenkins.

I started looking at the travis pipeline, operate.sh, and the Makefile last night. Quick question - is the helm install in .travis.yml actually used for anything? https://github.com/ploigos/ploigos-software-factory-operator/blob/e59cc6631939c5423c891cf289cac608d9053283/.travis.yml#L13

[andykrohg]

@andykrohg I am working on this one. I think our least bad alternative to Travis right now is Jenkins.

I started looking at the travis pipeline, operate.sh, and the Makefile last night. Quick question - is the helm install in .travis.yml actually used for anything?

https://github.com/ploigos/ploigos-software-factory-operator/blob/e59cc6631939c5423c891cf289cac608d9053283/.travis.yml#L13

No 😊

[dwinchell]

Phew. I was worried the rabbit hole went deeper :smile:

[jharmison-redhat]

That was to support an easy Nginx installation on Kind, which was a test target from earlier versions of various operators.