Hi, Almost 200 Eclipse projects use the build infrastructure at the Eclipse Foundation today and a lot more are coming in the next months, including EE4J projects. The IT team has been busy to plan how the infrastructure can be scaled and expanded to keep up with the high demand. Improving the utilization and efficiency of our current hardware and integrating new hardware and cloud resources are the main goals of this effort.
Therefore I’m glad to announce that CBI will be using CloudBees Jenkins Enterprise (CJE) on top of Red Hat’s OpenShift. Setting up the new environment has already started and we plan to install CJE at the end of May. What does that mean for Eclipse projects using the CI infrastructure? We don’t expect much disruption, and most of projects won’t need to change anything to their build settings. What’s the plan? Starting in a couple of weeks, all new projects will get a CJE JIPP instead of a regular JIPP. Soon after, we will start migrating existing JIPPs by calling for volunteer guinea pigs. Once this is done and we get confident in the process, we will gradually ramp up the migration and move all remaining projects over to CJE. There is no set timeline, but we aim to move most projects to CJE before the end of the year. We will populate the Migration FAQ on the Eclipse wiki (https://wiki.eclipse.org/CBI/CJE_Migration_FAQ) in the next few days. Feel free to let us know if you have any concerns or questions in the meantime. As part of this effort, we would like to thank both CloudBees and Red Hat for their generous donations in the form of software and support. Regards, Fred -- Frederic Gurr Release Engineer Eclipse Foundation _______________________________________________ cross-project-issues-dev mailing list [email protected] To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
