Point build log links at logs.rubyci.org - #661
Merged
Merged
Conversation
Log links were built from the server's registered URI, which for the chkbuild servers is a direct URL into the public rubyci S3 bucket. Route them through the Fastly service in front of the same bucket instead, so repeated access during triage is served from the edge. Object keys are unchanged, and the fetch and listing paths still talk to S3 directly. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The existing pattern only matched db/test.sqlite3, so the per-worker databases rake test writes alongside it (db/test.sqlite3_0 and friends) showed up as untracked. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Build log links were generated from the public
rubyciS3 bucket. A Fastly service now fronts the same bucket atlogs.rubyci.org, so pointing links there cuts S3 GET and egress cost and serves repeat access during triage from the edge.Server#log_base_uriswaps the host for servers registered under the bucket and leaves every other server on its registered URI, sologuri,diffuri,failuriandrecenturiall follow. Object keys are unchanged, and the/coverageand/doxygenredirects move too.The listing and fetch paths still talk to S3 directly.
failtxt_urianddifftxt_uristay on S3 as well, since they only feedLogExcerpt.capture, which can run before the object is uploaded, and a 404 cached under the one year TTL on/log/keys would outlive any chance to recover it.Direct S3 URLs keep working, so this is reversible. The second commit widens the
.gitignorepattern so the per-worker databasesrake testwrites are ignored.