Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-14137

Failed, matrix-generated Pipeline stages are not marked until build ends

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Unresolved
    • Icon: L3 - Default L3 - Default
    • None
    • None
    • CI
    • None

      In the Pipelines CI, there are matrix-generated stages. If one of these stages fails, the visualization (Pipeline graph) isn't updated until the Pipeline build is completed.

      Problem

      • The delayed update of a failed stage causes delays in development since a developer may miss a stage failure until the Pipeline build is completed (instead of canceling the build to fix the problem sooner).

      Acceptance Criteria (Required on creation):

      • A failed Pipeline stage:
        • is marked immediately after it fails.
        • before the Pipeline build is finished.

      Hints (optional):

      This problem occurs due to the use of programmatic matrix Stage generation. The Jenkins Blue Ocean UI caches the previous result of the given stage, and doesn't update the diagram until the Pipeline build is completed.

        This is the controller panel for Smart Panels app

              Unassigned Unassigned
              nikola.koevski Nikola Koevski
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: