Help moving legacy build hosts to current Jenkins
agent8 is free and open source, and you can roll it out yourself: the README has the install script and an Ansible playbook, and GitHub issues are the place for bugs.
Write to us when that is not enough:
- Your hosts run AIX, Solaris or HP-UX. agent8 has not been verified there yet. We run it with you on your platform as a pilot, and fix what breaks.
- You need to know whether your plugins work. Plugins that run code on agents, such as git, Maven or credentials binding, are the main open risk on a Java 8 agent. We check the ones your builds use.
- You have many hosts, or you need support you can put in a contract.
- You are not sure which path each host needs. Some can run a normal Java 21 agent, some builds can move into a container, and the rest need agent8.
The first answer is free and in writing: for each host, the highest Java it can run with the vendor source for it, the path that fits, and what we have not verified for your platform. If every host you have can run a normal agent, that is what we will tell you. The background is in Jenkins requires Java 21. What happens to your AIX 7.1 and RHEL 6 build hosts?
Leave out hostnames, IP addresses, credentials and anything else you would not put in an email to a stranger. Operating system versions and what each host builds are enough.
Tell us about your build hosts
Prefer to write it yourself? Email hello@keelinfra.io with your Jenkins version and the OS versions of the hosts that hold it back.