jenkinsci / jenkinsci/branch-api-plugin
[JENKINS-37369] Multibranch Pipeline: Last build information is not propagated to Jenkins View
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 39
- Forks
- 154
- PR merge metrics
- No merged PRs in 30d
Description
The build information Last Success, Last Failure and Last Duration is not propagated to the Jenkins view. The Jenkins view showing the multibranch pipeline folder always shows N/A. The latest built branch should propagate this build information to the outside view.
---
Originally reported by djviking, imported from: Multibranch Pipeline: Last build information is not propagated to Jenkins View
Raw content of original issue
The build information Last Success, Last Failure and Last Duration is not propagated to the Jenkins view. The Jenkins view showing the multibranch pipeline folder always shows N/A. The latest built branch should propagate this build information to the outside view.
- environment:
Jenkins 2.17, workflow-multibranch 2.8
4 attachments
- [Screen Shot 2017-03-10 at 11.01.44.png](https://issues.jenkins.io/secure/attachment/36382/Screen%20Shot%202017-03-10%20at%2011.01.44.png)
> 
- [Screen Shot 2017-03-10 at 11.10.10.png](https://issues.jenkins.io/secure/attachment/36383/Screen%20Shot%202017-03-10%20at%2011.10.10.png)
> 
- [jenkinspipeline1.png](https://issues.jenkins.io/secure/attachment/33604/jenkinspipeline1.png)
> 
- [jenkinspipeline2.png](https://issues.jenkins.io/secure/attachment/33605/jenkinspipeline2.png)
> 
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in the branch-api-plugin code that represents multibranch pipeline folders and exposes build information to Jenkins views. Reproduce the N/A values using the reported Jenkins 2.17 and workflow-multibranch 2.8 environment, then trace how the latest built branch is selected. Done means Last Success, Last Failure, and Last Duration appear in the outer view instead of N/A.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100