Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-41769

Developer can see a description for a pipeline run

    • Blue Ocean 1.1-beta4

      Example 1

      node {
         sh 'ping -c 5 localhost'
         currentBuild.description = "go to http://www.apple.com/";
      }
      

          [JENKINS-41769] Developer can see a description for a pipeline run

          James Dumay added a comment -

          jakauppila Blue Ocean 1.1-beta4 has been released to the experimental update center and contains this change if you want to try it out.

          James Dumay added a comment - jakauppila Blue Ocean 1.1-beta4 has been released to the experimental update center and contains this change if you want to try it out.

          jamesdumay Looks good! The only thing I would say is that now that the "Run" content updates from currentBuild.displayName, it's a bit limited as it only displays ~7 characters.

          Jared Kauppila added a comment - jamesdumay Looks good! The only thing I would say is that now that the "Run" content updates from currentBuild.displayName, it's a bit limited as it only displays ~7 characters.

          How do I use a Linebreak in the description? I have the Safe HTML Formatter, but neither "\n" not "<br>" trigger a line break.

          Kevin Grüneberg added a comment - How do I use a Linebreak in the description? I have the Safe HTML Formatter, but neither "\n" not "<br>" trigger a line break.

          With Safe HTML Formatter I can add links to currentBuild.description and links will be rendered correctly everywhere except Blue Ocean plugin:

          vs

          Are there any plans to support HTML tags in Blue Ocean build description?

          Veaceslav Gaidarji added a comment - With Safe HTML Formatter I can add links to currentBuild.description and links will be rendered correctly everywhere except Blue Ocean plugin: vs Are there any plans to support HTML tags in Blue Ocean build description?

          vgaidarji I opened JENKINS-45181 because I expected the description to support <br> (Safe HTML).

          Quoting jamesdumay 

           

           the design we have only caters for a single line on both the messages column and the pipeline result details header. Allowing arbitrary amounts of formatting and information there would significantly impact the design. Ill be honest, we are unlikely to change that in the next year. However sometime next year we are planning a redesign of those screens so we could consider it then.

           

          I would like to see HTML being supported in the description aswell.

          Kevin Grüneberg added a comment - vgaidarji I opened JENKINS-45181 because I expected the description to support <br> (Safe HTML). Quoting jamesdumay      the design we have only caters for a single line on both the messages column and the pipeline result details header. Allowing arbitrary amounts of formatting and information there would significantly impact the design. Ill be honest, we are unlikely to change that in the next year. However sometime next year we are planning a redesign of those screens so we could consider it then.   I would like to see HTML being supported in the description aswell.

          Is there a way to turn this feature off?

           

          Jakub Pawlinski added a comment - Is there a way to turn this feature off?  

          James Dumay added a comment -

          Yes by not setting the description for your pipeline

          James Dumay added a comment - Yes by not setting the description for your pipeline

          My pipelines were already using description property before this fix, generating a fancy html table with loads of useful links and such. It works well outside of blue ocean where now I'm getting half of page of html gibberish. 

          Jakub Pawlinski added a comment - My pipelines were already using description property before this fix, generating a fancy html table with loads of useful links and such. It works well outside of blue ocean where now I'm getting half of page of html gibberish. 

          James Dumay added a comment -

          quas I understand. Could you open a new ticket with your use case and we can evaluate it from there?

          James Dumay added a comment - quas I understand. Could you open a new ticket with your use case and we can evaluate it from there?

          Jakub Pawlinski added a comment - Created  https://issues.jenkins-ci.org/browse/JENKINS-45719

            jamesdumay James Dumay
            nok Martin Noack
            Votes:
            3 Vote for this issue
            Watchers:
            11 Start watching this issue

              Created:
              Updated:
              Resolved: