Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ENT-8277] - feat: record Blackboard client calls #2004

Merged
merged 3 commits into from
Jan 31, 2024

Conversation

hamzawaleed01
Copy link
Member

@hamzawaleed01 hamzawaleed01 commented Jan 29, 2024

Merge checklist:

  • Any new requirements are in the right place (do not manually modify the requirements/*.txt files)
    • base.in if needed in production but edx-platform doesn't install it
    • test-master.in if edx-platform pins it, with a matching version
    • make upgrade && make requirements have been run to regenerate requirements
  • make static has been run to update webpack bundling if any static content was updated
  • ./manage.py makemigrations has been run
    • Checkout the Database Migration Confluence page for helpful tips on creating migrations.
    • Note: This must be run if you modified any models.
      • It may or may not make a migration depending on exactly what you modified, but it should still be run.
    • This should be run from either a venv with all the lms/edx-enterprise requirements installed or if you checked out edx-enterprise into the src directory used by lms, you can run this command through an lms shell.
      • It would be ./manage.py lms makemigrations in the shell.
  • Version bumped
  • Changelog record added
  • Translations updated (see docs/internationalization.rst but also this isn't blocking for merge atm)

Post merge:

  • Tag pushed and a new version released
    • Note: Assets will be added automatically. You just need to provide a tag (should match your version number) and title and description.
  • After versioned build finishes in GitHub Actions, verify version has been pushed to PyPI
    • Each step in the release build has a condition flag that checks if the rest of the steps are done and if so will deploy to PyPi.
      (so basically once your build finishes, after maybe a minute you should see the new version in PyPi automatically (on refresh))
  • PR created in edx-platform to upgrade dependencies (including edx-enterprise)
    • This must be done after the version is visible in PyPi as make upgrade in edx-platform will look for the latest version in PyPi.
    • Note: the edx-enterprise constraint in edx-platform must also be bumped to the latest version in PyPi.

@hamzawaleed01 hamzawaleed01 changed the base branch from master to hamza/ENT-8276-record-corner-stone-api-calls January 29, 2024 09:33
@hamzawaleed01 hamzawaleed01 force-pushed the hamza/ENT-8277-record-blackboard-client-calls branch from afc7ce8 to ddc58d9 Compare January 29, 2024 09:34
@hamzawaleed01 hamzawaleed01 force-pushed the hamza/ENT-8276-record-corner-stone-api-calls branch 2 times, most recently from 4af246d to d5bd99d Compare January 30, 2024 09:47
Base automatically changed from hamza/ENT-8276-record-corner-stone-api-calls to master January 31, 2024 10:20
@hamzawaleed01 hamzawaleed01 force-pushed the hamza/ENT-8277-record-blackboard-client-calls branch 6 times, most recently from 637d7db to 7c9ad74 Compare January 31, 2024 12:12
@hamzawaleed01 hamzawaleed01 force-pushed the hamza/ENT-8277-record-blackboard-client-calls branch from 7c9ad74 to 7446e03 Compare January 31, 2024 12:24
@hamzawaleed01 hamzawaleed01 merged commit 8c10f51 into master Jan 31, 2024
9 checks passed
@hamzawaleed01 hamzawaleed01 deleted the hamza/ENT-8277-record-blackboard-client-calls branch January 31, 2024 12:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants