You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@kie.apache.org by "gitgabrio (via GitHub)" <gi...@apache.org> on 2026/04/08 08:47:58 UTC
[PR] [incubator-kie-issues#2029] Enforce framework-specific BOM separation [incubator-kie-optaplanner]
gitgabrio opened a new pull request, #3216:
URL: https://github.com/apache/incubator-kie-optaplanner/pull/3216
Fixes: https://github.com/apache/incubator-kie-issues/issues/2029
Depends on:
https://github.com/apache/incubator-kie-drools/pull/6633
https://github.com/apache/incubator-kie-kogito-runtimes/pull/4241
Needed by:
https://github.com/apache/incubator-kie-kogito-apps/pull/2317
https://github.com/apache/incubator-kie-kogito-examples/pull/2197
<details>
<summary>
How to retest this PR or trigger a specific build:
</summary>
- for <b>pull request checks</b>
Please add comment: <b>Jenkins retest this</b>
- for a <b>specific pull request check</b>
please add comment: <b>Jenkins (re)run [optaplanner|optaplanner-quickstarts] tests</b>
- for a <b>full downstream build</b>
- for <b>jenkins</b> job:
please add comment: <b>Jenkins run fdb</b>
- for <b>github actions</b> job:
add the label `run_fdb`
- for a <b>compile downstream build</b>
please add comment: <b>Jenkins run cdb</b>
- for a <b>full production downstream build</b>
please add comment: <b>Jenkins execute product fdb</b>
- for an <b>upstream build</b>
please add comment: <b>Jenkins run upstream</b>
- for <b>quarkus branch checks</b>
Run checks against Quarkus current used branch
Please add comment: <b>Jenkins run quarkus-branch</b>
- for a <b>quarkus branch specific check</b>
Run checks against Quarkus current used branch
Please add comment: <b>Jenkins (re)run [optaplanner|optaplanner-quickstarts] quarkus-branch</b>
- for <b>quarkus main checks</b>
Run checks against Quarkus main branch
Please add comment: <b>Jenkins run quarkus-main</b>
- for a <b>specific quarkus main check</b>
Run checks against Quarkus main branch
Please add comment: <b>Jenkins (re)run [optaplanner|optaplanner-quickstarts] quarkus-branch</b>
- for <b>quarkus lts checks</b>
Run checks against Quarkus lts branch
Please add comment: <b>Jenkins run quarkus-lts</b>
- for a <b>specific quarkus lts check</b>
Run checks against Quarkus lts branch
Please add comment: <b>Jenkins (re)run [optaplanner|optaplanner-quickstarts] quarkus-lts</b>
- for <b>native checks</b>
Run native checks
Please add comment: <b>Jenkins run native</b>
- for a <b>specific native check</b>
Run native checks
Please add comment: <b>Jenkins (re)run [optaplanner|optaplanner-quickstarts] native</b>
- for <b>native lts checks</b>
Run native checks against quarkus lts branch
Please add comment: <b>Jenkins run native-lts</b>
- for a <b>specific native lts check</b>
Run native checks against quarkus lts branch
Please add comment: <b>Jenkins (re)run [optaplanner|optaplanner-quickstarts] native-lts</b>
</details>
### CI Status
You can check OptaPlanner repositories CI status from [Chain Status webpage](https://apache.github.io/incubator-kie-optaplanner/).
<details>
<summary>
How to backport a pull request to a different branch?
</summary>
In order to automatically create a **backporting pull request** please add one or more labels having the following format `backport-<branch-name>`, where `<branch-name>` is the name of the branch where the pull request must be backported to (e.g., `backport-7.67.x` to backport the original PR to the `7.67.x` branch).
> **NOTE**: **backporting** is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.
Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.
> **NOTE**: this automated backporting is triggered whenever a pull request on `main` branch is labeled or closed, but both conditions must be satisfied to get the new PR created.
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org
Re: [PR] [incubator-kie-issues#2029] Enforce framework-specific BOM separation [incubator-kie-optaplanner]
Posted by "gitgabrio (via GitHub)" <gi...@apache.org>.
gitgabrio closed pull request #3216: [incubator-kie-issues#2029] Enforce framework-specific BOM separation
URL: https://github.com/apache/incubator-kie-optaplanner/pull/3216
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@kie.apache.org
For additional commands, e-mail: commits-help@kie.apache.org