|
|
| (20 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| − | = EE4J Build =
| + | #REDIRECT [[Jenkins]] |
| − | This page gives an overview of the build setup and infrastructure for EE4J projects.
| + | |
| − | | + | |
| − | == Build infrastructure overview ==
| + | |
| − | Every EE4J project can request it's own Jenkins instance. All sub projects of a project share a single Jenkins instance.
| + | |
| − | | + | |
| − | All EE4J JIPPs will be hosted on CloudBees Jenkins Enterprise (CJE) / CloudBees Core infrastructure. Projects that still have a Jenkins instance on our old infrastructure will be migrated in Q4 2018. Jenkins instances running on ci.eclipse.org (e.g. https://ci.eclipse.org/grizzly) are currently hosted on the old infrastructure. Jenkins instances running on jenkins.eclipse.org (e.g. https://jenkins.eclipse.org/glassfish) are hosted on our new infrastructure (CJE/Core). Please note: the sub domains ci.eclipse.org and jenkins.eclipse.org will be unified at a later date.
| + | |
| − | | + | |
| − | Please see the [https://docs.google.com/spreadsheets/d/1O2NA6YddYQy34riTabQd_lkNwwFzKq1HevxCJYNXrv4 EE4J Project Provisioning Status Google Doc] for details.
| + | |
| − | | + | |
| − | === How to requests a Jenkins instance? ===
| + | |
| − | Please [https://bugs.eclipse.org/bugs/enter_bug.cgi?product=Community&component=CI-Jenkins&short_desc=JIPP%20Request file a bug] file a bug against Eclipse Foundation > Community > CI-Jenkins to request your project's own instance. Make include the name of your project and ensure your project lead can +1 the request.
| + | |
