Build/Release Automation Notes 8/10/22

Process for automating release to Magento cloud

• Int/Stg/Prod will automatically deploy on push

• Can look into composer commands to help with some automation

• Retrieving/syncing things to Magento cloud would be more of a lift

• https://devdocs.magento.com/cloud/reference/cli-ref-topic.html

• Diff domains within the same repo/instance

  • Share code across the websites, no real way to separate them now

  • Going to have to coordinate across the domains for releasing, because they will have to be released at the same time

  • Requires regression testing across all domains that share the magento instance

    • Automating this will reduce some of the manual lift for each release

Concerns with using Azure for all needs, may be overkill

• Things like MBI chron reports aren’t the best suited for Azure Pipelines

  • Just running bash scripts

• Using Azure Pipelines for this is great for visibility and consolidation

• But the upskilling/knowledge sharing lift is great

• Still makes sense for build and deploy tasks

• For bespoke automations, would like to investigate different solutions

  • Drone, BuddyCI

  • N8N.io

    • All functional work is in JS, nothing new to learn

    • Free, self-hosted solution that allows us to tie into our APIs and run as much compute time as we want

    • Does this need to go through InfoSec/OneTrust for us to use?

Back-syncing post release across environments

• Ben to put to paper proposal for flow up and down

• DBs and assets need to come down on demand

• Should be a bash/shell script in the codebase – need real time SSH codebase access for these syncing processes to be useful

• Can also be part of the release pipeline to be the last step as part of each release