ACS-2499 Delete company release build stage. (#524)

* ACS-2499 Delete company release build stage.

This never uploaded any software, and so was not particularly useful. The software and license report should be
uploaded to S3 as part of the transform-service build.

Also skip uploading anything to staging bucket.

docs/build-and-release.md

@@ -5,8 +5,7 @@ The `.travis.yml` config file can be found in the root of the repository.
 
 ## Stages and Jobs
 1. **Build**: Java build with unit and integration tests.
-2. **Release**: Release with artifact deployment to Nexus and AWS Staging bucket.
-3. **Company Release**: Artifact deployment to AWS Release bucket.
+2. **Release**: Release with artifact deployment to Nexus, DockerHub and Quay.io.
 
 
 ## Branches
@@ -27,10 +26,6 @@ Travis CI builds differ by branch:
   of the release jobs (no artifacts will be published until the PR is actually merged).
 * `ATS-*` branches:
   - regular builds which include only the _Build_ and _Tests_ stages;
-* `company_release` branch:
-  - builds that include the _Company Release_ stage only.
-  - the `company_release` branch should be used for one-off events; once used (a build 
-  completes), the branch should be deleted.
 
 All other branches are ignored.
 
@@ -67,13 +62,3 @@ been generated by steps (2) and (3), then an empty commit should be created - e.
 **Create a merge commit** (_Merge pull request_) or **Squash and merge** options are used, you 
 need to ensure that the _commit message_ contains the `[trigger release]` tag (sub-string).
 
-## Company Release process steps & info
-Prerequisites:
-  - The **Release** stage is complete - i.e. the release commit is tagged and the release 
-  artifacts are deployed on Nexus.
-
-Steps:
-1. Create a new `company_release` branch from the `master` / `SP/*`/ `HF/*` branch. This job uses 
-the latest branch git tag to identify the version that must be uploaded to the S3 release bucket.
-2. Wait for a green build on the branch.
-3. Delete local and remote `company_release` branch.