Display Console Output on the build page (behind an experimental flag)

[janfaracik]

This PR adds the Console Output to the build page (behind an experimental flag). This reduces the amount of clicks it takes to get to the console, making it easy to see build output.

The implementation allows for console providers (such as Pipeline Graph View) to override what displays on the build page.

Why the new-build-page.flag flag? Modifying the build pages is pretty fiddly due to the sidebar and summary items, so I've put this behind a flag to not disrupt existing users layouts unless they explicitly want to. Keen to make more use of this flag going forward to avoid disruption/allow for more iterative work on things like this.

Freestyle

Pipeline

Flag

Testing done

• Widget hides if the flag is disabled
• Widget shows if the flag is enabled
• Existing console works as expected

Proposed changelog entries

• Add the option to display the Console Output on the build page (behind an experimental flag)

Proposed upgrade guidelines

N/A

Submitter checklist

Preview Give feedback

1. The Jira issue, if it exists, is well-described.
2. The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples). Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. For new APIs and extension points, there is a link to at least one consumer.

Desired reviewers

@jenkinsci/sig-ux

Before the changes are marked as ready-for-merge:

Maintainer checklist

Preview Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[A1exKH]

LGTM.

[timja]

I'm getting this:

[timja]

I don't have pipeline graph view installed on this instance or any other console provider

[janfaracik]

I don't have pipeline graph view installed on this instance or any other console provider

Ah great spot, hadn't considered that that prop could be null. Defaults to the DefaultConsoleProvider now 👍

[timja]

LGTM!

[timja]

/label ready-for-merge

---

This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback.

Thanks!