[TopicAssociation] Provide options to prevent triggering jobs when Change status != NEW

This issue is archived. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Feature released in Gerrit Trigger Plugin vers. 2.38.0

      When enabling the option "Enable Topic Association"  within the job configurations every job will be triggered as soon as the topic is of interest.

      This can lead to jobs triggered even if the Change matching the topic has the status MERGED or ABANDONED.

      In general you can't submit a whole topic in Gerrit if there is one change which has been abandoned. Since topics are not unique in Gerrit and it always can happen that some developers assign a change to another topic as reference there should be an option to prevent triggering builds if the change of interest assigned to the topic is already in a specific state.

            Assignee:
            rsandell
            Reporter:
            ckreisl
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: