Elevated Build Latency

Summary

Build time increased from 12 seconds to 47 seconds after adding SCSS compilation for three new component files. The deployment pipeline completed successfully but exceeded the informal 30-second threshold.

Impact

Zero users were affected. The site was never unavailable. The only observable effect was that the GitHub Actions job took longer to complete, which delayed the green checkmark on the commit by approximately 35 seconds.

Timeline

• 14:22 UTC — Commit pushed adding _components.scss partials for status page, encrypted content, and redacted text shortcode
• 14:23 UTC — Build started. Hugo compilation took 47 seconds (previous baseline: 12 seconds)
• 14:24 UTC — Build completed successfully. No errors
• 14:31 UTC — Author noticed the longer build time while checking the Actions tab
• 14:32 UTC — Root cause identified

Root Cause

Hugo’s SCSS pipeline recompiled all partials when new @import statements were added to main.scss. The extended build time was caused by Dart Sass processing three new files with nested selectors and media queries. This is normal behavior, not a bug.

Resolution

No action taken. A 47-second build for a static site with custom SCSS is within acceptable parameters. The informal threshold of 30 seconds was aspirational, not contractual.

Action Items

• Investigate root cause
• Confirm no user impact
• Consider setting a CI timeout to catch genuine build hangs
• Establish a formal build time budget (stretch goal)