Run failed: Build Docker image - master (28f527c)

[tschwinge]

Pushed to master branch commit 28f527c "Merge commit '2961ac45b9e19523958757e607d11c5893d6368b' [#247]", and got https://github.com/Rust-GCC/gccrs/actions/runs/1272865945 in return.

[philberty]

For some reason, it's not picking up our docker hub username and password secrets from the repo. Can't seem to find much info on this.

[philberty]

This is now fixed the secrets needed to be part of the organisation not the repo for it to pick up the docker username and pass

[tschwinge]

I'm still getting these error emails whenever I push to my own https://github.com/tschwinge/gccrs: https://github.com/tschwinge/gccrs/actions/runs/1341555112, https://github.com/tschwinge/gccrs/actions/runs/1348791814, for example. I have not set up any Docker things myself, so wouldn't expect anything Docker-y processing to happen?

[tschwinge]

Also, upon pushing to my own https://github.com/tschwinge/gccrs, this seems to have triggered a resource-hungry GCC bootstrap build (which I've never configured), which failed for unrelated reasons, see https://github.com/tschwinge/gccrs/actions/runs/1348791815. I don't think it's a good use of (compute) resources, to be doing such builds for (presumably?) every GitHub fork of gccrs?

[philberty]

Good point @tschwinge I think there are options here to limit/change the jobs for forks of the repo.

[philberty]

I've added this ticket to my current plan just to keep it on my radar to see what we can do to improve the experience for forked repos.

[philberty]

https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/enabling-features-for-your-repository/managing-github-actions-settings-for-a-repository
Seem to be the relevant options but not sure what we should set.

[tschwinge]

Or this maybe: https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#example-only-run-job-for-specific-repository?

[philberty]

that looks like the perfect solution!

[philberty]

Looks like #1124 fixes this