Update ESC build to enable Alpha release

Description

Acceptance Criteria

As a developer on the ESC project
When I set the release and development versions in the travis file
And I create a commit with a message containing the term “[release]“
And I push it to the master branch of ESC
Then a release is made such that:

  • The release jars are published in Nexus

  • The jars are published to the enterprise S3 bucket

  • The release docker images are published to quay.io

Notes

  • Currently the only release branch is master, so it is not necessary to check that releasing from branches starting with “release/” works.

Activity

Show:
Tom Page
February 17, 2021, 9:27 PM
Tom Page
February 17, 2021, 10:43 PM

Similar success with the 1.0.0-A2 release. This time we were missing the AWS_STAGING_ACCESS_KEY and AWS_STAGING_SECRET_KEY variables, and so the release could by not uploaded to S3.

Tom Page
February 17, 2021, 11:34 PM

The release of 1.0.0-A3 seems to have been successful. Green build and the log says that the app jars were uploaded to S3.

Done

Assignee

Unassigned

Reporter

Tom Page

Labels

None

Release Train

Iver

Delivery Team

Search

Story Points

3

Epic Link

Sprint

None

Fix versions

Priority

Unprioritized