Self-hosted workers are billed for each minute of work based on your Space subscription plan. Once the job is finished, the agent reports results to Automation and deletes the temporary directory. After the suitable worker is found, Automation initiates job run.Ĭreates a temporary directory on the host machine,ĭownloads the project source code including the Automation script, When a job with at least one host step is triggered, Automation will randomly choose a worker suitable for the job. Learn more about how to specify job run environment.

To run a job on the self-hosted worker, you should use the host blocks for job steps: The only requirement is access to your Space instance. This means that no specific network configuration is required on the agent side.

The agent uses pull communication with Space: The agent initiates the communication, and Space only responds to incoming requests. The running agent will regularly send its status to Space. Learn moreĪfter you register a self-hosted worker in Space, you should run the agent on the host machine. zip archive or as a part of a specially-prepared Docker image. The self-hosted worker agent is a Java application that is distributed either as a.

Using more powerful hardware configurations than those provided by Space Cloud.

For example, building iOS and macOS applications on Apple hardware, running ML tasks on GPUs, and so on. Self-hosted workers let you perform CI/CD workflows that are not possible with containers. The self-hosted worker connects to Space Automation, gets jobs and the project source code, runs the jobs, and reports results back to Space. A self-hosted worker is a lightweight agent that you can run on your own machine on Windows, Linux, or macOS.

Download jetbrains space on premise