[FINERACT-970] Automatically continuously integrate and deploy ("CI/CD") Fineract develop branch to fineract.dev

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.4.0
• Assignee: Michael Vorburger
• Reporter: Michael Vorburger
• Created: 10/May/20 11:49
• Updated: 22/May/20 03:24
• Resolved: 17/May/20 00:06

Description

The goal of this issue is to have every pull request merged to the develop branch on https://github.com/apache/fineract/ be as quickly as possible automatically continuously built and deployed ("CI/CD") to (my) https://www.fineract.dev demo server.

I originally requested INFRA-20143 for this, but meanwhile found a better way. Given that we're in in 2020 not 1990, I was surprised how non-trivial is is to do this in an open yet secure way... I think I'll write up a short personal blog post about it when I'm fully done with this.

Issue Links

• blocks: FINERACT-786 Fineract on Google Cloud ("managed", with Cloud SQL)
• is blocked by: FINERACT-979 Flyway cannot apply migrations because default schema history table name in new Flyway version now is flyway_schema_history instead of schema_version
• is blocked by: FINERACT-983 /actuator/info is empty in container
• relates to: FINERACT-994 Do not try to deploy to fineract.dev on forked branches
• links to: GitHub Pull Request #898
• links to: GitHub Pull Request #899
• links to: GitHub Pull Request #900
• links to: GitHub Pull Request #901
• links to: GitHub Pull Request #902
• links to: GitHub Pull Request #903
• links to: GitHub Pull Request #921