[ee4j-build] Notes from build team meeting (Mar. 7, 2018)

[Ed Bratt <ed.bratt@xxxxxxxxxx>]

Jignesh reported for GlassFish build porting -- GF Builds (Docker 
Container Build/Test) still stuck / blocked because we cannot share 
access between master and slave systems. Last week's suggestion to use 
CI/CD plugin appears to require too much work. Requested that we be 
allowed to use NFS. Legacy design choice was to avoid CI/CD specific 
plugins. All written in scripts now. Would likely require that these 
builds are pinned to certain hosts. Accepted by Denis -- as a temporary. 
Longer-term we can look at a re-engineer this at a later date. will use 
Eclipse infra-slaves. Can re-engineer as a community effort. Mikael 
confirms this is okay. But will run on CentOS (Docker should isolate). 
This should remove this road-block. Jignesh to file an Eclipse issue.

Dmitry/Lukas/Jan -- Question: what is the status of EclipseLink 
repository migration. https://bugs.eclipse.org/bugs/show_bug.cgi?id=531036
Jersey should be cleared for transfer soon. Want to start migrating 
CI/CD. Will need to use the -dash instance until Jersey project is 
provisioned.  Should be easy to easy to transfer. Jan Supol will take 
lead on this and work with Lukas. Will use DASH (test) env. to make test 
builds for Jersey. Once Jersey is cleared, will move to final home.

EclipseLink -- things were working well, but then started to fail 
(timeout problem). Eclipse to continue monitoring and attempt to resolve.

Yamini / MQ -- working in parallel to generate both exit build and dash 
instance build porting