Add shellcheck test action #108
Conversation
miigotu
force-pushed
the
docker-shellcheck
branch
4 times, most recently
from
846798d to
4aae8de
Compare
miigotu
force-pushed
the
docker-shellcheck
branch
from
07ad006 to
d00acf1
Compare
…turns 686 Signed-off-by: miigotu <[email protected]>
miigotu
force-pushed
the
docker-shellcheck
branch
from
14f23de to
74e2cdf
Compare
Signed-off-by: miigotu <[email protected]>
Signed-off-by: miigotu <[email protected]>
|
Looks like the Docker build is running out of disk space. Can you allocate more to it? |
|
@zeldin nope, they have a pre set allotment for the runner containers. I think I need to not cache locally for layer caching of buildx, and if that isn't enough I will have to separate different architectures into different builds like before buildx existed. I worked on it all day yesterday, I'll try some more later on. |
miigotu
force-pushed
the
docker-shellcheck
branch
from
b1c0849 to
456454a
Compare
…ce we aren't building for either. Add action to manually delete old workflows
miigotu
force-pushed
the
docker-shellcheck
branch
from
456454a to
94783ee
Compare
|
@zeldin, fixed. Just need secrets set for docker username/pass and enable ghcr for ps3dev I'd also like to pull the toolchains out of each image and make them available as tar artifacts for download right from the build, and use the action that makes releases |
|
Lol I think I figured out why the push fails for me, docker config is cached between all my builds even on other orgs, so it tries to login to ps3dev/ps3dev with my credentials for sickchill/sickchill ;) I had the same problem over there and fixed it, will update this PR soon as I solve an issue upgrading my other packages on synology. |
Signed-off-by: miigotu [email protected]