Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 7 Current »

Topics

Please enter your proposed topics for discussion here.
In Lean Coffee Style (link1, link2), we will vote on which topics the group wants to discuss and time-box the discussion to 10 or 15mns → 5mns (if re-voted) → 5mns (if re-voted).

  • Tech Radar - further assessment discussions from Tuesday’s Arch Study Group: Tech Radar

  • Health/monitoring of CI / CD pipelines - impact on squads? +++

    • https://openedx.atlassian.net/wiki/spaces/ENG/pages/1789526017/Operating%2BReviews

    • edx-platform

      • CI to master: ~40mns

      • merge → stage → e2e → prod: ~90mns

        • blocked on previous deploy

    • monitoring CD

      • splunk - though could be unreliable

    • impact on squads

      • e-commerce: CI is long here as well (~40mns), CD is much better though; manual CD after ensuring e2e tests pass

      • ORA: not a pain-point right now

      • edx-platform: couldn’t give a good estimate to stakeholders since uncertainty with rollbacks/etc

      • Actual impact on a team: no code merges after 3pm on weekdays, no code merges after 12pm on Fridays

      • Note:

        • Since CI/CD is about 2-hours, can’t fix-forward reasonably. We need to rollback and rollback all other concurrent changes.

        • Separate paths and testing considerations for infrastructure-level changes versus feature changes

          • feature changes: can use toggles to decouple release from enablement/monitoring in prod

          • infrastructure changes: can use canary releases for controlled testing - separated from the normal pipeline flow to keep pipeline flow

  • Django Signals + best practices! +

  • ChangeLogs - what are they? ++

Backlog of Questions/Discussions

This section lists a backlog of previous proposed topics that haven’t yet been discussed.

  • No labels