Skip to content

WINC-1456: adds windows-exporter jobs for 4.22#79273

Open
wgahnagl wants to merge 1 commit into
openshift:mainfrom
wgahnagl:WINC-1456
Open

WINC-1456: adds windows-exporter jobs for 4.22#79273
wgahnagl wants to merge 1 commit into
openshift:mainfrom
wgahnagl:WINC-1456

Conversation

@wgahnagl
Copy link
Copy Markdown
Contributor

@wgahnagl wgahnagl commented May 13, 2026

This is needed so this
openshift/prometheus-community-windows_exporter#131

PR can merge

Summary

Adds OpenShift CI configuration for building the prometheus-community-windows_exporter for the release-4.22 branch. The configuration defines build parameters and a test job that:

  • Uses the rhel-9-golang-1.25-openshift-4.22 builder image (updated from golang 1.24 to 1.25)
  • Clones the OpenShift promu build tool from the master branch
  • Builds the Windows exporter binary for Windows (via GOOS=windows ./promu build -v)
  • Sets resource limits (4Gi memory) and requests (100m CPU, 200Mi memory)

This CI configuration is required to enable the related prometheus-community-windows_exporter repository PR to merge.

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label May 13, 2026
@openshift-ci-robot
Copy link
Copy Markdown
Contributor

openshift-ci-robot commented May 13, 2026

@wgahnagl: This pull request references WINC-1456 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target either version "5.0." or "openshift-5.0.", but it targets "WMCO 10.19.0" instead.

Details

In response to this:

This is needed so this
openshift/prometheus-community-windows_exporter#131

PR can merge

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci Bot requested a review from jrvaldes May 13, 2026 20:19
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 13, 2026

Walkthrough

A CI configuration file is added for the Windows exporter on the release-4.22 branch, specifying the base image, resource constraints, and a build job that compiles the exporter for Windows using promu.

Changes

Windows Exporter Release-4.22 CI Configuration

Layer / File(s) Summary
Build environment and resource constraints
ci-operator/config/openshift/prometheus-community-windows_exporter/openshift-prometheus-community-windows_exporter-release-4.22.yaml (lines 1–21)
Base image 4.22 in the ocp namespace and builder image stream tag rhel-9-golang-1.25-openshift-4.22 are declared. Default resource limits (memory 4Gi cap; CPU 100m and memory 200Mi request) apply to all components.
Build job definition and metadata
ci-operator/config/openshift/prometheus-community-windows_exporter/openshift-prometheus-community-windows_exporter-release-4.22.yaml (lines 22–40)
Test job as: build clones openshift/promu from master, installs it, and runs GOOS=windows ./promu build -v to compile the Windows exporter. Generated metadata captures branch release-4.22, org openshift, and repo prometheus-community-windows_exporter.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 11 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Title check ⚠️ Warning The PR title mentions 'windows-exporter jobs for 4.22' which aligns with the new config file added, but the PR objectives indicate the actual purpose is updating golang from 1.24 to 1.25, which is not reflected in the title. Update the title to reflect the actual primary change: something like 'WINC-1456: Update golang from 1.24 to 1.25 for windows-exporter 4.22' to accurately convey the main objective.
✅ Passed checks (11 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names ✅ Passed PR adds a YAML CI configuration file, not Ginkgo tests. The check for "Stable and Deterministic Test Names" applies only to Ginkgo test definitions (It, Describe, etc.), which are absent.
Test Structure And Quality ✅ Passed Custom check for Ginkgo test code quality is not applicable. This PR adds a CI operator config file (YAML), not test code. No Ginkgo tests to review.
Microshift Test Compatibility ✅ Passed This PR adds only a CI operator configuration file (YAML), not any Ginkgo e2e tests. The MicroShift compatibility check is designed for e2e tests and is not applicable here.
Single Node Openshift (Sno) Test Compatibility ✅ Passed This PR adds a CI operator configuration file (YAML), not Ginkgo e2e tests. The custom check applies only to Ginkgo test additions. No test code is present in this PR.
Topology-Aware Scheduling Compatibility ✅ Passed CI-operator build config file, not a deployment manifest or controller. No scheduling constraints or topology assumptions present. Check not applicable.
Ote Binary Stdout Contract ✅ Passed Check not applicable. PR adds only a YAML CI configuration file, not test code or binaries. The OTE Binary Stdout Contract check applies to Go test code, not configuration files.
Ipv6 And Disconnected Network Test Compatibility ✅ Passed This PR adds a CI operator YAML configuration file, not Ginkgo e2e tests. The custom check applies only to new e2e tests and is not applicable here.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

Comment @coderabbitai help to get the list of available commands and usage tips.

@openshift-ci openshift-ci Bot requested a review from mansikulkarni96 May 13, 2026 20:19
@wgahnagl wgahnagl changed the title WINC-1456: updates from golang-1.24 to 1.25 WINC-1456: adds windows-exporter jobs for 4.22 May 13, 2026
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In
`@ci-operator/config/openshift/prometheus-community-windows_exporter/openshift-prometheus-community-windows_exporter-release-4.22.yaml`:
- Around line 28-32: The job currently clones openshift/promu using "git clone
--branch master" which is non-reproducible; change the git clone command to pin
a specific immutable revision (a tag or commit SHA) instead of master (replace
the "git clone --branch master https://github.com/openshift/promu.git
openshift-promu" line), then continue to install and run promu as before (the
subsequent commands
GOBIN=/go/src/github.com/openshift/prometheus-community-windows_exporter go
install . and GOOS=windows ./promu build -v remain unchanged) so the build uses
a known stable promu version.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository YAML (base), Central YAML (inherited)

Review profile: CHILL

Plan: Enterprise

Run ID: cd3c9a38-7563-4f44-89d6-5bd9b886d001

📥 Commits

Reviewing files that changed from the base of the PR and between 026bb90 and 258d744.

📒 Files selected for processing (1)
  • ci-operator/config/openshift/prometheus-community-windows_exporter/openshift-prometheus-community-windows_exporter-release-4.22.yaml

Comment on lines +28 to +32
git clone --branch master --single-branch https://github.com/openshift/promu.git openshift-promu
cd openshift-promu/
GOBIN=/go/src/github.com/openshift/prometheus-community-windows_exporter go install .
cd /go/src/github.com/openshift/prometheus-community-windows_exporter
GOOS=windows ./promu build -v
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major | ⚡ Quick win

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
set -euo pipefail

echo "Default branch ref:"
git ls-remote --symref https://github.com/openshift/promu.git HEAD

echo
echo "Existing branch refs (master/main):"
git ls-remote --heads https://github.com/openshift/promu.git master main || true

echo
echo "Recent tags to choose a pinned version from:"
git ls-remote --tags https://github.com/openshift/promu.git | tail -n 20

Repository: openshift/release

Length of output: 1069


🏁 Script executed:

#!/bin/bash
set -euo pipefail

# Check if the file exists
FILE="ci-operator/config/openshift/prometheus-community-windows_exporter/openshift-prometheus-community-windows_exporter-release-4.22.yaml"
if [ -f "$FILE" ]; then
  echo "File exists. Extracting lines 25-35 for context:"
  sed -n '25,35p' "$FILE" | cat -n
  echo
  echo "Full file for complete context:"
  cat -n "$FILE"
else
  echo "File does not exist at: $FILE"
  echo "Listing available CI configs in the directory:"
  find ci-operator/config/openshift -name "*prometheus*windows*" -o -name "*windows_exporter*" 2>/dev/null | head -20
fi

Repository: openshift/release

Length of output: 1941


Pin openshift/promu to an immutable revision.

Line 28 clones master, which makes this job non-reproducible and can break when upstream changes. Pin to a tag or commit SHA (stable versions v0.1.0 through v0.6.1 are available).

Suggested change
-        git clone --branch master --single-branch https://github.com/openshift/promu.git openshift-promu
-        cd openshift-promu/
-        GOBIN=/go/src/github.com/openshift/prometheus-community-windows_exporter go install .
-        cd /go/src/github.com/openshift/prometheus-community-windows_exporter
+        GOBIN=/go/src/github.com/openshift/prometheus-community-windows_exporter \
+          go install github.com/openshift/promu@<tag-or-commit-sha>
+        cd /go/src/github.com/openshift/prometheus-community-windows_exporter
         GOOS=windows ./promu build -v
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In
`@ci-operator/config/openshift/prometheus-community-windows_exporter/openshift-prometheus-community-windows_exporter-release-4.22.yaml`
around lines 28 - 32, The job currently clones openshift/promu using "git clone
--branch master" which is non-reproducible; change the git clone command to pin
a specific immutable revision (a tag or commit SHA) instead of master (replace
the "git clone --branch master https://github.com/openshift/promu.git
openshift-promu" line), then continue to install and run promu as before (the
subsequent commands
GOBIN=/go/src/github.com/openshift/prometheus-community-windows_exporter go
install . and GOOS=windows ./promu build -v remain unchanged) so the build uses
a known stable promu version.

@openshift-merge-bot openshift-merge-bot Bot added the rehearsals-ack Signifies that rehearsal jobs have been acknowledged label May 13, 2026
@openshift-merge-bot
Copy link
Copy Markdown
Contributor

[REHEARSALNOTIFIER]
@wgahnagl: no rehearsable tests are affected by this change

Note: If this PR includes changes to step registry files (ci-operator/step-registry/) and you expected jobs to be found, try rebasing your PR onto the base branch. This helps pj-rehearse accurately detect changes when the base branch has moved forward.

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse list to get an up-to-date list of affected jobs
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 13, 2026

@wgahnagl: all tests passed!

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Copy link
Copy Markdown
Contributor

@jrvaldes jrvaldes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci Bot added the lgtm Indicates that a PR is ready to be merged. label May 14, 2026
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 14, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jrvaldes, wgahnagl

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label May 14, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. rehearsals-ack Signifies that rehearsal jobs have been acknowledged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants