SweetOps #github-actions for April, 2024

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…

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

actions Archives - The GitHub Blog

05:15:38 PM

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

The GitHub Blog - Updates, ideas, and inspiration from GitHub to help developers build and design software.

Updates, ideas, and inspiration from GitHub to help developers build and design software.

2024-04-16

actions Archives - The GitHub Blog

05:25:44 PM

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

The GitHub Blog - Updates, ideas, and inspiration from GitHub to help developers build and design software.

Updates, ideas, and inspiration from GitHub to help developers build and design software.

actions Archives - The GitHub Blog

07:45:32 PM

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

The GitHub Blog - Updates, ideas, and inspiration from GitHub to help developers build and design software.

Updates, ideas, and inspiration from GitHub to help developers build and design software.

2024-04-22

actions Archives - The GitHub Blog

10:15:40 PM

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

The GitHub Blog - Updates, ideas, and inspiration from GitHub to help developers build and design software.

Updates, ideas, and inspiration from GitHub to help developers build and design software.

2024-04-24

Gabriel

10:03:26 AM

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?

Erik Osterman (Cloud Posse)

01:16:05 PM

Yes, this sounds familiar, or at least related

Erik Osterman (Cloud Posse)

01:16:26 PM

@venkata.mutyala alerted me to some of the problems after upgrading, one is that GHA are actually automatically disabled after upgrading

Erik Osterman (Cloud Posse)

01:16:34 PM

So make sure GHA are still enabled

Gabriel

01:23:02 PM

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.

GitHub Status

Welcome to GitHub’s home for real-time and historical data on system performance.

Erik Osterman (Cloud Posse)

01:40:11 PM

Hah, that seems like the more probably explanation

2024-04-25

johncblandii

03:52:58 PM

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?

cloudposse/github-action-atmos-affected-trigger-spacelift

A GitHub action to trigger spacelift for all atmos affected stacks

Dan Miller (Cloud Posse)

06:02:45 PM

That’s already supported by Spacelift natively. You can enable new runs for the same stack to cancel all previous runs

cloudposse/github-action-atmos-affected-trigger-spacelift

A GitHub action to trigger spacelift for all atmos affected stacks

Dan Miller (Cloud Posse)

06:04:53 PM

https://docs.spacelift.io/concepts/policy/push-policy/#canceling-in-progress-runs

Push policy - Spacelift Documentation

Collaborative Infrastructure For Modern Software Teams

Dan Miller (Cloud Posse)

06:05:13 PM

TLDR automatically cancel all queued runs if newer run is triggered for a given stack

johncblandii

07:08:49 AM

so we need to use your https://github.com/cloudposse/terraform-spacelift-cloud-infrastructure-automation/blob/main/catalog/policies/git_push.proposed-run.rego#L112-L117?

terraform-spacelift-cloud-infrastructure-automation/catalog/policies/git_push.proposed-run.rego at main · cloudposse/terraform-spacelift-cloud-infrastructure-automation attachment image

Terraform module to provision Spacelift resources for cloud infrastructure automation - cloudposse/terraform-spacelift-cloud-infrastructure-automation

Dan Miller (Cloud Posse)

04:17:58 PM

yeah our policy has specific conditions for cancelling runs, but you can configure that to whatever you need of course

Dan Miller (Cloud Posse)

04:19:06 PM

ie only cancel runs for the same PR, on plans, and if they’re in the Queued state (not in progress)

johncblandii

11:00:12 PM

but will it work the same if you’re squashing commits?

Dan Miller (Cloud Posse)

11:16:07 PM

I believe yes. Since the pull request head branch is still the same, it should match the conditions

run.branch == input.pull_request.head.branch

but tbf you should try it, and let me know if it works for you

johncblandii

04:17:32 PM

ok..sounds good

2024-04-29

Brett Au

01:30:54 AM

Having an issue with cloudposse/github-action-atmos-affected-stacks@v3

Only happens on PRs with no atmos related file changes, affected stacks is [] and jq fails to correctly run https://github.com/cloudposse/github-action-matrix-extended/issues/9

#9 JQ fails when affected stacks is empty

Describe the Bug

When updating our atmos repo, if we do not touch any component, catalog or stack files JQ fails to correctly parse the output.

jq: error: syntax error, unexpected ';' (Unix shell quoting issues?) at <top-level>, line 1:
def name: ;          
jq: 1 compile error
Error: The process '/usr/bin/jq' failed with exit code 3

When I run atmos locally the output is [] as expected

➜  affected=$(jq -c '.' affected-stacks.json)

➜  echo $affected
[]
➜  echo $affected | jq
[]

we are running cloudposse/github-action-atmos-affected-stacks@v3 which calls this action

Expected Behavior

cloudposse/github-action-atmos-affected-stacks@v3 runs successfully and returns an empty set so
if: ${{ needs.context.outputs.has-affected-stacks == 'true' }} returns false correct and doesn’t run more jobs based on the matrix.

Steps to Reproduce

name: "terraform plan matrix"

permissions:
  id-token: write
  contents: read
  pull-requests: write

on:
  pull_request:
    types: [opened, synchronize, reopened]

env:
  ATMOS_LOGS_LEVEL: Off

jobs:
  context:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v4

    - id: affected
      uses: cloudposse/github-action-atmos-affected-stacks@v3
      with:
        nested-matrices-count: 1

    outputs:
      affected: ${{ steps.affected.outputs.affected }}
      has-affected-stacks: ${{ steps.affected.outputs.has-affected-stacks }}
      matrix: ${{ steps.affected.outputs.matrix }}

Screenshots

image

Environment (please complete the following information):

Github actions runner ubuntu-latest

Additional Context

Add any other context about the problem here.

Erik Osterman (Cloud Posse)

02:36:12 AM

@Igor Rodionov

#9 JQ fails when affected stacks is empty

Describe the Bug

When updating our atmos repo, if we do not touch any component, catalog or stack files JQ fails to correctly parse the output.

jq: error: syntax error, unexpected ';' (Unix shell quoting issues?) at <top-level>, line 1:
def name: ;          
jq: 1 compile error
Error: The process '/usr/bin/jq' failed with exit code 3

When I run atmos locally the output is [] as expected

➜  affected=$(jq -c '.' affected-stacks.json)

➜  echo $affected
[]
➜  echo $affected | jq
[]

we are running cloudposse/github-action-atmos-affected-stacks@v3 which calls this action

Expected Behavior

Steps to Reproduce

name: "terraform plan matrix"

permissions:
  id-token: write
  contents: read
  pull-requests: write

on:
  pull_request:
    types: [opened, synchronize, reopened]

env:
  ATMOS_LOGS_LEVEL: Off

jobs:
  context:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v4

    - id: affected
      uses: cloudposse/github-action-atmos-affected-stacks@v3
      with:
        nested-matrices-count: 1

    outputs:
      affected: ${{ steps.affected.outputs.affected }}
      has-affected-stacks: ${{ steps.affected.outputs.has-affected-stacks }}
      matrix: ${{ steps.affected.outputs.matrix }}

Screenshots

image

Environment (please complete the following information):

Github actions runner ubuntu-latest

Additional Context

Add any other context about the problem here.

Erik Osterman (Cloud Posse)

02:36:25 AM

Cc @Gabriela Campana (Cloud Posse)