You may ask that this Pipeline build wait for completion of the downstream build.
In that case the return value of the step is an object on which you can obtain the following read-only properties:
so you can inspect its result
and so on.
number
result
SUCCESS
, UNSTABLE
, or FAILED
(may be null for an ongoing build)displayName
#123
but sometimes set to, e.g., an SCM commit identifierdescription
id
number
as a stringtimeInMillis
startTimeInMillis
duration
previousBuild
nextBuild
absoluteUrl
buildVariables
env
changeSets
kind
and is a list of commits; each commit has a commitId
, timestamp
, msg
, author
, and affectedFiles
each of which has an editType
and path
; easiest to use this inside a method marked @NonCPS
to avoid storing intermediate valuesrawBuild
hudson.model.Run
with further APIs, only for administrator-approved scripts outside the sandbox; you will generally need to use this inside a method marked @NonCPS
to avoid storing intermediate valuesIf you do not wait, this step succeeds so long as the downstream build can be added to the queue (it will not even have been started). In that case there is currently no return value.