[JENKINS-59599] Returning related triggered builds from Jenkins' REST API

Currently, related triggered builds are displayed on the build page of a triggered build:

 

However, I have some processing that could benefit from being able to read this information. Can we expose this in the output of the build REST API?

Currently, this is all we get:

```
{
"_class" : "hudson.model.FreeStyleBuild",
"actions" : [
{
"_class" : "hudson.model.CauseAction",
"causes" : [
{
"_class" : "com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritCause",
"shortDescription" : "Triggered by Gerrit: https://aa.bb.cc/c/repository-name/+/513530"
}
]
},
{
```

 

---
Originally reported by dsoprea, imported from: Returning related triggered builds from Jenkins' REST API

• assignee: rsandell
  
• status: Open
  
• priority: Minor
  
• component(s): gerrit-trigger-plugin
  
• resolution: Unresolved
  
• votes: 0
  
• watchers: 1
  
• imported: 2025-12-07
  

Raw content of original issue

Currently, related triggered builds are displayed on the build page of a triggered build:




 


However, I have some processing that could benefit from being able to read this information. Can we expose this in the output of the build REST API?


Currently, this is all we get:



{

  "_class" : "hudson.model.FreeStyleBuild",

  "actions" : [

    {

      "_class" : "hudson.model.CauseAction",

      "causes" : [

        {

          "_class" : "com.sonyericsson.hudson.plugins.gerrit.trigger.hudsontrigger.GerritCause",

          "shortDescription" : "Triggered by Gerrit: https://aa.bb.cc/c/repository-name/+/513530"

        }

      ]

    },

    { 



 

1 attachment

- [image-2019-09-30-23-43-35-510.png](https://issues.jenkins.io/secure/attachment/48895/image-2019-09-30-23-43-35-510.png)
> 

Start by tracing the Jenkins build REST API in gerrit-trigger-plugin and compare it with the related triggered-build information shown on a build page. Identify the API representation and entry point responsible for build data; done means related triggered builds are exposed in the build API output. The issue names no files or tests, so locate those before implementation.

Written by the indexing model from the issue text.