We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.

    • 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:

      • P2 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.

      P2 jobs:

      • .ci/jobs/query_performance.dsl
      • .ci/jobs/event_import_performance.dsl
      • .ci/jobs/cleanup_data_performance_large.dsl
      • .ci/jobs/event_import_performance.dsl
      • .ci/jobs/import_large_static_data_performance.dsl
      • .ci/jobs/upgrade_data_performance_large.dsl
      • .ci/jobs/event_cleanup_performance.dsl

        This is the controller panel for Smart Panels app

            Loading...

              • 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:

                • P2 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.

                P2 jobs:

                • .ci/jobs/query_performance.dsl
                • .ci/jobs/event_import_performance.dsl
                • .ci/jobs/cleanup_data_performance_large.dsl
                • .ci/jobs/event_import_performance.dsl
                • .ci/jobs/import_large_static_data_performance.dsl
                • .ci/jobs/upgrade_data_performance_large.dsl
                • .ci/jobs/event_cleanup_performance.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:

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

                                Created:
                                Updated: