Spent an entire afternoon dealing with setting up #GiteaActions #ci for #unity3d projects in my local instance. Man do I hate dealing with proprietary software in docker containers, nothing ever just works, everything licence related always seems to require workarounds for workarounds to get working.
The fact that someone at #unity thought that personal licence users couldn't possibly need to use unity from CLI also didn't help.
Does someone has an idea why gitea action recently got issues with complete job phase? The job itself runs fine. On the action host all containers are stopped and properly decommissioned but the job seems to be stuck and ends with an error after some time.
tags for visibility: #gitea #GiteaActions #selfhosted
@forgejo @gitea what is the preferred API to fetch unstarted actions?
I want to wake my #CI computer when a job is pending, but I'm not sure which call I should use.
I found the protobuf API, but it's not documented enough that I know how to use it :/ E.g. is fetching the same as accepting? What are the URLs?
https://gitea.com/gitea/actions-proto-def/src/branch/main/proto/runner/v1/messages.proto
Hey, #docker fedi, is there any way for me to mount a folder from one docker container into a sibling container?
I'm trying to avoid docker in docker by using sibling containers using a shared docker daemon socket, but some premade scripts that originally weren't supposed to run in a docker container really want to spawn children containers and mount files into them, which then turn into a mess of non existent paths in the host file system.
I'm starting to understand why people say to stay as far away from #docker in docker as possible...
Check out my latest post on my personal blog about checking out a new jazz club in the NC Triangle area:
I'm also super excited to announce I got CI/CD working with my #gitea instance and #GiteaActions still using #Hugo and #Netlify