Replace pipeline-stage-view with graph-view in the setup wizard

[NotMyFault]

The change proposed replaces the pipeline-stage-view plugin with the pipeline-graph-view plugin in the setup wizard.
Given the pipeline-stage-view is closely tied to BO - which was removed from the setup wizard some time ago - I'd like to suggest replacing it with the graph-view plugin, providing a more modern overview of your pipelines.

It's worth mentioning that the graph-view plugin is under active development and not feature-stalled like the stage view one (thanks to @timja 💯 )

Testing done

The plugin is installed as intended, when setting up a new instance.

Proposed changelog entries

• JENKINS-XXXXX, human-readable text

Proposed upgrade guidelines

N/A

Submitter checklist

Beta 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

@mention

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

Maintainer checklist

Beta 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).

[daniel-beck]

pipeline-stage-view is closely tied to BO

How so? AFAICT they're completely unrelated implementations, all they have in common is use stages (pipeline-stage-step) to organize content. From that perspective, Graph View is just as tied to BO.

[NotMyFault]

pipeline-stage-view is closely tied to BO

How so? AFAICT they're completely unrelated implementations, all they have in common is use stages (pipeline-stage-step) to organize content. From that perspective, Graph View is just as tied to BO.

Oh, I was believing that stage-view was the BO attempt to view pipelines, not that it's a dependency of BO.
But I would like to replace it still, given the stage view provides a more modern UI integrating with modern Jenkins, layout and UX wise. The feature-stallness of stage-view is another point I'd like to see it replaced.

[mawinter69]

In your initial description you have 2 places where you wrote stage-view but meant graph-view I think.

I'd like to suggest replacing it with the graph-view plugin, providing a more modern overview over your pipelines.
It's worth mentioning that the graph-view plugin is under active development and not feature-stalled like the stage view one

[NotMyFault]

In your initial description you have 2 places where you wrote stage-view but meant graph-view I think.

I'd like to suggest replacing it with the graph-view plugin, providing a more modern overview over your pipelines.
It's worth mentioning that the graph-view plugin is under active development and not feature-stalled like the stage view one

Oh absolutely 🤦
Thanks for finding, I'll fix it right away.