-
Notifications
You must be signed in to change notification settings - Fork 22
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
klutchell
wants to merge
6
commits into
master
Choose a base branch
from
kyle/env-cleanup
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
klutchell
temporarily deployed
to
balena-staging.com
January 2, 2025 19:21 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-staging.com
January 2, 2025 19:21 — with
GitHub Actions
Inactive
klutchell
had a problem deploying
to
balena-staging.com
January 2, 2025 19:22 — with
GitHub Actions
Error
klutchell
force-pushed
the
kyle/env-cleanup
branch
from
January 2, 2025 19:58
763a166
to
d43072d
Compare
klutchell
temporarily deployed
to
balena-staging.com
January 2, 2025 19:58 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-staging.com
January 2, 2025 19:58 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-staging.com
January 2, 2025 19:59 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 2, 2025 20:31 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 2, 2025 20:31 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 2, 2025 20:31 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 3, 2025 16:25 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-staging.com
January 3, 2025 16:26 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 3, 2025 16:26 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 3, 2025 17:01 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 3, 2025 17:01 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 3, 2025 17:01 — with
GitHub Actions
Inactive
klutchell
force-pushed
the
kyle/env-cleanup
branch
from
January 3, 2025 17:32
3124776
to
5c257c4
Compare
klutchell
temporarily deployed
to
balena-staging.com
January 3, 2025 17:32 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-staging.com
January 3, 2025 17:33 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-staging.com
January 3, 2025 17:33 — with
GitHub Actions
Inactive
klutchell
had a problem deploying
to
balena-staging.com
January 3, 2025 18:37 — with
GitHub Actions
Failure
klutchell
had a problem deploying
to
balena-staging.com
January 3, 2025 18:37 — with
GitHub Actions
Failure
klutchell
temporarily deployed
to
balena-cloud.com
January 3, 2025 18:37 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 3, 2025 18:37 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 3, 2025 18:37 — with
GitHub Actions
Inactive
klutchell
force-pushed
the
kyle/env-cleanup
branch
from
January 3, 2025 19:30
5c257c4
to
84c7d83
Compare
klutchell
temporarily deployed
to
balena-staging.com
January 3, 2025 19:30 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-staging.com
January 13, 2025 19:29 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 13, 2025 19:29 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 13, 2025 19:29 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 13, 2025 19:29 — with
GitHub Actions
Inactive
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]>
klutchell
force-pushed
the
kyle/env-cleanup
branch
from
January 13, 2025 20:48
02e3cb8
to
4ebdc08
Compare
klutchell
temporarily deployed
to
balena-staging.com
January 13, 2025 20:48 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-staging.com
January 13, 2025 20:48 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-staging.com
January 13, 2025 20:49 — with
GitHub Actions
Inactive
klutchell
had a problem deploying
to
balena-staging.com
January 13, 2025 21:23 — with
GitHub Actions
Failure
klutchell
temporarily deployed
to
balena-staging.com
January 13, 2025 21:23 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 13, 2025 21:23 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 13, 2025 21:23 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 13, 2025 21:23 — with
GitHub Actions
Inactive
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]>
Signed-off-by: Kyle Harding <[email protected]>
Signed-off-by: Kyle Harding <[email protected]>
klutchell
force-pushed
the
kyle/env-cleanup
branch
from
January 16, 2025 21:08
4ebdc08
to
b435169
Compare
klutchell
temporarily deployed
to
balena-staging.com
January 16, 2025 21:09 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-staging.com
January 16, 2025 21:09 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-staging.com
January 16, 2025 21:10 — with
GitHub Actions
Inactive
klutchell
temporarily deployed
to
balena-cloud.com
January 16, 2025 21:48 — with
GitHub Actions
Inactive
klutchell
had a problem deploying
to
balena-cloud.com
January 16, 2025 21:48 — with
GitHub Actions
Failure
klutchell
had a problem deploying
to
balena-cloud.com
January 16, 2025 21:48 — with
GitHub Actions
Failure
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
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