Gitea check context not unique for multi-target builds

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Major
    • Component/s: gitea-plugin
    • None
    • Environment:
      Jenkins → 2.516.1
      Gitea Checks plugin → 551.vd306d7ca_b_18f
      Gitea Plugin → 250.v76a_0b_d4fef5b_

      When running with a non-trivial BranchBuildStrategy,
      e.g. when using Basic Branch Build Strategies,
      a singular check context for a pull request is ambiguous.

      The plugin can build multiple variants (head, merged) based on the settings.

      A respecive extraction (similar to job name) is required to distinguish states for multiple builds:
      The statuses for e.g: PR-12-head, PR-12-merge
      MUST NOT share the same context string, generated from …/pipeline/pr-<target-branch-name>.

            Assignee:
            Unassigned
            Reporter:
            Marc Becker
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: