reapply gromit config to main #254
Draft
probelabs / Visor: performance
succeeded
Nov 26, 2025 in 1m 2s
✅ Check Passed
performance check completed successfully with no issues found.
Details
📊 Summary
- Total Issues: 1
🔍 Failure Condition Results
Passed Conditions
- global_fail_if: Condition passed
Issues by Category
Performance (1)
- ℹ️ .github/workflows/release.yml:70 - The
goreleaserjob serially executes package building (using GoReleaser) and Docker image building/pushing. The subsequent testing jobs (upgrade-deb,upgrade-rpm) depend on the entire job's completion, including the time-consuming Docker operations, even though they only need the generated packages. This serial execution unnecessarily lengthens the critical path of the CI pipeline.
Powered by Visor from Probelabs
💡 TIP: You can chat with Visor using /visor ask <your question>
Annotations
Check notice on line 342 in .github/workflows/release.yml
probelabs / Visor: performance
performance Issue
The `goreleaser` job serially executes package building (using GoReleaser) and Docker image building/pushing. The subsequent testing jobs (`upgrade-deb`, `upgrade-rpm`) depend on the entire job's completion, including the time-consuming Docker operations, even though they only need the generated packages. This serial execution unnecessarily lengthens the critical path of the CI pipeline.
Raw output
To optimize the workflow's execution time, separate the Docker image building and pushing logic into a new job. This new job can run in parallel with the package testing jobs. The current `goreleaser` job would be responsible only for building packages and uploading artifacts, allowing dependent jobs (testing and image building) to start earlier and run concurrently, reducing total wall-clock time.
Loading