Serve chkbuild logs through logs.rubyci.org - #58
Merged
Conversation
rubyci.org currently links to build logs on the public rubyci S3 bucket directly, so every fetch including crawler traffic hits S3 request and egress billing. Fronting the bucket with Fastly caches the immutable timestamped logs for a year, keeps overwritten keys like cur/ on a short TTL, and gives us edge logging and UA control. DNS records are staged as a TODO because certificate issuance needs the ACME challenge from terraform output first. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
vault implied secret storage; these are public read-only build logs, so logs says what it serves. The TLS subscription needs an explicit configuration_id because the account has no default configuration. Picking "HTTP/3 & TLS v1.3" keeps the negotiated protocols in line with http3 on the service, and it is what decides the m.sni.global.fastly.net CNAME target. Co-Authored-By: Claude Fable 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.
rubyci.org links build logs straight at the public
rubyciS3 bucket, so every hit is a billed GET plus egress and repeated reads during triage get no caching. This puts a Fastly service in front of the bucket atlogs.rubyci.org.Timestamped keys under
/log/are immutable and get a one year TTL. Keys that chkbuild overwrites, such asrecent.html, get 300s. The service shields attyo-tokyo-jpto match the bucket region, enables HTTP/3, serves stale on origin error, forces TLS, requires authentication forPURGE, and ships access logs to Datadog.The service, its TLS subscription and both CNAME records are already applied, and
terraform plananddnscontrol previeware clean. Switching the link generation over happens in ruby/rubyci. Existing S3 URLs keep working, so that can land separately.