This issue is archived. You can view it, but you can't modify it. Learn more

ExportXMLWordPrintable

      I need to easily navigate between upstream and downstream builds. Presently it is easy to navigate from downstream to upstream build because downstream build has upstream build as a cause. But navigating from upstream to downstream build is complicated when `wait: false` is used in the build step.

      When `wait` it is set to false, a build is triggered. But there is no way for the pipeline to know which build that was.

      When `wait` is false, the returned value is `org.codehaus.groovy.runtime.NullObject`.

      What will be useful is to have a parameter where build is triggered, then step waits until it has an id and returns only then.

      Or is there any other easy way to figure out triggered builds?

            Assignee:
            Stuart Rowe
            Reporter:
            akostadinov
            Archiver:
            Jenkins Service Account

              Created:
              Updated:
              Resolved:
              Archived: