Forward SubSteps() through wrapper steps#5151
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (6)
🚧 Files skipped from review as they are similar to previous changes (4)
📝 WalkthroughWalkthroughMultiple CI operator step wrappers now expose Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~12 minutes 🚥 Pre-merge checks | ✅ 13 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (13 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Review rate limit: 8/10 reviews remaining, refill in 7 minutes and 8 seconds. Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mdbooth The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
The purpose of this change is to add substep information to ci-operator-step-graph.json to enable much more efficient automated scraping of prow job artifacts. The step graph outputs substeps for steps which implement SubStepReporter, but this is lost when the step is wrapped by LeaseStep, IPPoolStep, or ClusterClaimStep.
|
Flakes /retest-required |
|
Scheduling tests matching the |
|
@mdbooth: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
The purpose of this change is to add substep information to ci-operator-step-graph.json to enable much more efficient automated scraping of prow job artifacts.
The step graph outputs substeps for steps which implement SubStepReporter, but this is lost when the step is wrapped by LeaseStep, IPPoolStep, or ClusterClaimStep.
Summary by CodeRabbit
New Features
Tests