Uploaded image for project: 'OptaPlanner'
  1. OptaPlanner
  2. PLANNER-2603

Do not merge a release to optaplanner-quickstarts stable if the artifacts are not yet on Maven Central

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Blocker Blocker
    • None
    • None
    • optaplanner-quickstarts
    • None
    • NEW
    • NEW 

      $ mvn clean install -U
[INFO] Scanning for projects...
Downloading from central: https://repo.maven.apache.org/maven2/org/optaplanner/optaplanner-bom/8.14.1.Final/optaplanner-bom-8.14.1.Final.pom
[ERROR] [ERROR] Some problems were encountered while processing the POMs:
[ERROR] Non-resolvable import POM: Could not find artifact org.optaplanner:optaplanner-bom:pom:8.14.1.Final in central (https://repo.maven.apache.org/maven2) @ line 30, column 19

      Discussion: https://kie.zulipchat.com/#narrow/stream/235756-optaplanner-dev/topic/quickstarts.20broken.3A.208.2E14.2E1.20does.20not.20exist.20in.20maven.20central

      Proposal A) Do not merge the optaplanner-quickstart PR's automatically.

      "Tristan Radisson: and removing the automatic is feasible and can be done directly on the optaplanner repo
      Tristan Radisson: see https://github.com/kiegroup/optaplanner/blob/main/.ci/jenkins/Jenkinsfile.promote#L112
      Tristan Radisson: and then you should bypass also https://github.com/kiegroup/optaplanner/blob/main/.ci/jenkins/Jenkinsfile.promote#L127
      Tristan Radisson: and most probably https://github.com/kiegroup/optaplanner/blob/main/.ci/jenkins/Jenkinsfile.promote#L190
      Tristan Radisson: this could be added to another job to be executed once artifacts are available on Maven central"

              tradisso@redhat.com Tristan Radisson
              gdesmet@redhat.com Geoffrey De Smet (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: