Building an enterprise git repository (the hard bits!)
summary
Relays concrete operational choices and pain points: chosen Bitbucket Server data center with active/passive sites and 6,000+ repos already present, added smart mirrors for geo reads, integrated SAML SSO and SSH key rotation every 90 days, enforce pull‑request only merges with approver metadata, protect branches and forbid force pushes, log pusher vs commit via post-receive hooks for audit, struggled with CI scale when tens of thousands of builds cause full checkouts, built automation for repo provisioning and settings auditing.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:18Overview
- 2:11GitHub
- 3:41Operationalization
- 11:21Safety Best Practices
- 15:03Code Integrity Best Practices
- 17:27Who wrote your code
- 19:11Access control
- 21:03Automation
related talks
28mGitOps for Skeptics: How I Learned to Stop Worrying and Trust the Repo
31mGitHub as a self-sustaining product for large-scale environments
17mNo More Walled Gardens: Removing Barriers with SCM...
21mFighting Git Workflows
32mContinuous Integration and Deployment: Five Lessons Learned
35mGitOps Approaches and Trade-offs
21mDriving Cultural Change to Improve Software Development and CI/CD
47mDeploying Like a Boss: From 2 Servers to 20,000