#github-actions (2023-05)

Discussions related to GitHub Actions

2023-05-01

timduhenchanter avatar
timduhenchanter

Anyone have any unique implementations of deleting the infrastructure tied to IaC when the corresponding repository is deleted in the absence of a trigger for repository/delete?

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

Maybe consider centralizing the management of repos. That way to delete a repo, you delete it from the configuration, rather than click ops.

Sudhish KR avatar
Sudhish KR

Hey Folks,

We at Dgraph Labs use Github as our VCS. And we have recently migrated our CI/CD setup to Github Actions. This was a huge win for us internally, especially in a startup setting like ours. Our wins were broadly in these 3 areas Compute Costs, Maintenance Efforts & Configuration Time.

With this new setup, we designed & developed Dynamic AutoScaling of Github Runners in house. We are thinking of open-sourcing this project. If there is any interest here - pls do reach out. We were able to save ~87% $$ of our Compute Costs with this setup.

Blog Link => https://www.sudhishkr.com/posts/20230217_dynamic-autoscaling-of-github-runners/

Dynamic AutoScaling Of GitHub Runnersattachment image

In this article we explain our transition to GitHub Actions for our CI/CD needs at Dgraph Labs Inc. As a part of this effort we have built (in-house) & implemented a new architecture for “Dynamic AutoScaling of GitHub Runners” to power this setup. In the past, our CI/CD was powered by a self-hosted on-prem TeamCity setup - this turned out to be a little difficult to operate & manage in a startup setting like ours. Transitioning to GitHub Actions & implementing our new in-house built “Dynamic AutoScaling of GitHub Runners” - has helped us reduce our Compute Costs, Maintenance Efforts & Configuration Time across our repositories for our CI/CD efforts (with improved security).

Joe Perez avatar
Joe Perez

@Sudhish KR Congrats on the successful migration! Plz open source this implementation, I would like to see how this works under the hood

Dynamic AutoScaling Of GitHub Runnersattachment image

In this article we explain our transition to GitHub Actions for our CI/CD needs at Dgraph Labs Inc. As a part of this effort we have built (in-house) & implemented a new architecture for “Dynamic AutoScaling of GitHub Runners” to power this setup. In the past, our CI/CD was powered by a self-hosted on-prem TeamCity setup - this turned out to be a little difficult to operate & manage in a startup setting like ours. Transitioning to GitHub Actions & implementing our new in-house built “Dynamic AutoScaling of GitHub Runners” - has helped us reduce our Compute Costs, Maintenance Efforts & Configuration Time across our repositories for our CI/CD efforts (with improved security).

Sudhish KR avatar
Sudhish KR

@Joe Perez thanks for the kind message. I am happy to share the internals, and even drop a demo to you if required. We will be open sourcing this in about a month (we areprepping to work on some smart features).

1
Pawel Rein avatar
Pawel Rein

Thanks for sharing (and I’m looking forward to seeing it opensourced)! It would be great to see efficiency (cost) comparison between Philips and your solution

Joe Perez avatar
Joe Perez

a demo would be great too, looking forward to the release!

Sudhish KR avatar
Sudhish KR

@Pawel Rein thanks for the idea. Thats a good way to show efficiency. Let me try something on that front.

Also @Joe Perez when we OS this repo we can add a quick video snippet of this in works to help understand the ease of use & setup of this compared to other tools.

Both are good feedback - appreciate everyones ideas! thank you

1

2023-05-02

samuel avatar

Good afternoon, I am setting self-hosted runner, then I am recibed a msj The SSL connection could not be established, see inner exception. but I don´t have idea becouse this msj

2023-05-03

2023-05-04

actions Archives | The GitHub Blog avatar
actions Archives | The GitHub Blog
12:55:37 PM

GitHub Actions: All Actions will run on Node16 instead of Node12 GitHub Actions: All Actions will run on Node16 instead of Node12

GitHub Actions: All Actions will run on Node16 instead of Node12 | GitHub Changelogattachment image

GitHub Actions: All Actions will run on Node16 instead of Node12

2023-05-05

    keyboard_arrow_up