Re: [jakartaee-spec-project-leads] Getting started with CI/Jenkins - Jak

["Kevin Sutter" <sutter@xxxxxxxxxx>]

Scott,
I would reference
this first:  https://wiki.eclipse.org/CBI
And, of course,
the overall Project Handbook:  https://www.eclipse.org/projects/handbook/

Once your get
your Jenkins instance in place, then it's up to your project what type
of build scripts, etc you wish to host.  You can go simple and just
enter your scripts into the Build configuration, or you can put more control
in place and put your scripts into github.  I'd probably suggest starting
simple and just using the Build configuration until you get your scripts
nailed down and working.  And, then maybe consider moving them to
an scm.

There is no tight
CI/CD with the TCK integration.  Of course, for Jakarta EE 9, the
overall Platform TCK will be the "blessed" TCK.  So, if
you do decide to have a separate TCK in your own repo (ala json-b and json-p),
you still have to ensure that your TCK will integrate with the Platform
TCK.

HTH!

---------------------------------------------------
Kevin Sutter 
STSM, MicroProfile and Jakarta EE architect @ IBM
e-mail:  sutter@xxxxxxxxxx     Twitter:  @kwsutter
phone: tl-553-3620 (office), 507-253-3620 (office)    
LinkedIn: https://www.linkedin.com/in/kevinwsutter



From:
       "Scott
Kurz" <skurz@xxxxxxxxxx>
To:
       "JakartaEE
Spec Project Leadership discussions" <jakartaee-spec-project-leads@xxxxxxxxxxx>
Date:
       03/17/2020
10:06
Subject:
       [EXTERNAL]
[jakartaee-spec-project-leads] Getting started with CI/Jenkins -  
     Jakarta Batch
Sent
by:        jakartaee-spec-project-leads-bounces@xxxxxxxxxxx

---

Hi, I'm looking for pointers or first
steps for getting the Jakarta Batch started using some of the CI / Jenkins
pipelines used by other projects.

To date, I've been releasing the batch-api project manually via
my own personal credentials, not via CI credentials. Haven't had time to
look more, however now we have some volunteers offering to help.
That said, we already use the ee4j project parent POM, and use the nexus-staging-maven-plugin,
so that piece at least is in place.

In addition, another concern looking ahead is how to fit the TCK execution
into the pipeline. I'm happy to start without worrying about the TCK at
all, for now... I would like to look to converting the TCK to Arquillian
format later in the year. My only question is does that approach prevent
us from leveraging any other EE4J common function other projects are using?
Are other pipelines tightly coupled to TCK execution? 

I realize there are some materials out there, e.g: https://www.youtube.com/watch?v=J5qLpTcRgH0
but anyway thought I'd ask for direction before diving in ourselves.

Thank you,
------------------------------------------------------
Scott Kurz
WebSphere Batch and Developer Experience
skurz@xxxxxxxxxx
--------------------------------------------------------_______________________________________________
jakartaee-spec-project-leads mailing list
jakartaee-spec-project-leads@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/jakartaee-spec-project-leads