Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create jobs to separate AWS environments from build environments #481

Open
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

klutchell
Copy link
Contributor

@klutchell klutchell commented Jan 2, 2025

This allows more granular control over which environments are used for which steps, and avoids requiring a single environment to define how to build, sign, and publish.

Initially this workflow will still fallback to the existing monolith environments and the behaviour should be unchanged.

See: https://balena.fibery.io/Work/Improvement/Update-yocto-scripts-workflow-with-separate-jobs-for-AWS-and-signing-environments-2471

image

Here are the workflows still pinned to master, generally meaning their builds are broken either way or Renovate would have pinned them to the current yocto-scripts submodule commit.
https://github.com/search?type=code&q=yocto-build-deploy.yml%40master+NOT+repo%3Abalena-os%2Fmeta-balena

.github/workflows/yocto-build-deploy.yml Fixed Show fixed Hide fixed
.github/workflows/yocto-build-deploy.yml Dismissed Show dismissed Hide dismissed
.github/workflows/yocto-build-deploy.yml Fixed Show fixed Hide fixed
.github/workflows/yocto-build-deploy.yml Dismissed Show dismissed Hide dismissed
This allows more granular control over which environments are used
for which steps, and avoids requiring a single environment to define
how to build, sign, and publish.

This is better for security as it allows each job to only have
the secrets it needs, and not all secrets for all steps.

We retain backwards compatibility by falling back to the original
monolith environment input for now.

Change-type: minor
Signed-off-by: Kyle Harding <[email protected]>
This key was only used to fetch the supervisor image name from the API,
but that endpoint does not need auth as the supervisor images are public.

Change-type: patch
Signed-off-by: Kyle Harding <[email protected]>
S3 deploy needs most of the files generated by the
prepare artifacts function, so compress them as much
as possible and remove images that have been zipped.

This creates artifacts up to 2.4gb in size, but most
should be less.

Signed-off-by: Kyle Harding <[email protected]>
@klutchell klutchell marked this pull request as ready for review January 16, 2025 21:09
@klutchell klutchell temporarily deployed to balena-staging.com January 16, 2025 21:09 — with GitHub Actions Inactive
@klutchell klutchell temporarily deployed to balena-staging.com January 16, 2025 21:09 — with GitHub Actions Inactive
@klutchell klutchell temporarily deployed to balena-staging.com January 16, 2025 21:10 — with GitHub Actions Inactive
@flowzone-app flowzone-app bot enabled auto-merge January 16, 2025 21:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant