You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kie.apache.org by Jan Šťastný <js...@apache.org> on 2024/01/31 12:47:10 UTC

[HEADS UP] Drools SNAPSHOT dependency in OptaPlanner requires pipeline changes

Hello,

With the recent switch to fixed snapshot version and OptaPlanner dependency
on Drools snapshots, the CI builds should be adjusted.

These are the problems:
1. OptaPlanner builds rely on availability of Drools snapshots in Nexus
repository, which prevents from running OptaPlanner PR checks with contents
of Drools main branch. We should include Drools into OptaPlanner
build-chain configuration, so that Drools main branch (or a matching PR
branch in case of cross repository PR ensemble) is built locally before the
actual OptaPlanner build (must have for FDB, and branch builds = nightly).
2. At the moment a PR targeted to Drools is not validated by an OptaPlanner
build.
This is a difference compared to how Drools -> Kogito relation is handled
at the moment, where a Drools PR check runs also Kogito projects as
downstream verification of the changes. We should include OptaPlanner into
Drools build-chain configuration, so that OptaPlanner is built with
relevant Drools changes.
3. Buildchain configurations for Drools and OptaPlanner need adjustment of
mappings, thanks to unified versioning of snapshots (and eventually
releases) we can drop any custom mapping between versions of individual
projects.
4. And thanks to quarkus3 upgrade finished in OptaPlanner, we can drop
optaplanner-quickstarts '8.x' branch from pipeline configuration and build
'development' instead.

While this might seem complicated, I think this is a quick win, without the
need to "merge" all projects into one pipeline, which is IMO a bigger topic.

Regards
Jan

Re: [HEADS UP] Drools SNAPSHOT dependency in OptaPlanner requires pipeline changes

Posted by Tibor Zimányi <tz...@apache.org>.
+1, thanks Jan.

Tibor

Dňa st 31. 1. 2024, 14:12 Luca Molteni <lm...@redhat.com> napísal(a):

>
>
> > On 31 Jan 2024, at 13:47, Jan Šťastný <js...@apache.org> wrote:
> >
> > Hello,
> >
> > With the recent switch to fixed snapshot version and OptaPlanner
> dependency
> > on Drools snapshots, the CI builds should be adjusted.
> >
> > These are the problems:
> > 1. OptaPlanner builds rely on availability of Drools snapshots in Nexus
> > repository, which prevents from running OptaPlanner PR checks with
> contents
> > of Drools main branch. We should include Drools into OptaPlanner
> > build-chain configuration, so that Drools main branch (or a matching PR
> > branch in case of cross repository PR ensemble) is built locally before
> the
> > actual OptaPlanner build (must have for FDB, and branch builds =
> nightly).
> > 2. At the moment a PR targeted to Drools is not validated by an
> OptaPlanner
> > build.
> > This is a difference compared to how Drools -> Kogito relation is handled
> > at the moment, where a Drools PR check runs also Kogito projects as
> > downstream verification of the changes. We should include OptaPlanner
> into
> > Drools build-chain configuration, so that OptaPlanner is built with
> > relevant Drools changes.
> > 3. Buildchain configurations for Drools and OptaPlanner need adjustment
> of
> > mappings, thanks to unified versioning of snapshots (and eventually
> > releases) we can drop any custom mapping between versions of individual
> > projects.
> > 4. And thanks to quarkus3 upgrade finished in OptaPlanner, we can drop
> > optaplanner-quickstarts '8.x' branch from pipeline configuration and
> build
> > 'development' instead.
> >
> > While this might seem complicated, I think this is a quick win, without
> the
> > need to "merge" all projects into one pipeline, which is IMO a bigger
> topic.
> >
> > Regards
> > Jan
>
> +1
>
> Thanks
>
> Luca
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
> For additional commands, e-mail: dev-help@kie.apache.org
>
>

Re: [HEADS UP] Drools SNAPSHOT dependency in OptaPlanner requires pipeline changes

Posted by Luca Molteni <lm...@redhat.com>.

> On 31 Jan 2024, at 13:47, Jan Šťastný <js...@apache.org> wrote:
> 
> Hello,
> 
> With the recent switch to fixed snapshot version and OptaPlanner dependency
> on Drools snapshots, the CI builds should be adjusted.
> 
> These are the problems:
> 1. OptaPlanner builds rely on availability of Drools snapshots in Nexus
> repository, which prevents from running OptaPlanner PR checks with contents
> of Drools main branch. We should include Drools into OptaPlanner
> build-chain configuration, so that Drools main branch (or a matching PR
> branch in case of cross repository PR ensemble) is built locally before the
> actual OptaPlanner build (must have for FDB, and branch builds = nightly).
> 2. At the moment a PR targeted to Drools is not validated by an OptaPlanner
> build.
> This is a difference compared to how Drools -> Kogito relation is handled
> at the moment, where a Drools PR check runs also Kogito projects as
> downstream verification of the changes. We should include OptaPlanner into
> Drools build-chain configuration, so that OptaPlanner is built with
> relevant Drools changes.
> 3. Buildchain configurations for Drools and OptaPlanner need adjustment of
> mappings, thanks to unified versioning of snapshots (and eventually
> releases) we can drop any custom mapping between versions of individual
> projects.
> 4. And thanks to quarkus3 upgrade finished in OptaPlanner, we can drop
> optaplanner-quickstarts '8.x' branch from pipeline configuration and build
> 'development' instead.
> 
> While this might seem complicated, I think this is a quick win, without the
> need to "merge" all projects into one pipeline, which is IMO a bigger topic.
> 
> Regards
> Jan

+1

Thanks

Luca


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@kie.apache.org
For additional commands, e-mail: dev-help@kie.apache.org