> Surprisingly the builds in the main branch of optaplanner pipelines are all > green:
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` branch. Please someone familiar with optaplanner double-check. Thanks! Toshiya On Tue, Jul 23, 2024 at 11:56 PM Jan Šťastný <[email protected]> wrote: > Hello Paolo, > > Thanks for the reviews, this is indeed a problem. > > The optaplanner nightly build actually builds both optaplanner and > optaplanner-quickstarts repositories. The problem seems to be a mismatch > between branches used for optaplanner and optaplanner-quickstarts. > > Currently even in the main branch, optaplanner branch.yaml config maps to > optaplanner-quickstarts:8.x branch - it's on the OptaPlanner devs to answer > if this is correct (the other option is 'development'). > > https://github.com/apache/incubator-kie-optaplanner/blob/main/.ci/jenkins/config/branch.yaml#L36 > > Now, during branching, the framework took the 8.x branch of > optaplanner-quickstarts and pushed as 10.0.x. > > Surprisingly the builds in the main branch of optaplanner pipelines are all > green: > > https://ci-builds.apache.org/job/KIE/job/optaplanner/job/main/job/nightly/job/optaplanner-deploy/ > > As it turns out that optaplanner uses different Jenkinsfile for nightly and > release, so this needs some love from us to resolve the problems - since > Jenkinsfile.nightly seems to work to large extent, perhaps we should try to > adjust Jenkinsfile.release similarly: > > https://github.com/apache/incubator-kie-optaplanner/tree/main/.ci/jenkins/project > > Regards > Jan > > > > On Tue, 23 Jul 2024 at 16:11, Paolo Bizzarri <[email protected]> wrote: > > > Hello, > > > > I performed a review of the status for the optaplanner jobs in the 10.x > > folder. > > > > Here is the status. Overall the status is not ok, due to various failures > > that need to be addressed. > > > > Folders that need review > > - nightly > > The job optaplanner-deploy is failing due to a Quarkus compilation error. > > This needs to be addressed since we have not seen a nightly compilation > > yet. > > Here is the error. "Execution default of goal > > io.quarkus:quarkus-maven-plugin:2.16.10.Final:build failed: A required > > class was missing" > > > > - nightly.native > > The job optaplanner-quickstarts.build-and-test is failing due to the same > > error as above. > > > > other > > The job optaplanner.weekly-deploy is failing due to missing drools > > snapshot. > > > > - other - it is showing failures in the jobs due to deploying issues. > > Possibly it is just an environmental issue. > > > > - setup-branch > > One of the job is yellow, apparently for a failure related to > > optaplanner-quickstart. > > > > Folders that contains on demand scripts (probably no review needed?) > > - release > > - tools > > > > Regards > > > > Paolo > > >
