CI: install ocular via Composer (fixes Scrutinizer coverage upload)#16
Merged
Conversation
scrutinizer-ci.com/ocular.phar now returns HTTP 403 (Cloudflare bot challenge), so the previous wget-based install silently failed with exit code 8. Because the step was continue-on-error, CI stayed green but Scrutinizer never received coverage and every inspection sat pending until the 900s external_code_coverage timeout. Use the scrutinizer/ocular package from Packagist instead, installed via composer global require. Resolves the ocular binary path from \`composer global config bin-dir --absolute\` so it survives any future Composer default-path changes. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #16 +/- ##
=========================================
Coverage 98.07% 98.07%
Complexity 27 27
=========================================
Files 1 1
Lines 52 52
=========================================
Hits 51 51
Misses 1 1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
`scrutinizer-ci.com/ocular.phar` now returns HTTP 403 (Cloudflare bot challenge). The CI step that did `wget -q https://scrutinizer-ci.com/ocular.phar\` was silently exiting with code 8.
Because the step was marked `continue-on-error: true`, GitHub Actions stayed green — but Scrutinizer never received coverage and every inspection sat pending until the 900s `external_code_coverage` timeout fired.
Fix
Install `scrutinizer/ocular` (1.9) from Packagist via `composer global require` instead of wget-ing the phar. Resolves the binary path via `composer global config bin-dir --absolute` so it survives any future Composer default-path changes.
`continue-on-error: true` is preserved on the upload step — Scrutinizer outages shouldn't fail CI.
Test plan
🤖 Generated with Claude Code