Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ee4j-build] Weekly Eclipse - Java EE Infra
Hi,

The experimental CI instance is located here https://ci.eclipse.org/dash/. Please let us know which email address you use for your Eclipse Foundation account and we will grant you access to this instance.

Thanks.

--
Mikaël Barbero - Eclipse Foundation
IT Services - Release Engineering
📱 (+33) 642 028 039
🐦 @mikbarbero

Le 13 déc. 2017 à 16:48, Denis Roy <denis.roy@xxxxxxxxxxxxxxxxxxxxxx> a écrit :

As per today's discussion, I've added a short paragraph on the Migration Plan document that we had authored last month, based on the current direction.

https://docs.google.com/document/d/1vTdpOxmIA4cRqVsbZuw3jI-BshzLy9t3XP_k7sCwuVQ/edit#

In essence, we'll allow access to an experimental CI system so that projects may begin determining which pieces of their build system need to be altered to be run on Eclipse CBI (Common Build Infra). EE4J projects who wish to have access, please let us know which email address you use for your Eclipse Foundation account.

You can create your Eclipse account here: https://accounts.eclipse.org/

Denis


On 12/12/2017 11:42 PM, Ed Bratt wrote:

We will discuss mechanics of the transfer as well as infra structure topics

Update from meeting on Monday --

My rundown of the initial process:

  1. Prior to handing over source-code we will replace Oracle headers with Eclipse headers. These are being finalized between Oracle and Eclipse legal. There will be three options: EPL 2.0 (the large majority of files); EPL 2 with Apache Attribution; EDL 1.0 (files that were BSD licensed before).
  2. We zip these up and make them available for Eclipse IP clearance.
  3. Eclipse will provision our initial projects and repositories (we still need to settle on initial repo. names)
  4. When the initial IP clearance is done Eclipse will check the source into the repositories

At this point, full IP clearance will begin and we will need to start working on initial build CI pipelines.

We presented the CI detail for GlassFish last week, now we need to discuss the next steps the first-batch projects.

  • First, ensure that manual builds work (after code available at Eclipse)
  • 2nd start implementation and test for any CI automation using Eclipse Jenkins servers
  • If additional resources are needed (i.e. Gerrit), we will need to identify this.
  • What else, from Eclipse side is needed?

Talk with you tomorrow morning.

Thanks,


Organizer: Ed J Bratt
----------------------
Weekly coordination for Infrastructure development

Wed. 7 AM PST

Agenda e-mailed weekly
Zoom Details

https://zoom.us/my/edbratt
Conference ID: 327-448-7218
Optional telephone numbers:+1 646 558 8656 or +1 669 900 6833 US Toll
International numbers available: https://oracle.zoom.us/zoomconference?m=qtVrxXyZV-3wG0KB6QXlSz-GX8C8GCtM



_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-build

_______________________________________________
ee4j-build mailing list
ee4j-build@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ee4j-build

Attachment: signature.asc
Description: Message signed with OpenPGP

Back to the top