DevOps automation with Go
summary
Company runs ~120,000,000 lines of Go plus 2.8M external lines, with three release channels and weekly production releases; a small release API receives build tgz and metadata, validates MD5 while streaming, writes artifacts and triggers per-product release scripts. A freshdesk gitlab bridge injects escalation buttons and copies comments/attachments. Webhooks enforce version-match checks and auto-transition issue boards. Daily logs feed a race-detection issue creator that files GitLab issues. Automatic tagging bumps ~20 internal libraries.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 1:58DevOps pipeline at RestorePoint
- 2:40Release API tool
- 4:27Freshdesk GitLab bridge
- 5:51Merge safety version check
- 6:55GitLab board automation
- 8:18Race conditions in Go builds
- 10:47Go module versioning
- 11:48Summary
related talks
34mGitOps for the people
48mDevops@Scale
30mHow Go Helped Accelerate Software Delivery at the BBC
35mGitOps - Operations by Pull Request
30mDevOps and Agility Immersed in the Production Factory
55mDevOps @Scale (Greek Tragedy in 3 Acts)
43mDevOps for Mere Mortals
15mManaging Third Party Software in your GitOps Setups