|
|
| (19 intermediate revisions by 4 users not shown) |
| Line 1: |
Line 1: |
| − | This page gives an overview of the build setup and infrastructure for EE4J projects.
| + | #REDIRECT [[Jenkins]] |
| − | | + | |
| − | == 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.
| + | |
| − | | + | |
| − | === Deployment to OSSRH / Maven Central ===
| + | |
| − | Deploying artifacts to OSSRH (OSS Repository Hosting provided by Sonatype) requires an account at OSSRH. It is also required to sign all artifacts with GPG. The Eclipse IT team will set this up for the project.
| + | |
| − | | + | |
| − | Here are the required steps to configure your Jenkins build job for deployment to OSSRH:
| + | |
| − | | + | |
| − | # Inject settings-security.xml file into .m2 directory [[File:InjectSettingsSecurity.png]] | + | |
| − | # Insert trustedkeys.gpg as secret file in job [[File:InjectSecretFile.png]]
| + | |
| − | | + | |
| − | | + | |
| − | '''Please note this is currently a workaround and will be improved in the future.'''
| + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | | + | |
| − | [[Category:CBI]] [[Category:Releng]] [[Category:Jenkins]]
| + | |
