[FOLIO-2188] Previous folio-snapshot build is not removed when build has failed Created: 22/Jul/19  Updated: 03/Jun/20  Resolved: 23/Jul/19

Status: Closed
Project: FOLIO
Components: None
Affects versions: None
Fix versions: None

Type: Task Priority: P2
Reporter: John Malconian Assignee: John Malconian
Resolution: Done Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint: CP: sprint 68
Story Points: 2
Development Team: Core: Platform

 Description   

When a new ec2 instance for folio-snapshot is created it is tagged with 'Group: folio_snapshot'. After a folio-snapshot build is successful, it is tagged with 'Build: folio_snapshot_latest'. When the UI regression tests pass, the Group and Build tags are updated to 'folio_snapshot_stable'. Before a new folio-snapshot build is run, we check for the existence of the previous folio_snapshot build by looking for an instance with the 'Build: folio_snapshot_latest tag'. If found, we terminate that instance. However, if the previous build had failed before the Build tag was applied, it doesn't find this instance and proceeds. However, there may be an ec2 instance still hanging around with the tag 'Group: folio_snapshot'. This can lead to some problems with the latest folio-snapshot build since the target Ansible host is based on the Group tag.



 Comments   
Comment by John Malconian [ 23/Jul/19 ]

When a new folio-snapshot/folio-snapshot-core build is initiated, the previous instance is now search on the Group tag which is applied when the EC2 instance is created. This change should fix most issues that could occur. The only time it may not is if something goes wrong with creating the EC2 instance.

Generated at Thu Feb 08 23:18:52 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.