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

9 views
Skip to first unread message

jakub@pawlinski.pl (JIRA)

unread,
Aug 7, 2018, 1:12:01 PM8/7/18
to jenkinsc...@googlegroups.com
Jakub Pawlinski updated an issue
 
Jenkins / Bug JENKINS-52923
Error Signal Description not displayed in Blue Ocean
Change By: Jakub Pawlinski
Summary: CLONE - Error Signal Description not expandible displayed in Blue Ocean when using Declarative Pipeline and Environment Variables
Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.10.1#710002-sha1:6efc396)

jakub@pawlinski.pl (JIRA)

unread,
Aug 7, 2018, 1:12:02 PM8/7/18
to jenkinsc...@googlegroups.com
Jakub Pawlinski updated an issue
Change By: Jakub Pawlinski
Environment: Jenkins
=======

Version details
---------------

  * Version: `2.60.1`
  * Mode:    WAR
  * Url:     http://127.0.0.1:8080
  * Servlet container
      - Specification: 3.1
      - Name:          `jetty/9.2.z-SNAPSHOT`
  * Java
      - Home:           `/usr/lib/jvm/java-8-oracle/jre`
      - Vendor:           Oracle Corporation
      - Version:          1.8.0_131
      - Maximum memory:   1.52 GB (1629487104)
      - Allocated memory: 797.50 MB (836239360)
      - Free memory:      269.19 MB (282262896)
      - In-use memory:    528.31 MB (553976464)
      - GC strategy:      ParallelGC

Relevant plugins:

blueocean:1.1.6:not-pinned
blueocean-autofavorite:1.0.0:not-pinned
blueocean-commons:1.1.6:not-pinned
blueocean-config:1.1.6:not-pinned
blueocean-dashboard:1.1.6:not-pinned
blueocean-display-url:2.0:not-pinned
blueocean-events:1.1.6:not-pinned
blueocean-git-pipeline:1.1.6:not-pinned
blueocean-github-pipeline:1.1.6:not-pinned
blueocean-i18n:1.1.6:not-pinned
blueocean-jwt:1.1.6:not-pinned
blueocean-personalization:1.1.6:not-pinned
blueocean-pipeline-api-impl:1.1.6:not-pinned
blueocean-pipeline-editor:0.2.0:not-pinned
blueocean-pipeline-scm-api:1.1.6:not-pinned
blueocean-rest:1.1.6:not-pinned
blueocean-rest-impl:1.1.6:not-pinned
blueocean-web:1.1.6:not-pinned

pipeline-build-step:2.5:not-pinned
pipeline-classpath:0.1.0:not-pinned
pipeline-github-lib:1.0:not-pinned
pipeline-graph-analysis:1.4:not-pinned
pipeline-input-step:2.8:not-pinned
pipeline-maven:2.5.0:not-pinned
pipeline-milestone-step:1.3.1:not-pinned
pipeline-model-api:1.1.6:not-pinned
pipeline-model-declarative-agent:1.1.1:not-pinned
pipeline-model-definition:1.1.6:not-pinned
pipeline-model-extensions:1.1.6:not-pinned
pipeline-rest-api:2.8:not-pinned
pipeline-stage-step:2.2:not-pinned
pipeline-stage-tags-metadata:1.1.6:not-pinned
pipeline-stage-view:2.8:not-pinned
pipeline-utility-steps:1.3.0:not-pinned

workflow-aggregator:2.5:not-pinned
workflow-api:2.17:not-pinned
workflow-basic-steps:2.5:not-pinned
workflow-cps:2.36:not-pinned
workflow-cps-checkpoint:2.4:not-pinned
workflow-cps-global-lib:2.8:not-pinned
workflow-durable-task-step:2.12:not-pinned
workflow-job:2.12.1:not-pinned
workflow-multibranch:2.16:not-pinned
workflow-scm-step:2.6:not-pinned
workflow-step-api:2.11:not-pinned
workflow-support:2.14:not-pinned

jakub@pawlinski.pl (JIRA)

unread,
Aug 7, 2018, 1:12:02 PM8/7/18
to jenkinsc...@googlegroups.com
Jakub Pawlinski updated an issue
Change By: Jakub Pawlinski
Priority: Critical Major

jakub@pawlinski.pl (JIRA)

unread,
Aug 7, 2018, 1:18:02 PM8/7/18
to jenkinsc...@googlegroups.com
Jakub Pawlinski updated an issue
Change By: Jakub Pawlinski
Attachment: image-2018-08-07-18-17-35-341.png

jakub@pawlinski.pl (JIRA)

unread,
Aug 7, 2018, 1:18:02 PM8/7/18
to jenkinsc...@googlegroups.com
Jakub Pawlinski updated an issue
Change By: Jakub Pawlinski
Attachment: image-2018-08-07-18-17-28-500.png

jakub@pawlinski.pl (JIRA)

unread,
Aug 7, 2018, 1:18:03 PM8/7/18
to jenkinsc...@googlegroups.com
Jakub Pawlinski updated an issue
When defining a running Declarative Pipeline which declares an {{environment}} directive in below particular case error signal descriptions are does not expandible in Blue Ocean view display any descriptions .

declarative-pipeline-error-signal-example-with-env-var:
{code:java}
pipeline {
agent none
environment {
EXAMPLE_VARIABLE = 'This is an example variable'
}
stages {
stage The only place to find it ( 'Error Example' and its there properly expanded ) {
steps {
error "This is an error example using declarative pipeline"
}
}
}
}
{code}
Note that when looking at Blue Ocean output that the error description is not expandible:

!declarative-pipeline-error-signal-example-with-env-var end of console output . png!

The issue is not reproduced when using Scripted Pipeline.

scripted-pipeline-with-env-var:
 {code:java}
 node {
    withEnv(['EXAMPLE_VARIABLE="this is an example variable"']) {
         stage(' Error Example Pipeline-PR ') {
             error "This is an example error message using scripted pipeline"
        }
    }
}
     when { code}
Error is expandible in Blue Ocean:         changeRequest()

!scripted-pipeline-with-         expression { env -var . png!

 

Looking at the console logs in the Declarative Pipeline example.

declarative-pipeline-error-signal-example-with-env-var.log:

{quote}
blueocean.js:18586 Browser configuration of @jenkins-cd/logging is explained at https://tfennelly.github.io/jenkins-js-logging/index.html#browser-config
jenkins-js-extension.js:47602 [Violation] Added non-passive event listener to a scroll-blocking CHANGE_TARGET == ' wheel master ' event || env . Consider marking event handler as CHANGE_TARGET == ' passive develop ' to make the page more responsive. }
blueocean.js:2752 Uncaught TypeError: Cannot read property 'indexOf' of undefined     }
at trimRestUrl (blueocean.js:2752)     steps {
at getPrefetchedDataFuture (blueocean.js:2762)         script {
at request             def version = bat ( blueocean.js script : 2629)
at DeDupeCallTracker "@set library . dedupe (blueocean componentPipeline . js version", returnStdout : 7920 true )
at dedupe (blueocean . js:7943)
at Object.rawFetch split ( blueocean.js:2659 "=",2 )
at Object . fetch last ( blueocean.js:2737 )
at jenkins-js-extension . js:50210
at invokeFunc trim ( jenkins-js-extension.js:7887 )
 at trailingEdge             if ( jenkins-js-extension.js:7934 version != 'master' ) {
trimRestUrl @ blueocean.js:2752
getPrefetchedDataFuture @ blueocean.js:2762
                 error "Pull request @ blueocean targeting ${env . js:2629 CHANGE_TARGET} cannot be based on ${version} branch of component pipeline, should be based on master!"
dedupe @ blueocean.js:7920             }
dedupe @ blueocean.js:7943         }
rawFetch @ blueocean.js:2659     }
fetch @ blueocean.js:2737 }{code}
(anonymous) @ jenkins-js-extension.js shows only as : 50210
invokeFunc @ jenkins-js-extension.js:7887
trailingEdge @ jenkins !image - js 2018 - extension.js:7934
timerExpired @ jenkins 08 - js 07 - extension.js:7922
blueocean.js:18807 [ERROR 18 - io.jenkins.blueocean.dashboard.karaoke.Pager.Step] Error fetching page 17 - fetch log TypeError: Cannot read property 'newStart' of undefined
at jenkins 35 - js-extension 341 . js:51074
at <anonymous>
error @ blueocean.js:18807
(anonymous) @ jenkins-js-extension.js:51100
{quote} png!

jakub@pawlinski.pl (JIRA)

unread,
Aug 7, 2018, 1:18:03 PM8/7/18
to jenkinsc...@googlegroups.com
Jakub Pawlinski updated an issue
Change By: Jakub Pawlinski
Attachment: image-2018-08-07-18-17-28-500.png

jakub@pawlinski.pl (JIRA)

unread,
Aug 7, 2018, 1:18:03 PM8/7/18
to jenkinsc...@googlegroups.com
Jakub Pawlinski updated an issue
Change By: Jakub Pawlinski
Attachment: image-2018-08-07-18-17-35-341.png

jakub@pawlinski.pl (JIRA)

unread,
Aug 7, 2018, 1:18:03 PM8/7/18
to jenkinsc...@googlegroups.com
Jakub Pawlinski updated an issue
Change By: Jakub Pawlinski
Attachment: image-2018-08-07-18-17-57-087.png

jakub@pawlinski.pl (JIRA)

unread,
Aug 7, 2018, 1:19:02 PM8/7/18
to jenkinsc...@googlegroups.com
Jakub Pawlinski updated an issue
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.
{code:java}
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!"
            }
        }
    }
}{code}
shows only as:

!image-2018-08-07-18-17- 35 57 - 341 087 .png!

jakub@pawlinski.pl (JIRA)

unread,
Aug 7, 2018, 1:20:02 PM8/7/18
to jenkinsc...@googlegroups.com
Jakub Pawlinski updated an issue
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.
{code:java}
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!"
            }
        }
    }
}{code}
shows only as:

!image-2018-08-07-18-17-57-087.png!

!image-2018-08-07-18-19-01-833.png!

jakub@pawlinski.pl (JIRA)

unread,
Aug 7, 2018, 1:20:02 PM8/7/18
to jenkinsc...@googlegroups.com
Jakub Pawlinski updated an issue
Change By: Jakub Pawlinski
Attachment: image-2018-08-07-18-19-01-833.png

Saad.Azam@magna.com (JIRA)

unread,
Aug 29, 2018, 7:46:01 AM8/29/18
to jenkinsc...@googlegroups.com
This message was sent by Atlassian Jira (v7.11.2#711002-sha1:fdc329d)

igor.solovko@gmail.com (JIRA)

unread,
Sep 4, 2018, 5:15:03 PM9/4/18
to jenkinsc...@googlegroups.com

similar issue

jakub@pawlinski.pl (JIRA)

unread,
Sep 5, 2018, 11:45:03 AM9/5/18
to jenkinsc...@googlegroups.com

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

Saad.Azam@magna.com (JIRA)

unread,
Feb 8, 2019, 9:20:02 AM2/8/19
to jenkinsc...@googlegroups.com

comment-348310 holds true for me as well.

Saad.Azam@magna.com (JIRA)

unread,
Feb 8, 2019, 9:20:03 AM2/8/19
to jenkinsc...@googlegroups.com
Saad Azam edited a comment on Bug JENKINS-52923
[#comment-348310]  (above) holds true for me as well.

melvin.won@dhl.com (JIRA)

unread,
Sep 3, 2019, 3:17:01 AM9/3/19
to jenkinsc...@googlegroups.com

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.")

 

jakub@pawlinski.pl (JIRA)

unread,
Sep 5, 2019, 9:45:05 AM9/5/19
to jenkinsc...@googlegroups.com
Jakub Pawlinski updated an issue
Change By: Jakub Pawlinski
Attachment: image-2019-09-05-14-44-09-770.png

jakub@pawlinski.pl (JIRA)

unread,
Sep 5, 2019, 9:45:05 AM9/5/19
to jenkinsc...@googlegroups.com
Jakub Pawlinski updated an issue
Change By: Jakub Pawlinski
Attachment: image-2019-09-05-14-44-29-866.png

jakub@pawlinski.pl (JIRA)

unread,
Sep 5, 2019, 9:46:02 AM9/5/19
to jenkinsc...@googlegroups.com
Jakub Pawlinski commented on Bug JENKINS-52923
 
Re: Error Signal Description not displayed in Blue Ocean

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:

 
Reply all
Reply to author
Forward
0 new messages