#github-actions (2023-05)
Discussions related to GitHub Actions
2023-05-01
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
?
Maybe consider centralizing the management of repos. That way to delete a repo, you delete it from the configuration, rather than click ops.
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/
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 Congrats on the successful migration! Plz open source this implementation, I would like to see how this works under the hood
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 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).
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
a demo would be great too, looking forward to the release!
@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
@Sudhish KR any updates on this stuff?
2023-05-02
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
Not enough details
Raw error logs would be best.
2023-05-03
2023-05-04
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
2023-05-05
2023-05-09
Introducing Actions on the Repository view on GitHub Mobile Introducing Actions on the Repository view on GitHub Mobile
Introducing Actions on the Repository view on GitHub Mobile
hi folks, curious how you maintain a list of GH repo labels and then sync it to all repos, is anyone doing that differently than say https://github.com/marketplace/actions/label-sync-action ?
I think a better long-term approach is https://github.com/github/safe-settings
Because after you sync labels, what about branch protections, merge behaviors, etc
interesting, wasn’t aware of it. I shall have a look and see if my Org admin approves it so that i can use it for only a set of repos. Thx a bunch Erik !
2023-05-10
GitHub Actions – Actions Runner Controller Public Beta GitHub Actions - Actions Runner Controller Public Beta
GitHub Actions - Actions Runner Controller Public Beta
2023-05-11
Edit workflow files on GitHub mobile Edit workflow files on GitHub mobile
Edit workflow files on GitHub mobile
2023-05-22
GitHub Actions Importer – Bamboo Server and Data Center Migrations (Public Beta) GitHub Actions Importer - Bamboo Server and Data Center Migrations (Public Beta)
GitHub Actions Importer - Bamboo Server and Data Center Migrations (Public Beta)
2023-05-24
Hi, can anyone recommend a tool for graphing GHA dependencies? What I mean is I have a workflow in repo A that calls a reusable workflow in repo B that calls a number of composite actions and I want to see the whole flow as a graph
2023-05-30
Hi, anyone knows of a different action actions-ecosystem/action-get-merged-pull-request
which does implement similar functionality as used by CloudPosse team ? Unfortunately the action hasn’t been maintained and it throws some deprecated warnings
@DaniC (he/him) Hello. At the moment we had not any cases when we need that functionality. Thanks for pointing that GH actions, I guess it could be useful for us in near future.
@Igor Rodionov the point is that our actions are calling an action that is unmaintained and throwing deprecated warnings. We need to get this fixed or find an alternative.
@DaniC (he/him) we’ll get this fixed or find an alternative.
Sure @Gabriela Campana (Cloud Posse) , i went ahead with the mentioned action and is all working fine for me.
hi Folks, i’m not very familiar with renovate so please excuse my silly q:
Can you please help me understand the need for https://github.com/cloudposse/terraform-aws-vpn-connection/blob/main/.github/renovate.json#L4 ?
Context:
Am chasing the flow of how you use auto-release.yml (config for release-drafter) as part of various reusable workflows (2 or 3 layers of abstractions), however i got stuck and wonder if renovate is getting involved into working out the next sermVer.
Read the renovate docs but didn’t help much. Thx
":preserveSemverRanges"
terraform {
required_providers {
aws = "~> 3.0"
}
}
Renovate is not related to release drafter in any way. This line just states that renovate will upgrade within semver range specified in a dependency - it will obey things like ^
ah i see, much thanks @Max Lobur (Cloud Posse) .