[RHPAM-4449] spring-boot downgraded to 2.5.12

[Ginxo]

JIRA:
https://issues.redhat.com/browse/RHPAM-4449

referenced Pull Requests:

• [RHPAM-4449] spring-boot downgraded to 2.5.12 kiegroup/droolsjbpm-build-bootstrap#2008
• [7.67.x][RHPAM-4449] spring-boot downgraded to 2.5.12 kiegroup/droolsjbpm-build-bootstrap#2010
• [7.67.x-blue][RHPAM-4449] spring-boot downgraded to 2.5.12 kiegroup/droolsjbpm-build-bootstrap#2009
• https://github.com/kiegroup/optaplanner/pull/2089
• https://github.com/kiegroup/optaplanner/pull/2090
• https://github.com/kiegroup/optaplanner/pull/2091

Checklist

• Documentation updated if applicable.
• Upgrade recipe provided if applicable.

How to replicate CI configuration locally?

Build Chain tool does "simple" maven build(s), the builds are just Maven commands, but because the repositories relates and depends on each other and any change in API or class method could affect several of those repositories there is a need to use build-chain tool to handle cross repository builds and be sure that we always use latest version of the code for each repository.

build-chain tool is a build tool which can be used on command line locally or in Github Actions workflow(s), in case you need to change multiple repositories and send multiple dependent pull requests related with a change you can easily reproduce the same build by executing it on Github hosted environment or locally in your development environment. See local execution details to get more information about it.

How to retest this PR or trigger a specific build:

• for pull request checks
  Please add comment: Jenkins retest this

• for a specific pull request check
  please add comment: Jenkins (re)run [optaplanner|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] tests

• for a full downstream build

  • for jenkins job:
    please add comment: Jenkins run fdb
  • for github actions job:
    add the label run_fdb

• for a compile downstream build
  please add comment: Jenkins run cdb

• for a full production downstream build
  please add comment: Jenkins execute product fdb

• for an upstream build
  please add comment: Jenkins run upstream

• for quarkus branch checks
  Run checks against Quarkus current used branch
  Please add comment: Jenkins run quarkus-branch

• for a quarkus branch specific check
  Run checks against Quarkus current used branch
  Please add comment: Jenkins (re)run [optaplanner|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] quarkus-branch

• for quarkus main checks
  Run checks against Quarkus main branch
  Please add comment: Jenkins run quarkus-main

• for a specific quarkus main check
  Run checks against Quarkus main branch
  Please add comment: Jenkins (re)run [optaplanner|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] quarkus-branch

• for native checks
  Run native checks
  Please add comment: Jenkins run native

• for a specific native check
  Run native checks
  Please add comment: Jenkins (re)run [optaplanner|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] native

• for mandrel checks
  Run native checks against Mandrel image
  Please add comment: Jenkins run mandrel

• for a specific mandrel check
  Run native checks against Mandrel image
  Please add comment: Jenkins (re)run [optaplanner|optaplanner-quickstarts|optaweb-employee-rostering|optaweb-vehicle-routing] mandrel

CI Status

You can check OptaPlanner repositories CI status from Chain Status webpage.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[rsynek]

Jenkins run optaweb-vehicle-routing tests

[rsynek]

@Ginxo It looks like there is no downstream build to optawebs that are based on Spring Boot on the 7.x branch.

[Ginxo]

@rsynek FDB from kiegroup/droolsjbpm-build-bootstrap#1987 is covering the PR set change

[rsynek]

Good to merge provided the FDB succeeded for both optawebs.