#279 print judges and fbe versions at startup - #279
Open
VasilevNStas wants to merge 1 commit into
Open
Conversation
When diagnosing CI failures it's often unclear which version of judges or fbe was used. Print both versions to stdout before running judges update, so baza.rb (or any operator reading logs) can see the exact gem versions in the job output. Use `gem specification` for fbe since it's not a standalone CLI.
Contributor
Author
Why this mattersWhen a job fails in CI or on a production host, the first question is always "which version ran?" Without this, debugging means:
After this PR, every job log starts with: One line, zero guesswork. Saves 5–10 minutes per debugging session, which adds up fast when chasing regressions across 50+ judges. |
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.
When diagnosing CI or job failures it's often unclear which version of
judgesorfbewas used. This is especially important now thatfbeandjudgeshave broad version constraints (~>0).What this PR does
Prints both gem versions to stdout before
judges updateruns:baza.rb(or any operator reading job logs) can now see the exact versions without checkingGemfile.lockor the Docker image.For
judges— usesjudges --version(CLI flag).For
fbe— uses Ruby'sGem::Specificationsince fbe has no standalone CLI.Checklist
bundle exec rubocop— 0 offencesbundle exec rake— all tasks pass@yegor256 please review