Add reliable engine binary retrieval

[RevoluPowered]

Why?

• We kept having bugs when ingesting the binaries into github steps, 50 percent of the time it would fail and keep failing or the artefacts were deleted by GitHub.
• I just implemented a bucket to upload these binaries in GCP as it is 3 times faster, and also always is guaranteed to actually function for our development branch.
• We're working towards getting a full release out soon.

Changes:

• Split the engine and the app build into separate files
• Used composite job for the engine build so we can easily invoke it at the correct phase
• Upload the binaries to GCP and GitHub artefacts, so that the GCP bucket contains a binary for each engine hash.
• Add hash checker to ensure builds fail as early as possible if this is missing.
• Ensure we build the engine before building the app.
• Format fixes.

Important (ONLY FOR Pull Requests. on the dev branch on the dev branch this is totally automatic):

• Engine builds must update the Engine / Template hash manually until we make some additional changes to this code

Future:

• We can re-merge the deployment-pr.yml once we have some simple code to grab the correct engine hash without running the engine.yml file. (right now the editor and template are just static links but only in the PR context)
• In the engine build context (on the dev branch we can safely upload engine binaries as they have been vetted)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Ignored Deployment

Name	Status	Preview	Comments	Updated (UTC)
mirror-docs	⬜️ Ignored (Inspect)	Visit Preview		Apr 11, 2024 4:04pm