Re: [incubation] Keyple - Publishing to Maven Central

[Mikaël Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx>]

No, we only provide CI instances to build Open Source code of Eclipse Foundation projects. 

Mikaël Barbero 

Team Lead - Release Engineering | Eclipse Foundation

📱 (+33) 642 028 039 | 🐦 @mikbarbero

Eclipse Foundation: The Platform for Open Innovation and Collaboration

Le 27 sept. 2018 à 14:41, Olivier Delcroix <odelcroi@xxxxxxxxx> a écrit :

Thanks for your answers. 

I'm concerned about the code that we haven't plan to realease publicly nor to publish to the Eclipse Github Repos, would it be possible to manage it with the Jenkins JIPP too? 

Bests,

On Thu, Sep 27, 2018 at 12:07 PM Mikaël Barbero <mikael.barbero@xxxxxxxxxxxxxxxxxxxxxx> wrote:

As you already said, we provide full support for publishing to Maven Central from JIPP. 

Unfortunately, while we do support TravisCI, we don't support CircleCI (CircleCI wants write access to code. We can't allow that). It also means that as soon as your Github repos will be transfered to Eclipse, you won't be able to use CircleCI.

To make it thorough, even with Travis you won't be able to push artifacts from Travis to Jenkins or pull from Jenkins to Travis.

Cheers,

Mikaël Barbero 

Team Lead - Release Engineering | Eclipse Foundation

📱 (+33) 642 028 039 | 🐦 @mikbarbero

Eclipse Foundation: The Platform for Open Innovation and Collaboration

Le 27 sept. 2018 à 11:56, Mickael Istria <mistria@xxxxxxxxxx> a écrit :

Hi Olivier,

Glad to see our paths crossing again, it's been a while!

Have you considered using the OSSHR sonatype Nexus instance, that can
host any OSS project and mirror content to Central? That seems much
simpler than going through Jenkins and CBI@xxxxxxxxxxx if you're
already using external services.
Or maybe the EclipseCBI Nexus instance can be accessed externally and
mirror to Maven Central, making it on par with OSSHR ?

Cheers,

On 9/27/18, Olivier Delcroix <odelcroi@xxxxxxxxx> wrote:

Dear Eclipse members,

At Calypso Network Association, we are building the Keyple SDK
<https://keyple.org/> to help public transport organizations (and other
services) to share smartcard/NFC among cities/countries.

We recently joined the Eclipse foundation, so we would like to leverage
the possibilies offered by the CBI.
After reading the wiki, I still have doubt about Maven Artifact Publishing.

This is our CI context :
- Right now we are using our own Github account + Circle CI to build our
jars and android aars. Artifacts are then published back to Github, we do
not publish on Maven nor Nexus yet. Apart from the Open Source Keyple SDK
we
have others projects with CI workflow on CircleCI, those projects are not
meant to be public.

I understood that we can publish to maven central through our (not
configured yet) jenking JIPP.
Can we build our artifacts with CircleCI, send them to Jenkins and then
publish to Maven?

Thanks in advance for your answers :-)
Olivier

-- 
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red Hat Developers <https://developers.redhat.com/>
_______________________________________________
incubation mailing list
incubation@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation

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

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

Attachment: signature.asc
Description: Message signed with OpenPGP