[JIRA] (JENKINS-41579) API for Pipeline level for causeOfBlockage

[vivek.pan...@gmail.com (JIRA)]

Title: Message Title

Vivek Pandey commented on JENKINS-41579   Re: API for Pipeline level for causeOfBlockage James Dumay causeOfBlockage is going to appear in the queued item of pipeline run. We can't provide it as part of run response as causeOfBlockage is applicable only to queued item. UI can call queue API to check if pipeline has queued item. GET http://localhost:8080/jenkins/blue/rest/organizations/jenkins/pipelines/pipeline1/queue/ [ { "_class" : "io.jenkins.blueocean.service.embedded.rest.QueueItemImpl", "_links" : { "parent" : { "_class" : "io.jenkins.blueocean.rest.hal.Link", "href" : "/blue/rest/organizations/jenkins/pipelines/pipeline1/" }, "self" : { "_class" : "io.jenkins.blueocean.rest.hal.Link", "href" : "/blue/rest/organizations/jenkins/pipelines/pipeline1/queue/4/" } }, "causeOfBlockage" : "Waiting for next available executor", "expectedBuildNumber" : 4, "id" : "4", "organization" : "jenkins", "pipeline" : "pipeline1", "queuedTime" : "2017-02-16T12:07:21.725-0800" } ] PR is up there https://github.com/jenkinsci/blueocean-plugin/pull/837 Add Comment   This message was sent by Atlassian JIRA (v7.1.7#71011-sha1:2526d7c) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.