Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-4200

Include the OptaPlanner version number calculation and version bump in the Jenkinsfile.deploy and Jenkinsfile.promote

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • 1.2.0.Final
    • None
    • Core Engine
    • None
    • False
    • False
    • Undefined
    • ---
    • ---

      As part of the changes realized in:
      https://issues.redhat.com/browse/KOGITO-4167

      we can now add the proper dependency to OptaPlanner in kogito-apps.

      The dependency will added like this, in the kogito-apps/pom.xml

      <properties>
           <version.org.optaplanner>8.2.0-SNAPSHOT</version.org.optaplanner>
      </properties>
      

      and in the

        <dependencyManagement>
            <dependency>
              <groupId>org.optaplanner</groupId>
              <artifactId>optaplanner-bom</artifactId>
              <version>${version.org.optaplanner}</version>
              <type>pom</type>
              <scope>import</scope>
            </dependency>
      </dependencyManagement>
      

      By doing this the proper version passed by the Jenkinsfile.deploy/Jenkinsfile.promote will be taken.

      However it was stated https://github.com/kiegroup/kogito-apps/pull/591#pullrequestreview-570250826 it looks that these scripts might require some tuning for doing the calculation of the value of the OPTAPLANNER_VERSION variable to be passed to the maven script.

              tradisso@redhat.com Tristan Radisson
              wmedvede@redhat.com Walter Medvedeo
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: