Optimize shared library logging in CI pipelines

XMLWordPrintable

    • Type: Task
    • Resolution: Unresolved
    • Priority: L3 - Default
    • None
    • Affects Version/s: None
    • Component/s: None

      Description

      The current logger level for the Pipelines is set to DEBUGhttps://github.com/camunda/camunda-bpm-platform/blob/master/Jenkinsfile#L14

      Problem

      The DEBUG logger provides a lot of additional output in the Jenkins Pipelines UI, which causes a lot of noise and makes extracting useful information more difficult.

      Proposal

      • Change the logger level to INFO to reduce the number of messages.
      • Consider if some DEBUG logs should be set to the INFO level.
      • Add additional INFO and DEBUG logging to:
        • PR label evaluation.
        • Matrix stage generation.
        • Not triggering a stage due to a previous failed stage of the same type.
        • ... and other cusom steps (TBD).
           

            Assignee:
            Unassigned
            Reporter:
            Yana Vasileva
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: