Discussions related to GitHub Actions
Quick question for you all, say I have two paths
on: push: paths: X Y
Is there any specific variables that actually contain the folder path that actually triggers the “on push” call in Github Actions? Say I want it to build a specific application in folder X and need to navigate this monorepo to actually do so
I think you want this one:
GITHUB_WORKSPACE The default working directory on the runner for steps, and the default location of your repository when using the checkout action. For example, /home/runner/work/my-repo-name/my-repo-name.
So if you want to build on
X, you can checkout the code and do:
Yeah workspaces + looking into matrix seems to help
GitHub Actions: Inputs unified across manual and reusable workflows GitHub Actions: Inputs unified across manual and reusable workflows
GitHub Actions: Inputs unified across manual and reusable workflows
GitHub Actions: macOS 12 for GitHub-hosted runners is now generally available GitHub Actions: macOS 12 for GitHub-hosted runners is now generally available
GitHub Actions: macOS 12 for GitHub-hosted runners is now generally available
Is there a particular scripting language that is recommended to use as an alternative to unwieldy BASH scripts in github actions?
Ideally I’d prefer to use python - curious to know how people have found support for that compared to shell
write better bash — if I’m doing something complex then I end up creating a Docker image and run the step as that
@Darren Cunningham I’m new to all of this, I wrote a pipeline for my work in jenkins but it’s never had quite the performance I want it to have so I’m thinking about moving over to gha. Where do you get to those steps where you can write steps in bash / python make docker images etc. I shutter to say it but that stuff seems more straight forward in jenkins
if performance is your key decision factor than GHA might not solve the problem. Hosted runners are not that powerful, you might have to use self-hosted runners; which is a pile of work alone.
Creating the Docker image is it’s own workflow which is pretty much just docker/build-push-action — but I push to a private ECR. Authentication to from GHA uses OIDC with aws-actions/amazon-ecr-login. Doing all of that is no small feat.
Jenkins to GHA migration isn’t an easy one, the primary decision factor for me was not having to manage Jenkins itself. System updates, patches, etc. We were ok with pipelines taking a bit longer to startup/run in order to not have to manage that.
List and delete caches in your Actions workflows List and delete caches in your Actions workflows
List and delete caches in your Actions workflows
Anyone else here affected by the GitHub Actions outages? We use actions for our deployments so this is a real concern. How are other teams dealing with this?
We basically wait until they no longer have issues
We like to subscribe to the rss feed of that page in slack to keep up to date with it
/feed subscribe <https://www.githubstatus.com/history.rss>
HN updates faster than GitHub Status, see the second post
yep we’ve seen this with aws too
it’s totally fair, we go crying to the internet while they’re scrambling to figure out (1) if it’s a real issue (2) how many customers are really impacted (3) make the executive decision to publicly disclose it (4) have the grammar and spelling of the post checked (5) post it. all that takes a whole lot longer than a HN rage post.