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

OptaPlanner 7.x branch: adapt cross-repos PR's jobs

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Major Major
    • None
    • None
    • None
    • None

      Normal main requirements:
      2 PR's to kiegroup repo's (from the repository-list.txt basically) must use be combined if the they have the same sourceBranch name (for example "ge0ffrey:myFeature") and if they have the same targetBranch name.

      Adjusted main requirements proposal A):
      The targetBranch "master" and "7.x" are considered the same.
      This isn't perfect, but it will work.

      Adjusted main requirements proposal B):
      If one targetBranches is "master" and in "repository-list.txt" but not in "branched-7-repository-list.txt"
      and the other targetBranch is "7.x" and in "branched-7-repository-list.txt",
      then they are considered the same.
      This is perfect.

      See https://docs.google.com/document/d/1o_A3YdfWz9ghIp1ooE_0XI3ZbLWgFzLezRm7xP0j-uE/edit#

      Will affect:
      https://github.com/kiegroup/jenkins-pipeline-shared-libraries/blob/7e9cef7826c62db210aadb165968b4bb27057236/vars/util.groovy#L33

      These are the new cases that should work now

      CASE source branch community target branch optaplanner target branch Goal
      A same master master SEPARATE
      B same master 7.x COMBINE
      C different master master SEPARATE
      D different master 7.x SEPARATE

       

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

                Created:
                Updated:
                Resolved: