You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ossie.apache.org by Yong Zheng <yz...@apache.org> on 2026/07/20 04:29:59 UTC

Discussion: add CI for various components

Hello all,

As we are getting more and more PRs, is it a good time for us to consider adding CI for some basic checks? Taking one example, there are PRs around python implementation of the spec as well as different converters, but there is no CI for any of them. Reviewer would either need to run the test locally or trust the devs who did the diligent of validation.

One potential concern from me for introducing CI at this stage is diff module/tools requires different dependency at this stage. For example, not all converters support same min version of python or java. Until UV change is in, we would need different commands for diff module/tools for running pytest.

Thanks,
Yong Zheng

Re: Discussion: add CI for various components

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Fully agree!

On Mon, Jul 20, 2026 at 5:53 PM Quigley Malcolm <q...@quigleymalcolm.com> wrote:
>
> Howdy,
>
> Just want to +1 on the idea of CI workflow per module. In my mind, this is the most high value initial CI setup.
>
> Best,
> Quigley
>
> On Sunday, July 19th, 2026 at 11:35 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>
> > Hi
> >
> > I was planning to add CI but I wanted to have consistency/stability between
> > modules.
> > That’s the challenge about Ossie: we have the spec and the converters.
> > Each converter is independent from another with different technologies,
> > dependencies, frameworks. And it’s totally fine.
> > I don’t see problem to have a CI workflow for each converter/module.
> > It’s a bit what we do in Arrow.
> >
> > So even if it’s more effort, I think we could have CI workflow for each
> > converter.
> > It’s what I was planning to start. A bit related is the release process. I
> > will start a thread about that.
> >
> > Regards
> > JB
> >
> > Le lun. 20 juil. 2026 à 06:30, Yong Zheng <yz...@apache.org> a écrit :
> >
> > > Hello all,
> > >
> > > As we are getting more and more PRs, is it a good time for us to consider
> > > adding CI for some basic checks? Taking one example, there are PRs around
> > > python implementation of the spec as well as different converters, but
> > > there is no CI for any of them. Reviewer would either need to run the test
> > > locally or trust the devs who did the diligent of validation.
> > >
> > > One potential concern from me for introducing CI at this stage is diff
> > > module/tools requires different dependency at this stage. For example, not
> > > all converters support same min version of python or java. Until UV change
> > > is in, we would need different commands for diff module/tools for running
> > > pytest.
> > >
> > > Thanks,
> > > Yong Zheng
> > >
> >

Re: Discussion: add CI for various components

Posted by Quigley Malcolm <q...@quigleymalcolm.com>.
Howdy,

Just want to +1 on the idea of CI workflow per module. In my mind, this is the most high value initial CI setup.

Best,
Quigley

On Sunday, July 19th, 2026 at 11:35 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:

> Hi
> 
> I was planning to add CI but I wanted to have consistency/stability between
> modules.
> That’s the challenge about Ossie: we have the spec and the converters.
> Each converter is independent from another with different technologies,
> dependencies, frameworks. And it’s totally fine.
> I don’t see problem to have a CI workflow for each converter/module.
> It’s a bit what we do in Arrow.
> 
> So even if it’s more effort, I think we could have CI workflow for each
> converter.
> It’s what I was planning to start. A bit related is the release process. I
> will start a thread about that.
> 
> Regards
> JB
> 
> Le lun. 20 juil. 2026 à 06:30, Yong Zheng <yz...@apache.org> a écrit :
> 
> > Hello all,
> >
> > As we are getting more and more PRs, is it a good time for us to consider
> > adding CI for some basic checks? Taking one example, there are PRs around
> > python implementation of the spec as well as different converters, but
> > there is no CI for any of them. Reviewer would either need to run the test
> > locally or trust the devs who did the diligent of validation.
> >
> > One potential concern from me for introducing CI at this stage is diff
> > module/tools requires different dependency at this stage. For example, not
> > all converters support same min version of python or java. Until UV change
> > is in, we would need different commands for diff module/tools for running
> > pytest.
> >
> > Thanks,
> > Yong Zheng
> >
> 

Re: Discussion: add CI for various components

Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
Hi

I was planning to add CI but I wanted to have consistency/stability between
modules.
That’s the challenge about Ossie: we have the spec and the converters.
Each converter is independent from another with different technologies,
dependencies, frameworks. And it’s totally fine.
I don’t see problem to have a CI workflow for each converter/module.
It’s a bit what we do in Arrow.

So even if it’s more effort, I think we could have CI workflow for each
converter.
It’s what I was planning to start. A bit related is the release process. I
will start a thread about that.

Regards
JB

Le lun. 20 juil. 2026 à 06:30, Yong Zheng <yz...@apache.org> a écrit :

> Hello all,
>
> As we are getting more and more PRs, is it a good time for us to consider
> adding CI for some basic checks? Taking one example, there are PRs around
> python implementation of the spec as well as different converters, but
> there is no CI for any of them. Reviewer would either need to run the test
> locally or trust the devs who did the diligent of validation.
>
> One potential concern from me for introducing CI at this stage is diff
> module/tools requires different dependency at this stage. For example, not
> all converters support same min version of python or java. Until UV change
> is in, we would need different commands for diff module/tools for running
> pytest.
>
> Thanks,
> Yong Zheng
>