Distribution 3.21 Tracking issue
Created by: pecigonzalo
Plan
Support new and existing deployments
This is an ongoing expense, we anticipate this taking no more than 10d of work spread across the entire team.
Support Security in deploying a log analysis tool
Security is planning to deploy a centralized logging and analysis system and will require our assistance to setup and review this new infrastructure.
Implement 2+ sourcegraph.com services using dhall
sourcegraph.com sees the highest amount of Kubernetes changes out of all of our deployments + deploy-sourcegraph. Scoping a single component limits the customizations that we need to implement and allows for easier onboarding other engineers.
- @ggilmore
- @uwedeportivo
- @slimsag
Releases are created in a single day
We have a goal of reducing the time it takes to create releases, and this current several-day system has encouraged us to view releases as “baked” rather than “snapshots of the main branch”, leading to situations where main is broken and we have to retrospectively fix it or adding last minute features.
- @slimsag
- @davejrt
- @uwedeportivo
- @bobheadxi
Split infrastructure into separate GCP projects
GCP utilizes project wide roles and permissions, to ensure resources are isolated from each other and reduce the blast radius of changes, we should split resources into separate projects. Additionally, this will grant us more insight into our infrastructure costs and will become more important as we grow and expand it.
- @pecigonzalo
Availability
Period is from September 20th to October 19th (21 working days). Please write the days you won't be working and the number of working days for the period.
- Gonza: 19d (23rd Sept and TBD)
Tracked issues
@unassigned: 5.00d
Completed: 5.00d
-
( 🏁 14 days ago) run "e2e regression tests" in CI once/day, even if they fail all the time (#13876) 5.00d
@bobheadxi: 8.50d
-
on-call: document actions to follow up on critical alerts(#1468)
Completed: 8.50d
-
( 🏁 36 days ago) renovate-downstream: refine action trigger (#13842) -
( 🏁 23 days ago) release steps: stop posting milestone triage messages (#13871) 2.00d -
( 🏁 22 days ago) dogfood-k8s: finalize migration over to new cluster (#13792) 1.00d -
( 🏁 17 days ago) release steps: automate CHANGELOG version header creation (#13873) 2.00d -
( 🏁 17 days ago) release steps: do not verify CHANGELOG entries (#13872) 0.50d -
( 🏁 16 days ago) release steps: roll deploy-sourcegraph PR creation intoyarn run release release:publish(#14242) 1.00d -
( 🏁 16 days ago) managed-instances: deploy a demo instance (#13604) 1.00d -
( 🏁 15 days ago) release steps: stop announcing release candidates (#13875) 0.50d -
( 🏁 10 days ago) release steps: stop posting messages about branch cut in Slack (#13869) 0.50d -
( 🏁 7 days ago) release: command naming and behaviour is inconsistent (#14623)
-
Run QA tests on bare-metal Buildkite agents on every commit to master (non-blocking)(#12340) -
blackbox exporter & site 24/7 next steps(#13627) 🧶 -
sourcegraph/customer(#111)👩
Completed
-
( 🏁 119 days ago) Bigdata customer Tracking issue (#11717) -
( 🏁 24 days ago) Run e2e tests on bare-metal Buildkite agents on every commit to master (non-blocking) (#12339)
@daxmc99: 4.00d
-
explore making it easier to run Kubernetes cluster QA tests (or relax to just smoke tests)(#13878) 4.00d
@efritz
-
docs: Update pure-docker upgrading docs (#14671) :shipit:
@ggilmore
-
ci: build and pin tool apks in CI for release (#13297) 🧶 -
write instructions for how to modify sourcegraph.com's dhall generation pipleine (#14136) -
write developer friendly documentation for deploy-sourcegraph-dhall architecture (#14135) -
add "symbols" to service deploy-sourcegraph-dhall, with support for sourcegraph.com customizations (#14130) -
dhall: use dhall on sourcegraph.com(#13340)
Completed
-
( 🏁 13 days ago) sourcegraph/customer (#110)👩
@pecigonzalo: 23.00d
Completed: 23.00d
-
( 🏁 28 days ago) Move the CI e2e runner to the CI project (#13919) 1.00d -
( 🏁 24 days ago) Move the CI cluster to the CI project (#13920) 3.00d -
( 🏁 23 days ago) Move the single container dogfood deployment to the dogfood k8s cluster (#13916) 2.00d -
( 🏁 23 days ago) Delete the big data clusters (#13918) 5.00d -
( 🏁 22 days ago) dogfood-k8s: finalize migration over to new cluster (#13792) 1.00d -
( 🏁 15 days ago) Remove the-toolingcluster from the production project (#13917; PRs:#1719) 3.00d -
( 🏁 10 days ago) sourcegraph/customer (#105) 8.00d👩
@slimsag: 15.00d
Completed: 14.50d
-
( 🏁 31 days ago)sourcegraph/customer(#104)👩 -
( 🏁 29 days ago) Create a dev/testing managed instance (#14075) -
( 🏁 24 days ago) Run e2e tests on bare-metal Buildkite agents on every commit to master (non-blocking) (#12339) -
( 🏁 16 days ago) Remove syntax highlighting for GraphQL, INI file, TOML, and Perforce (#13933) -
( 🏁 16 days ago) release steps: make Product team self-sufficient (#13868) 0.50d -
( 🏁 8 days ago) License report for syntect_server & its dependencies (#11269) 1.00d👩 -
( 🏁 7 days ago)Document when to introduce new services or not(#5487) :shipit: -
( 🏁 3 days ago) engineering: document when to (or not to) introduce a new service (#1769) :shipit: -
( 🏁 3 days ago) distribution: add monitoring architecture page (#1221) :shipit: -
( 🏁 3 days ago) Improve reliability of QA tests (#13880) 12.00d -
( 🏁 3 days ago) Document QA test commands (#14632) 1.00d
@uwedeportivo: 9.50d
-
sourcegraph.com: write bot to incorporate image tag updates in dhall pipeline(#14133) 1.50d -
add deploy-sourcegraph-dhall pipeline to deploy-sourcegraph-dot-com (#14132) 1.00d -
add gitserver to deploy-sourcegraph-dhall, with support for sourcegraph.com customizations(#14131) 4.00d -
dhall: generate separate yaml files for each "component" instead of one large one(#13338) 2.00d -
deploy-sourcegraph: restricted integration test fails with Kubernetes 1.16+(#14728) -
dhall: use dhall on sourcegraph.com(#13340)
Completed: 1.00d