Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.12
    • Component/s: Pipeline
    • Labels:

      Description

      Current algorithm:

      1. start listening for webhook for the task
      2. query api/ce/task
        1. if task status = SUCCESS, query the quality gate status, and stop listening for webhook
        2. if task status = IN_PROGRESS, assume webhook has not been sent, and wait for it

      The problem is that even if api/ce/task says that task is IN_PROGRESS, the webhook may have already been sent, and received before we started to listen for it.

      Proposed workaround is to change the algorithm:

      1. start listening for webhook for the task
      2. query api/ce/task
        1. if task status = SUCCESS, query the quality gate status, and stop listening webhook
        2. if task status = IN_PROGRESS, still query the quality gate status
          1. if WS response is 404, assume webhook has not been sent, and wait for it
          2. is response is 200, get the quality gate status, and stop listening for webhook

      Update: the proposed workaround is not possible, since api/ce/task doesn't provide the analysisId when task is "IN_PROGRESS".

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                mark.rekveld Mark Rekveld (Inactive)
                Reporter:
                julien.henry Julien Henry
              • Votes:
                17 Vote for this issue
                Watchers:
                16 Start watching this issue

                Dates

                • Due:
                  Created:
                  Updated:
                  Resolved: