Uploaded image for project: 'AMQ Streams'
  1. AMQ Streams
  2. ENTMQST-5140

[QE] - Improve KafkaSTs trigger to force all jobs to run even in SUCCESS

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Undefined Undefined
    • 2.7.0.GA
    • None
    • None
    • None

      Currently, we do not have any mechanism, which will trigger all Kafka jobs when they are in SUCCESS or WAIVE state. At first glance, this seems like a proper solution but sometimes you need to run these jobs again to check if some of the changes were fixed (f.e., SUCCESS jobs also mean <= 5 failures or one wants again to execute WAIVED job).

      Thus, for that reason, we would like to have an option to forcibly run all JOBS (i.e., doesn't matter in which state they are in the gatings repo [1]).

      Proposed solution:

      We can add a boolean parameter as we have for rerun failed tests [2]. And then propagate that param in [3] method. Here we could simply add an or operator [4] and if such a boolean parameter is set to true it will also run a SUCCESS job (by default it will be false).

      [1] - https://gitlab.cee.redhat.com/strimzi/amq-streams-gating/-/blob/main/2.5.0/cr1/gating-rhel.yaml
      [2] - https://gitlab.cee.redhat.com/strimzi/strimzi-ci/-/blob/master/src/io/strimzi/ci/jobs/kafka/rhel_trigger_dsl.groovy#L30
      [3] - https://gitlab.cee.redhat.com/strimzi/strimzi-ci/-/blob/master/src/io/strimzi/ci/pipelines/kafka/rhel_trigger_pipeline.groovy#L32
      [4] - https://gitlab.cee.redhat.com/strimzi/strimzi-ci/-/blob/master/vars/gating.groovy#L188

              hzrncik_kafka_test Henrich Zrncik
              morsak Maros Orsak
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: