In terms of the following PR https://github.com/jenkinsci/workflow-basic-steps-plugin/pull/100 and this issue https://issues.jenkins-ci.org/browse/JENKINS-59776 the quiet option was added to the waitUntil instruction. This really helps in case you wait for something for a long time. But this doesn't resolve the problem fully. It still spams logs with the following output

      [Pipeline] }
      [Pipeline] {
      [Pipeline] }
      [Pipeline] {
      [Pipeline] }
      [Pipeline] {
      [Pipeline] }
      [Pipeline] {
      [Pipeline] }
      [Pipeline] {
      [Pipeline] }
      [Pipeline] {
      [Pipeline] }
      

       

       

       

      And it still really spams up the flowGraphTable "Pipeline Steps" view with these blocks.

      This needs to be resolved to be silent

          [JENKINS-62531] "waitUntil" in the quiet mode still spams

          Devin Nusbaum added a comment -

          This makes sense as an improvement, but I think it would be difficult to fix on a technical level. The waitUntil step runs its body using Pipeline APIs that create a new BodyExecution for each attempt until the body evaluates to true, so the "

          {" and "}

          " messages printed in the logs and the nodes in the Pipeline Steps view for each attempt are an artifact of the current implementation.

          Devin Nusbaum added a comment - This makes sense as an improvement, but I think it would be difficult to fix on a technical level. The waitUntil step runs its body using Pipeline APIs that create a new BodyExecution for each attempt until the body evaluates to true, so the " {" and "} " messages printed in the logs and the nodes in the Pipeline Steps view for each attempt are an artifact of the current implementation.

            Unassigned Unassigned
            asavanchuk Alaiksei Savanchuk
            Votes:
            5 Vote for this issue
            Watchers:
            8 Start watching this issue

              Created:
              Updated: