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

Error Signal Description not displayed in Blue Ocean

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Major Major
    • blueocean-plugin
    • None

      When running Declarative Pipeline in below particular case error signal does not display any descriptions. The only place to find it (and its there properly expanded) is the end of console output.

      stage ('Pipeline-PR') {
          when {
              changeRequest()
              expression { env.CHANGE_TARGET == 'master' || env.CHANGE_TARGET == 'develop' }
          }
          steps {
              script {
                  def version = bat(script: "@set library.componentPipeline.version", returnStdout: true).split("=",2).last().trim()
                  if (version != 'master') {
                      error "Pull request targeting ${env.CHANGE_TARGET} cannot be based on ${version} branch of component pipeline, should be based on master!"
                  }
              }
          }
      }

      shows only as:

          [JENKINS-52923] Error Signal Description not displayed in Blue Ocean

          Saad Azam added a comment -

          I am facing a similar issue

          Saad Azam added a comment - I am facing a similar issue

          Igor Solovko added a comment -

          similar issue

          Igor Solovko added a comment - similar issue

          feels like something is interfering with propagating the signal message to UI, could not replicate it in simpler cases yet

          Jakub Pawlinski added a comment - feels like something is interfering with propagating the signal message to UI, could not replicate it in simpler cases yet

          Saad Azam added a comment - - edited

          comment-348310 (above) holds true for me as well.

          Saad Azam added a comment - - edited comment-348310  (above) holds true for me as well.

          Melvin Won added a comment -

          It happens to me when the variable to be interpolated is larger than 104 characters.

          Example, when metaDataFilePath is larger than 104 characters, the entire error description is not displayed on blue ocean. error signal is still displayed.

          error ("[ERROR] Metadata missing for ${bundleName} : Unable to find ${metaDataFilePath}. Please make sure the file exists.")
          

           

          Melvin Won added a comment - It happens to me when the variable to be interpolated is larger than 104 characters. Example, when  metaDataFilePath is larger than 104 characters, the entire error description is not displayed on blue ocean. error signal is still displayed. error ( "[ERROR] Metadata missing for ${bundleName} : Unable to find ${metaDataFilePath}. Please make sure the file exists." )  

          I did some more tests with this

           

          stage ('Throw Error') {
            steps {
              script {
                println "Testing ${params.length} bytes"
                def lipsum = new XmlSlurper().parseText("https://www.lipsum.com/feed/xml?what=bytes&amount=${params.length}&start=no".toURL().text).lipsum.toString()
                error lipsum
              }
            }
          }
          

          and it works fine up to 1023 bytes:

           

          Jakub Pawlinski added a comment - I did some more tests with this   stage ( 'Throw Error' ) { steps { script { println "Testing ${params.length} bytes" def lipsum = new XmlSlurper().parseText( "https: //www.lipsum.com/feed/xml?what=bytes&amount=${params.length}&start=no" .toURL().text).lipsum.toString() error lipsum } } } and it works fine up to 1023 bytes:  

            Unassigned Unassigned
            quas Jakub Pawlinski
            Votes:
            6 Vote for this issue
            Watchers:
            7 Start watching this issue

              Created:
              Updated: