Orka 2.4.x content
This page has not been updated to reflect the changes introduced in Orka 3.0. Some of the information might be outdated or incorrect. Use 2.4.x to 3.0.0: API Mapping and 2.4.x to 3.0.0: CLI Mapping to figure out the correct endpoints and commands.
Orka performance depends on the actual builds running on your virtual machines. For detailed performance reports from beta and performance testing, contact us.
The performance of Jenkins builds depends on the connection speed between the master and the slave and the size of the artifacts transferred over this connection. If you are transferring large-sized artifacts over a slow connection, the build is also slow.
The location of the slave (on-premises or in the cloud) does not affect the connection speed.
You can use the Orka API to create any integrations with third-party tools yourself. For a complete list of the plugins and integrations provided and supported by the MacStadium team, see Tools & Integrations.
Yes. You can set up multiple Jenkins masters to spin up ephemeral agents in a single Orka environment. However, keep in mind that the resources of the environment are limited and you cannot deploy more VMs than the available resources allow.
Currently, the default Orka cluster comes with three nodes. This provides a reliable, highly available setup. You can scale up as much as you need. To scale up, contact us.
Updated 5 days ago