The staging environment is the test bed before something gets released to production. It contains data and due to trunk based development we can assume it has all the code from production as well as anything new that has been added to dev since the last production deployment.
Deployments to staging are automated using a GitHub Action. In short, the workflow sends a request to the deploy hooks for the jadmin, next-app and strapi projects.
Please navigate to the vendors directly:
The code that every user sees, the aim is to have no production bugs and a smooth user experience.
The following tests should be performed before any production release:
Before any deployment, post a message in #devs to notify other members that
a deployment is happening, this is to make everyone aware incase something goes wrong.
workflow_dispatch GitHub ActionRun workflow, ensuring the branch is selected as devtag e.g. if the current tag is beta-1.0.0 and this is a patch then the new version should be beta-1.0.1.Run workflow button and voila!Once successfully deployed, please perform a smoke test on production:
Only post the release notes once he deployment has finished.
Generate release notes to see a list of the commits that have been added**New** ✨
* Created a new and exciting feature that is going to transform JustAbout
**Improvements & Optimisations** ⚡️
* Fixed the issue where the wrong replies were loaded for the wrong thread
* Speed up the pages with a new server loading pattern
**Behind the Scenes** 🧩
* Introduce speed insights to understand what areas of the platform are performing
* Foundational work for the next version of JAutoMod
Full Changelog: [https://github.com/Just-about/just-about/compare/beta-1.1.4...beta-1.2.0](https://github.com/Just-about/just-about/compare/beta-1.1.4...beta-1.2.0)
For all completed tickets do the following:
🔖 Bath Tokens project🔜 Backstage project📭 In Production