Jenkins X changes name to JayeX!
Categories:
Background
During the early days of Jenkins X the Jenkins part of the name made sense for two reasons: Jenkins was used as the main pipeline engine and the development was done within CloudBees, the company that also is the main developer of Jenkins.
Why change?
Nowadays the Jenkins X name is more of a burden than boon marketing wise: It attracts people interested in Jenkins, who will dissapointed. It detracts people that are looking for an alternative to Jenkins, who might actually find what this project offers attractive.
What happens now?
Technically nothing happens immediately. We will by and by replace the Jenkins X name with JayeX within the project without affecting the functionality. Any remaining integrations with Jenkins should be seen as deprecated though and will eventually be removed.
We will renew our marketing efforts using the new name.