Repository navigation
RHIDP-15240: replace RHEL 9 references with RHEL 10 - #2532
deerskindoll wants to merge 10 commits into
Conversation
… backport (redhat-developer#2496) Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com> Co-authored-by: Fabrice Flore-Thébault <ffloreth@redhat.com>
…#2498) The link text said "Logging for" but the destination page title is "Logging and monitoring on Amazon EKS". Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
…-developer#2483) * chore: generalize release-1.* branch patterns for 2.y support GitHub Actions branch filters hardcoded release-1.** / rhdh-1.** / 1.**.x, and pr.yml had already grown a manually-curated release-1.**/release-2.** pair. Generalize all of these to digit-agnostic patterns (release-[0-9]+.**, etc.) so CI keeps working across future minor/major release branches without needing a manual update at every cut. Part of the upstream build-infrastructure audit for 2.y readiness. Co-authored-by: Cursor <cursoragent@cursor.com> * chore: drop EOL branch filters and align release pattern Remove dead rhdh-* and *.x workflow triggers, and use 'release-[0-9]+.[0-9]+' for consistency with other RHDH repos. Co-authored-by: Cursor <cursoragent@cursor.com> --------- Co-authored-by: Cursor <cursoragent@cursor.com>
…developer#2506) Co-authored-by: GitHub Actions <github-actions@github.com>
Shellcheck Analysis ResultsChanged shell scripts in this PR: 1 Scripts analyzed:
Check the Files changed tab for detailed shellcheck suggestions. All findings are reported as warnings and won't block the PR. Automated shellcheck analysis • See shellcheck.net for details |
PR Build ResultsBuild failed -- 36/36 titles | 89s Link Validation (lychee)Total: 2726 | OK: 2576 | Errors: 1 | Excluded: 106 | Timeouts: 0
Content Quality AssessmentCQA Report
SummaryChecks: 22 total, 21 pass, 1 fail 22 checks: 21 pass, 1 fail Run Updated 2026-10-13 11:28:51 UTC |
|
deerskindoll
changed the title
|
|
|
||
| [role="_abstract"] | ||
| To enable the Nexus Repository Manager plugin, set the `disabled` property to `false`. | ||
| Enable the Nexus Repository Manager plugin and configure its frontend mount point to view build artifact details on entity pages in {product-short}. |
There was a problem hiding this comment.
should we clarify that this plugin in community-supported and available from the Optional Extras catalog in 2.1?
There was a problem hiding this comment.
I could also just yeet this whole thing. and add Nexus to the list of plugins we'll have to remove from docs. or start slapping a huge warning on the procedures that they're for plugins that are community supported
|
looks good but the PR title is about RHEL10 and there are updates here for nexus plugin install intstuctions, which could be replaced by a pointer to https://github.com/redhat-developer/rhdh-plugin-export-overlays/blob/release-2.1/workspaces/nexus-repository-manager/metadata/backstage-community-plugin-nexus-repository-manager.yaml#L29 as there is no longer configuration yaml needed. |
| - package: oci://ghcr.io/redhat-developer/rhdh-plugin-export-overlays/backstage-community-plugin-nexus-repository-manager:__<tag>__ | ||
| disabled: false | ||
| pluginConfig: | ||
| dynamicPlugins: |
There was a problem hiding this comment.
this is all obsolete. See https://github.com/redhat-developer/rhdh-plugin-export-overlays/blob/release-2.1/workspaces/nexus-repository-manager/metadata/backstage-community-plugin-nexus-repository-manager.yaml#L29 where we have removed default configuration yaml as of 2.1
| `isNexusRepositoryManagerAvailable`:: A condition that renders the component only for entities that have Nexus Repository Manager annotations. | ||
|
|
||
| .Additional sources | ||
| * link:https://github.com/redhat-developer/rhdh-plugin-export-overlays/blob/main/workspaces/nexus-repository-manager/metadata/backstage-community-plugin-nexus-repository-manager.yaml#L30[Latest Nexus Repository Manager metadata for {product-very-short}] |
There was a problem hiding this comment.
for 2.1 you probably want to use the release-2.1 branch instead of main.
at this point, the PR is somewhat obsolete. how about I simply replace all mentions of RHEL 9 in our docs (in AEM) and leave Nexus plugin be for the time being. the intent of this PR was good, including Nexus was an absolute coincidence and now I feel I'm juggling too many balls at once. |
|
@nickboldt I updated rhel9 references in AEM, Nexus plugin will be removed from docs in AEM by Gerry |
IMPORTANT: Do Not Merge - To be merged by Docs Team Only
Version(s):
release-2.1Issue:
https://redhat.atlassian.net/browse/RHIDP-15240Preview: