Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-5987 Optimize CI extended to support maintenance branches
  3. OPT-5990

Optimize JobDSL is adjusted for maintenance branch support: P1

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Unresolved
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • None

      Description of the problem:
      Tests must be executed as well for maintenance branches.
      If we keep using the same jobs for maintenance, the folder prefix needs to be adjusted.

      Desired outcome and acceptance tests:

      • P1 jobs are adjusted for maintenance branches (list below) and symlinked
      • If applicable, job names are generated with a maintenance/<version>/ prefix.
      • There are no collisions with non-maintenance jobs, e.g. data-generating or consuming jobs for master.

      Hints (optional):

      • Ideally, a shared-library function is used for prefixing the job name.
      • Pay attention to references to master
      • Jobs which generate or consume data using Google Buckets need to use a path prefix as well.

      P1 jobs:

      • .ci/jobs/elasticsearch_combatibility.dsl
      • .ci/jobs/engine_compatibility.dsl
      • .ci/jobs/java_combatibility.dsl
      • .ci/jobs/e2e_tests.dsl
      • .ci/jobs/import_dynamic_data_performance.dsl
      • .ci/jobs/import_mediator_permutation_test.dsl
      • .ci/jobs/secured_es.dsl
      • .ci/jobs/cluster_test.dsl
      • .ci/jobs/dependency_check.dsl
      • .ci/jobs/release_optimize.dsl

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              leonhardt.wille Leonhardt Wille
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: