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

Make master 8.0.0-SNAPSHOT, branch 7.x and adjust build scripts and CI

    XMLWordPrintable

Details

    • Task
    • Resolution: Done
    • Major
    • None
    • None
    • None
    • None
    • 2020 Week 25-27 (from Jun 15)
    • 5
    • NEW
    • NEW

    Description

      Inventory of things that must be tested to still work, so requirements:

      • * community release (dry run?)
        • git clone all script
        • update versions script
        • ...
      • product release (dry run?)
      • Jenkins Pr builds
      • Jenkins daily builds
      • ...

      Proposal A battleplan:

      BEFORE
    Master pom.xml:
          <parent>
            <groupId>org.kie</groupId>
            <artifactId>kie-parent</artifactId>
            <version>7.40.0-SNAPSHOT</version>
          </parent>
          (<version>7.40.0-SNAPSHOT</version>)

Proposal A)
    Step A.1
        Branch 7.x:
              <parent>
                <groupId>org.kie</groupId>
                <artifactId>kie-parent</artifactId>
                <version>7.40.0-SNAPSHOT</version>
              </parent>
              (<version>7.40.0-SNAPSHOT</version>)
        Master pom.xml:
              <parent>
                <groupId>org.kie</groupId>
                <artifactId>kie-parent</artifactId>
                <version>7.40.0-SNAPSHOT</version>
              </parent>
              <version>8.0.0-SNAPSHOT</version>
    Step A.2
        Fix all scripts, Jenkins, etc
    Step A.3
        Master pom.xml:
                <<< BREAK THE XML >>>
    Step A.4
        Master pom.xml:
              <parent>...</parent> // no more kie-parent
              <version>8.0.0-SNAPSHOT</version>

      Attachments

        Issue Links

          incorporates

          Task - Represents a small unit of work that is not end-user facing. PLANNER-2043 OptaPlanner 7.x branch: adapt cross-repos PR's jobs

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. PLANNER-2044 OptaPlanner 7.x branch: adapt nightly

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Task - Represents a small unit of work that is not end-user facing. PLANNER-2045 OptaPlanner 7.x branch: Adjust git-clone-others.sh

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is incorporated by

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. PLANNER-1964 Branching towards 8.0

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved

          Activity

            People

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

              Dates

                Created:
                Updated:
                Resolved: