|
I've completed the following changes to folio-snapshot. 'folio-snapshot' is a daily FOLIO build which utilizes the folio-registry and module descriptors to enforce dependencies across modules (unlike 'folio-testing).
Overview of major changes:
- The last folio-snapshot build that passes all UI regression tests can be accessed at:
http://folio-snapshot-stable.aws.indexdata.com - Sometimes 'folio-snapshot-latest' and 'folio-snapshot-stable' will point to the same instance. Sometimes not.
- Each build is a separate build of folio-snapshot and can be accessed directly by appending the Jenkins build number in the URL. e.g http://folio-snapshot-36.aws.indexdata.com. DNS aliases 'folio-snapshot-latest' and 'folio-snapshot-stable' are always applied after a successful build (or successful build that passes UI regression tests in the case of 'folio-snapshot-stable'). The benefit to this is that there should always be a 'folio-snapshot-latest' up and available even if the last build fails to complete.
- I use AWS tagging to attach special build tags to the instances associated with each build so that old, unused AWS instances can be safely terminated via a separate automated job.
- I incorporated UI regression testing into the same pipeline that builds the FOLIO platform so that UI regression test reports are published alongside each build in Jenkins making it easier to associate test results with a specific build. See example here:
https://jenkins-aws.indexdata.com/job/Automation/job/folio-snapshot/36/UI_Regression_Test_Report/
|