FAQ and Troubleshooting
FAQ
Can I use self-hosted runners for Automation jobs?
Yes, in terms of Automation, they are called self-hosted workers.
Can I run Automation jobs on macOS or Windows?
Yes, you can do this using self-hosted workers.
Can I access the Docker daemon from my Automation jobs?
No, it's not possible.
Can I dynamically run Docker containers from my Automation jobs?
No, currently, it's not possible. The workaround is to pre-configure the required Docker containers using services.
Can I run a step in a Docker image created in a previous step?
Yes, it's possible by using Automation parameters. See an example
Do Automation jobs support Docker-in-Docker?
Docker-in-Docker is not supported out of the box.
If you use Docker compose, you can use service containers.
If you want to programmatically use the Docker API, you should run jobs using Space cloud workers or self-hosted workers.
Troubleshooting
gradlew build fails with 'Permission denied'
Symptoms:
When trying to run Gradle build using the wrapper, the job fails with Permission denied.
Possible cause:
The gradlew wrapper file doesn't have the execute permission. Typically, this happens when the wrapper is located not in the project root but in a different directory. In this case Automation is unable to set the execute flag to the file.
Solution:
Follow the instructions.