[FOLIO-2210] Changes in CI/CD process Created: 12/Aug/19  Updated: 03/Jun/20

Status: Open
Project: FOLIO
Components: Continuous Integration
Affects versions: None
Fix versions: None

Type: Task Priority: P3
Reporter: Mikita Siadykh Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: platform-backlog
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Sprint:
Development Team: Core: Platform

 Description   

Hi team,

testing and snapshot envs are down again again because of failed BE build and snapshot-stable env is stale because of failed auto tests

there are several proposals for test and snapshot envs:
1. roll back to the previous build version in case a new build is failed. In this case we'll always have working environments, but with a bit stale code (~1 day) - IMO it's not a big problem. plus dashboard shows what version is deployed - it will avoid confuses together with #2
2. notify devs that build is failed (it can be push notification in slack, email or smth like that) they can react.

plus snapshot-stable env
1. should have the last successful snapshot build (doesn't matter automation tests are failed or passed Zak Burke John Coburn what do you think? IMO we are interested in test reports that can be reviewed by anyone), because automation are usually failed because of timeouts etc that's not related to the functionality.
2. send test report to devs in case automation is failed



 Comments   
Comment by Zak Burke [ 12/Aug/19 ]

If a testing or snapshot build fails, the previous build should be restored. This is what we have in place right now for folio-snapshot-stable; if the integration tests fail, we do not update folio-snapshot-stable.

That said, it would be ideal to replace folio-snapshot-stable with a folio-release build constructed on-demand when new modules are released, but we don't release often enough for this to happen. I'm not sure how we find the right release cadence between nightly and quarterly.

Comment by Jakub Skoczen [ 12/Aug/19 ]

Mikita Siadykh A build success on its own is not enough to ensure the environment is "ok". As Zak Burke mentioned for this purpose we have the folio-snapshot-stable release which is updates only when the build is successful AND when the regression tests pass. The problem is that besides Zak Burke no one maintains regression tests so snapshot-stable is not updated frequently enough.

As Zak Burke mentioned, the release environment is much more stable and has passing regression tests and that's the environment we should be using going forward for things like Sprint Reviews. This will also mean we get more frequent releases.

I agree about notifications though – it would be good to send out e-mails to developers when the environment fails.

Comment by Mikita Siadykh [ 12/Aug/19 ]

Jakub Skoczen what do you think about restoring previous version on testing/snapshot (not stable)?

I agree that nobody support regression tests, that's why I asked about possibility last build, but with not failed testing/snapshot it's not really required

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