Remove the experimental optaplanner-operator

[Rikkola]

JIRA

Referenced pull requests

Checklist

• Documentation updated if applicable.
• Release notes 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] 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] 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] quarkus-branch

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

• for a specific quarkus lts check
  Run checks against Quarkus lts branch
  Please add comment: Jenkins (re)run [optaplanner|optaplanner-quickstarts] quarkus-lts

• 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] native

• for native lts checks
  Run native checks against quarkus lts branch
  Please add comment: Jenkins run native-lts

• for a specific native lts check
  Run native checks against quarkus lts branch
  Please add comment: Jenkins (re)run [optaplanner|optaplanner-quickstarts] native-lts

CI Status

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

How to backport a pull request to a different branch?

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.

[Copilot]

Pull Request Overview

This PR removes the experimental optaplanner-operator module entirely from the codebase and distribution, including its tests, k8s manifests, CI settings, and parent BOM/dependencies.

• Deleted the optaplanner-operator directory (code, tests, k8s, README, .gitignore)
• Dropped the operator module from the root pom.xml and all distribution assemblies/profiles
• Cleaned up CI job DSL to remove operator‐specific environment variables

Reviewed Changes

Copilot reviewed 42 out of 43 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
pom.xml	Removed the optaplanner-operator profile module
build/optaplanner-distribution-internal/.../assembly-optaplanner.xml	Removed operator distribution fileSet
build/optaplanner-distribution-internal/pom.xml	Dropped operator dependency from distribution
build/optaplanner-build-parent/pom.xml	Removed operator dependencies in parent POM
build/optaplanner-bom/pom.xml	Removed operator from BOM dependency management
.ci/jenkins/dsl/jobs.groovy	Removed OPERATOR_IMAGE_NAME and related vars
optaplanner-operator/**	Entire module and tests deleted

Comments suppressed due to low confidence (2)

build/optaplanner-distribution-internal/src/main/assembly/assembly-optaplanner.xml:74

• [nitpick] Consider updating the top‐level project documentation (README, website docs) to remove references to the experimental Operator, so users aren’t misled by stale instructions.

    </fileSet>

.ci/jenkins/dsl/jobs.groovy:315

• After removing the OPERATOR_IMAGE_NAME environment variable, ensure that downstream pipeline scripts or templates no longer reference it. Update any job templates that expect OPERATOR_IMAGE_NAME to prevent undefined variable errors.

        jobParams.env.putAll([