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
PR:
Release build for 1.0.0-A1: https://travis-ci.com/github/Alfresco/alfresco-elasticsearch-connector/builds/217341314
Release was partially successful. Some artifacts are now available.
Git tag: https://github.com/Alfresco/alfresco-elasticsearch-connector/releases/tag/1.0.0-A1
Nexus: https://nexus.alfresco.com/nexus/#nexus-search;gav~org.alfresco~alfresco-elasticsearch*~1.0.0-A1~~
Docker images (with tag 1.0.0-A1 and also with digest appended):
https://quay.io/repository/alfresco/alfresco-elasticsearch-live-indexing?tab=tags
https://quay.io/repository/alfresco/alfresco-elasticsearch-live-indexing-content?tab=tags
https://quay.io/repository/alfresco/alfresco-elasticsearch-live-indexing-mediation?tab=tags
https://quay.io/repository/alfresco/alfresco-elasticsearch-live-indexing-metadata?tab=tags
There was a syntax error which prevented upload to S3 from working.
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.
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.
Assignee
Reporter
Labels
Release Train
Delivery Team
Story Points
Epic Link
Sprint
Fix versions
Priority
