#github-actions (2024-04)
Discussions related to GitHub Actions
2024-04-01
macOS 14 (Sonoma) is generally available and the latest
macOS runner image
macOS 14 (Sonoma) is generally available and the latest
macOS runner image
The post macOS 14 (Sonoma) is generally available and the latest
macOS runner image appeared first on The GitHub Blog.
macOS 14 (Sonoma) is generally available and the latest
macOS runner image
Updates, ideas, and inspiration from GitHub to help developers build and design software.
2024-04-02
What’s new for GitHub Actions hosted runners What’s new for GitHub Actions hosted runners The post What’s new for GitHub Actions hosted runners appeared first on The GitHub Blog.
What’s new for GitHub Actions hosted runners
Updates, ideas, and inspiration from GitHub to help developers build and design software.
GitHub Actions: Hardware accelerated Android virtualization now available GitHub Actions: Hardware accelerated Android virtualization now available The post GitHub Actions: Hardware accelerated Android virtualization now available appeared first on The GitHub Blog.
GitHub Actions: Hardware accelerated Android virtualization now available
2024-04-04
Actions: Jobs executing on self hosted runners will now timeout in 5 days To ensure that the Actions runners are truly ephemeral and more secure, we are now limiting execution timeouts on self hosted jobs to 5 days. If a job reaches this limit, the job is terminated and fails to complete. Learn more about using self-hosted runners with GitHub Actions The post Actions: Jobs executing on self hosted runners will now timeout in 5 days…
To ensure that the Actions runners are truly ephemeral and more secure, we are now limiting execution timeouts on self hosted jobs to 5 days. If a job reaches this limit, the job is terminated and fails to complete. Learn more about using self-hosted runners with GitHub Actions
2024-04-10
GitHub-hosted runner images deprecation notice: Docker Compose v1 GitHub-hosted runner images deprecation notice: Docker Compose v1 The post GitHub-hosted runner images deprecation notice: Docker Compose v1 appeared first on The GitHub Blog.
GitHub-hosted runner images deprecation notice: Docker Compose v1
Updates, ideas, and inspiration from GitHub to help developers build and design software.
2024-04-16
Deprecation notice: v3 of the artifact actions Deprecation notice: v3 of the artifact actions The post Deprecation notice: v3 of the artifact actions appeared first on The GitHub Blog.
Deprecation notice: v3 of the artifact actions
Updates, ideas, and inspiration from GitHub to help developers build and design software.
Deprecation of multi-label larger runners Deprecation of multi-label larger runners The post Deprecation of multi-label larger runners appeared first on The GitHub Blog.
Deprecation of multi-label larger runners
Updates, ideas, and inspiration from GitHub to help developers build and design software.
2024-04-22
Dependabot Updates on Actions for GitHub Enterprise Cloud and Free, Pro, and Teams Users Dependabot Updates on Actions for GitHub Enterprise Cloud and Free, Pro, and Teams Users The post Dependabot Updates on Actions for GitHub Enterprise Cloud and Free, Pro, and Teams Users appeared first on The GitHub Blog.
Dependabot Updates on Actions for GitHub Enterprise Cloud and Free, Pro, and Teams Users
Updates, ideas, and inspiration from GitHub to help developers build and design software.
2024-04-24
After creating an enterprise account and moving orgs under one enterprise, we have many queued jobs waiting for runners. Did anyone experience the same after moving orgs under an enterprise?
Yes, this sounds familiar, or at least related
@venkata.mutyala alerted me to some of the problems after upgrading, one is that GHA are actually automatically disabled after upgrading
So make sure GHA are still enabled
Thanks. Yes, everything is working but the runners stay queued for too long, I found the problem, it’s our concurrent jobs limit which went down to 10 is increasing slowly by 1 every 10 min or so. But GH also seems to have a lot of issues today. https://www.githubstatus.com/. Maybe it’s just a weird coincidence.
Welcome to GitHub’s home for real-time and historical data on system performance.
Hah, that seems like the more probably explanation
2024-04-25
re: https://github.com/cloudposse/github-action-atmos-affected-trigger-spacelift.
can we get an update so it cancels old plans on feature branches?
Context:
• push a PR (commit abc
)
• Action triggers 20 stacks
• push a commit before those stacks finish planning (commit def
• Action triggers 20 stacks
You’ll now have up to 40 stacks (depending how fast it was triggered) and commit abc
is irrelevant now. We want to just verify def
(the latest).
Thoughts?
A GitHub action to trigger spacelift for all atmos affected stacks
That’s already supported by Spacelift natively. You can enable new runs for the same stack to cancel all previous runs
A GitHub action to trigger spacelift for all atmos affected stacks
Collaborative Infrastructure For Modern Software Teams
TLDR automatically cancel all queued runs if newer run is triggered for a given stack