Available images
You can select one of two images per repository.| Image | Environment | Best for |
|---|---|---|
| Default Image | General-purpose environment with common languages and runtimes preinstalled, including Python, Node.js, Java, Go, Ruby, PHP, and .NET. | Most repositories. |
| Universal 6 | A newer build of the same environment on Ubuntu 24.04, with up-to-date versions across every included language and runtime. | Repositories that need a more recent toolchain than the default provides. |
Default Image
The standard Overcut agent environment. It covers the most common stacks and is the right choice unless your project needs a newer toolchain version than it provides.Universal 6
A newer, modern build of the universal environment on Ubuntu 24.04. It refreshes the whole toolchain, bringing more recent versions of every included language and runtime (Python, Node.js, Java, Go, Ruby, PHP, C/C++, and .NET). Choose it when your repository depends on a language or SDK version that the default image predates, for example a newer Python interpreter, an updated Node.js LTS, or a recent .NET release.If your project requires a language or runtime version newer than the default image provides, agents in the default image can still write and commit code, but their build and test checks fail. Selecting Universal 6 gives agents the matching versions to validate their changes.
Custom and upcoming images
Overcut builds and maintains the available images, and adds newer universal images as they become available, so your repositories get updated toolchains without any maintenance on your side. If neither image fits your repository, for example you need a toolchain that is not preinstalled, or you want to run your own custom image, contact Overcut. We work with you to add a compatible image and make it selectable for your workspace.Selecting an image
The Agent Image is set per repository. Other repositories keep the workspace default.Open repository settings
Go to the repository’s configuration panel under Repositories, or the integration that connected it.
How Overcut selects the image for a run
Overcut resolves the agent image once, when a run starts, and uses it for the whole run. It checks, in order:- The trigger repository. If the repository that triggered the run has an Agent Image set, that image is used.
- Linked code repositories. If the trigger repository has no image set, Overcut checks the code repositories linked to it and uses the first one that does. This is common for ticket repositories in Jira or Azure DevOps, where the ticket has no code to build and the image belongs to the linked code repository.
- Workspace default. If none of the above set an image, the run uses the workspace default.
Handling conflicts
If a run involves several linked code repositories that set different images, Overcut uses the first one by the order above and records a warning so you can spot the mismatch. To keep the outcome predictable, set the same image across the related repositories, or set it on the trigger repository so it takes precedence.The image is chosen when the run starts, so a code repository must be the trigger repository or already linked to it for its image to apply. A repository discovered only later in the run, during repository identification, cannot change the image for that run.