> On 24 Jul 2024, at 11:43, Luca Molteni <[email protected]> wrote:
>
>
>
>> On 24 Jul 2024, at 09:25, Toshiya Kobayashi <[email protected]>
>> wrote:
>>
>> optaplanner-quickstarts 8.x runs with 8.45.0-SNAPSHOT, so it results in
>> green regardless of the optaplanner main (999-SNAPSHOT).
>>
>> https://github.com/apache/incubator-kie-optaplanner-quickstarts/blob/8.x/pom.xml#L9
>>
>> Hence, for optaplanner main, I guess the expected optaplanner-quickstarts
>> branch would be `development`.
>>
>> In the optaplanner 10.0.x nightly job, the optaplanner-quickstarts 10.0.x
>> branch was taken from 8.x, but it updates the version to 10.0.999-SNAPSHOT,
>> so hit the error (quarkus version conflict).
>>
>> https://github.com/apache/incubator-kie-optaplanner-quickstarts/blob/10.0.x/pom.xml#L9
>>
>> I think the optaplanner-quickstarts 10.0.x branch should also be taken from
>> the `development`
Was the 10.0.x branch taken from 8 because of this mapping that wasn’t never
updated? (I’ve created a PR for it)
https://github.com/apache/incubator-kie-optaplanner/pull/3112/files
Reading the log from this failing PR
(https://github.com/apache/incubator-kie-optaplanner/pull/3111)
[2024-07-23T19:21:26.364Z] # Checkout summary
[2024-07-23T19:21:26.364Z] [INFO] [apache/incubator-kie-optaplanner]
[2024-07-23T19:21:26.364Z] [INFO] Project taken from
apache/incubator-kie-optaplanner:10.0.x (Branch HEAD
26504a8aa1a1201a4f334687278bc6f5b6d01fc4)
[2024-07-23T19:21:26.364Z] [INFO] Merged
rodrigonull/incubator-kie-optaplanner:adjust-release-jobs into branch 10.0.x
[2024-07-23T19:21:26.364Z] [INFO] [apache/incubator-kie-optaplanner-quickstarts]
[2024-07-23T19:21:26.365Z] [INFO] Project taken from
apache/incubator-kie-optaplanner-quickstarts:10.0.x (Branch HEAD
b690beadc53493fb132e8a93d0b9d269f5452fed)
I see that build-chain is taking the 10.0.x branch from optaplanner-quickstart,
but as Toshiya already noticed, the 10.0.x branch was wrongly created (see
https://github.com/apache/incubator-kie-optaplanner-quickstarts/commits/10.0.x
the last commit before the bump is 0085584a74976b66d8f43c1155012773c52e3fe1
instead of 752f8be515cbd02d1fc130dda75adb6e99b0dca7
I’m not sure if this email alone can help, feel free to ping me on Zulip so
that we can fix this
Luca
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
