That's interesting, for me, the nested view always shows the grey "ABORTED" status.

BTW, you should probably report your second statement: "Moreover, it is impossible..." as a separate issue.

>Always shows fail whenever we use a build pipeline as a nested view. Even if there is no issues in the build pipeline.

NestedView shows worst status within BuildPipelineView.getItems().

    @Override
    public Collection<TopLevelItem> getItems() {
        return Hudson.getInstance().getItems();
    }

>Moreover, it is impossible to add a nested view if the first one is a build pipeline.

I could not reproduce the problem.
Please report with detailed procedure as another issue, if the problem remains.

Thanks Yoichi, that looks great!

Still have some problems with this fix! It looks great if you have just one pipeline! But if you have multiple pipelines that uses the same builds (except the starting build off course) then this is a problem still. The thing that happens when one build fails in one of your pipelines is that all your pipelines get red! This ain't good at all! The goal here should be to only get the pipeline red or green that fails or succeeds at the moment! Don't know how to solve that though!

This is still not fixed. As stated, if one job in one pipeline is red - ALL pipeline views are red. This is really bad. Can we reopen?

To reproduce - create two pipelines (each with different jobs). Create two Build Pipeline views. Add the "Status" Ball to each view. Break a job in one view, and both views are red. v1.5.1

Reopening (hope that is ok). See comments.