FY21-Q1 Nick Thomas (Create:Source Code Staff Backend Engineer) OKR: Safeguard future productivity with projectless repositories
Key Results
-
Refactor Blob
to remove project references -
Refactor Repository
to remove project references -
Refactor Commit
to remove project references -
0 regressions introduced as a result of introducing snippet / group repos - Some bugs discovered and fixed behind a feature flag, nothing impacting
- Group repos not introduced yet
- Refactoring
Gitlab::Shell
did introduce a regression
-
0 security issues introduced as a result of introducing snippet / group repos - None!
Overall WIP: gitlab-org/gitlab!24376 (closed)
CC @m_gill
Retrospection
Good
- Identified that legacy
Gitlab::Shell
code was a blocker- This would impact geo and other repository-adjacent concerns downstream with projectless repos
- Legacy storage is affected much more so than hashed storage
- Untangled much of this:
- Suggested prioritising the removal of legacy storage to untangle the rest
- Made significant progress on decoupling Blob and Repository
- Started to socialise context on developing without relying on blob-commit-repository-project-container coupling
Bad
- Introduced a regression while disentangling gitlab-shell code: gitlab-org/gitlab!27798 (merged)
- Made no progress on Commit at all
- Despite this being an OKR, I felt deliverables and other work took priority much of the time
- Only really made progress where I found myself under-scheduled for one reason or another (unexpected holiday cancellation, assigned issues much lower weight than expected)
Try
- A more systematic approach to socialising information about these being decoupled
- Advocating for some time to be explicitly scheduled for this work
- Continuing it as a Q2 OKR
Edited by Nick Thomas