Just few more notes from my side:
JsonP production Jenkins is running on
https://ci.eclipse.org/jsonp/, is seems to be OK.
Frederic also transfered jobs there. I modified the build job to
use proper repository - github.com/eclipse-ee4j/jsonp.git and
removed snapshot deploy until artifacts deployment is solved.
Artifacts deployment to maven central is being solved on bugzilla
https://bugs.eclipse.org/bugs/show_bug.cgi?id=530304
and as was already mentioned, is blocked by Oracle org.glassfish group Id.
Tomas
Dne 28/02/18 v 21:31 Ed Bratt
napsal(a):
Sorry
about the confusing subject that accompanied the original e-mail.
On 2/28/2018 9:54 AM, Ed Bratt wrote:
Ed started the meeting a few minutes late.
Apologies if anyone gave up before that.
Jignesh gave an update on progress with the GlassFish build
experiments. They are working to re-engineer the build
foundation since Eclipse uses cloud based compute nodes. With
assistance from Eclipse IT folks earlier road-blocks have been
discussed (e.g. using SSH and/or NFS mount points to transfer
components between master and slaves. Currently re-implementing
this to use Jenkins "copy-artifact" plugin.
Frederic confirmed that the production environment for JSON P.
is configured. They have progressed as far as deploying to maven
central. setting up account for deployment to maven central.
Oracle needs to decide what to do with the maven artifact
domains.
Yamini raised concern about variability in build/test time.
(most are 5 mins. one took over 50 minutes). Frederic is looking
at build history to see what else was happening. This is similar
to previous reports made by Dmitry. Hopefully Frederic can
triangulate this with whatever else is happening on those
machines. 10x variability is probably going to be difficult for
our CI scripts to handle.
Find-bugs plugin is installed. Questions about configuration
differences between what we have internal to Oracle vs. config.
at Eclipse. Yamini will update wiki how-to pages once she's
successfully got this working.
No one from Prague team was able to join, but there were updates
to the internal Eclipse Org CI/CD wiki page. This was shared
internally to Oracle team after the meeting. (With apologies,
this is an Oracle internal wiki.) Once we start accumulating
operational recipes (as opposed to migration based commentary)
we need to post these procedures in a public location.
Thanks,
-- Ed
_______________________________________________
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
