Update Travis to build and push the operator container

[JohnStrunk]

Describe what this PR does
This updates the Travis-CI configuration to build the container image for the operator, and, if successful, it will push the image to quay.io

Is there anything that requires special attention?
no

Related issues:

• Related to Set up TravisCI, codecov #31
  • Adds automated build and linting of goland files.

[jarrpa]

I'd like to see more scripting such that the linters can be reproduced locally before sending them off to Travis, but that can come in another PR. The PR LGTM as is, but I'd like to ask: how are the QUAY_ and DOCKER_ variables set in Travis? Is that configured privately on the Travis end?

[JohnStrunk]

I'd like to ask: how are the QUAY_ and DOCKER_ variables set in Travis?

They are set in the Travis settings on the website. Since these are sensitive, they can't be set in the standard env block. They must either be encrypted in the yaml or set on the web settings page. While the settings page isn't version controlled, it's much easier to see the config and change it.

[jarrpa]

They are set in the Travis settings on the website. Since these are sensitive, they can't be set in the standard env block. They must either be encrypted in the yaml or set on the web settings page. While the settings page isn't version controlled, it's much easier to see the config and change it.

Makes total sense, wanted to make sure it wasn't just assumption. ;)