# Build history list as the main view of a job

**URL:** https://community.jenkins.io/t/build-history-list-as-the-main-view-of-a-job/17015
**Category:** Ask a question
**Tags:** question
**Created:** [July 12, 2024, 9:29am UTC](https://community.jenkins.io/t/build-history-list-as-the-main-view-of-a-job/17015 "2024-07-12T09:29:27Z")
**Posts on this page:** 7
**Page:** 1

<div class="post-metadata">

### Author: ![yanivyam](https://avatars.discourse-cdn.com/v4/letter/y/ecae2f/32.png) [@yanivyam](https://community.jenkins.io/u/yanivyam)
#### Post date: [July 12, 2024, 9:29am UTC](https://community.jenkins.io/t/build-history-list-as-the-main-view-of-a-job/17015/1 "2024-07-12T09:29:27Z")

</div>

Hello,

It would be great to have the option to view the build history as a list in the main section of the job page instead of the Pipeline stage view.

We have many builds for each job and need to be able to have a clear view of the builds - the history displayed in the side bar is not enough. It would be great to have the default job view in a similar manner as the Blue Ocean build view.

I wonder if there is a plugin that provides this functionality.

Jenkins setup:  
Version: 2.401.3

Thanks,  
Yaniv

---

<div class="post-metadata">

### Author: ![mawinter69](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/mawinter69/32/1625_2.png) [@mawinter69](https://community.jenkins.io/u/mawinter69)
#### Post date: [July 12, 2024, 10:06am UTC](https://community.jenkins.io/t/build-history-list-as-the-main-view-of-a-job/17015/2 "2024-07-12T10:06:02Z")

</div>

What exactly are you missing from the sidepanel?

---

<div class="post-metadata">

### Author: ![yanivyam](https://avatars.discourse-cdn.com/v4/letter/y/ecae2f/32.png) [@yanivyam](https://community.jenkins.io/u/yanivyam)
#### Post date: [July 12, 2024, 2:32pm UTC](https://community.jenkins.io/t/build-history-list-as-the-main-view-of-a-job/17015/3 "2024-07-12T14:32:01Z")

</div>

The side pannel is too narrow and not at the focus of the builds screen. It’s not easy to scroll through the builds. Our developers run many builds per job, and it would be nice to be able to scroll and see previous builds with the mouse instead of clicking on the up/down arrows on the sidebar.

Also, it does not display information such as build time, button to retrigger, and possibly other details, like which user triggered the job, which branch was built, etc.

Thanks,  
Yaniv

---

<div class="post-metadata">

### Author: ![mawinter69](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/mawinter69/32/1625_2.png) [@mawinter69](https://community.jenkins.io/u/mawinter69)
#### Post date: [July 12, 2024, 2:57pm UTC](https://community.jenkins.io/t/build-history-list-as-the-main-view-of-a-job/17015/4 "2024-07-12T14:57:43Z")

</div>

I’m not aware of a plugin that provides this

---

<div class="post-metadata">

### Author: ![sodul](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/sodul/32/7828_2.png) [@sodul](https://community.jenkins.io/u/sodul)
#### Post date: [July 12, 2024, 3:29pm UTC](https://community.jenkins.io/t/build-history-list-as-the-main-view-of-a-job/17015/5 "2024-07-12T15:29:27Z")

</div>

We actually have an internal jenkins library to augment our pipelines when they start with some of these details.

We install the [build user vars](https://plugins.jenkins.io/build-user-vars-plugin/) plugin and configure it globally (very important) so it can actually work well.

All our pipelines call `pipelineInit()` before the `pipeline {}` block of our jenkinsfiles.

The `pipelineInit()` ‘step’ calls our custom `AugmentJobDescription()` which then does this:

```auto
    userName = env.BUILD_USER_ID
    if (user_name) {
        currentBuild.displayName += ' ' + userName
    }
    description = [currentBuild.description]
    // add more details like start time, etc...

    // resolve the branch name even if parameterized:
    branch = env.getEnvironment().expand(scm.branches[0].name)
    if (branch) {
        description.add(branch)
    }
    currentBuild.description = description.join(' ')

```

We include other standardized details such as the name of the target deployment environment, aws account, etc…

This is very useful, although not as comprehensive as what you were looking for.

---

<div class="post-metadata">

### Author: ![sodul](https://dub1.discourse-cdn.com/flex013/user_avatar/community.jenkins.io/sodul/32/7828_2.png) [@sodul](https://community.jenkins.io/u/sodul)
#### Post date: [July 12, 2024, 5:23pm UTC](https://community.jenkins.io/t/build-history-list-as-the-main-view-of-a-job/17015/6 "2024-07-12T17:23:33Z")

</div>

Have you tried the BlueOcean view?

Here is an example of what the job view looks like. It shows the status, duration, how long ago it completed (hover will show you the exact date and time).

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/jenkins/original/2X/8/88e7f1e00def61a94ba63aad767efe1213079e99.png)

In this screenshot you can see the augmented displayName in the RUN column as well as the branch name from currentBuild.description that got set by our jenkins library.

BlueOcean is no longer being actively developed (no new features), but it is still being maintained for bug fixes and security so it should be usable for quite a while.

If you loads of runs it fill load in chunks (click a Show More button). I think this one fits your asks.

> **[Blue Ocean](https://www.jenkins.io/doc/book/blueocean/)**
>
> Jenkins – an open source automation server which enables developers around the world to reliably build, test, and deploy their software

---

<div class="post-metadata">

### Author: ![yanivyam](https://avatars.discourse-cdn.com/v4/letter/y/ecae2f/32.png) [@yanivyam](https://community.jenkins.io/u/yanivyam)
#### Post date: [July 13, 2024, 10:29am UTC](https://community.jenkins.io/t/build-history-list-as-the-main-view-of-a-job/17015/7 "2024-07-13T10:29:36Z")

</div>

Yes, I am aware of Blue Ocean. It would be great to have the same build view of Blue Ocean in the standard Jenkins theme, since Blue Ocean is deprecated and not in active development.
