Contributed by the JayeX Project
Jenkins X has changed its name to JayeX
Why change the name?
In the beginning, the name Jenkins X made sense for two reasons: 1) Jenkins was used as its primary pipeline engine, and 2) development was led by CloudBees, the main contributor to Jenkins.
Nowadays, the Jenkins X name is more of a burden than a boon, as it attracts people interested in Jenkins, who are disappointed when they realize it isn’t Jenkins, nor is it closely related.
The new JayeX Technical Oversight Committee chose the name JayeX because jx has been shorthand for the project since the start—it’s now all over the codebase.
We wanted a name that was familiar without doing a full rebrand—we like our little robot. And more importantly, we didn’t want to break anyone’s custom pipelines or user flows, nor did we want to break our own.
Does anything else change?
The name is new, but the project functionalities stay the same.
JayeX understands its roots—Jenkins was a fantastic springboard to get Jenkins X off the ground, but the goals and aspirations of JayeX and Jenkins are fundamentally different, and it’s time to promote them as such.
The Jenkins integrations within JayeX were initially useful, but they are no longer widely used and their maintenance weighs heavily on the project’s contributors. By freeing up this time, we’ll be able to make JayeX even better. To that end, any remaining integrations with Jenkins should be considered deprecated and will eventually be removed.
Who should use JayeX?
JayeX is a highly customizable tool suite for cloud developers with great out-of-the-box CI/CD. If your team wants to quickly get up to speed with building applications in Kubernetes and deploy them into Kubernetes, JayeX is for you.
