馃敋 馃惓 Docker MR Final: Resolve "Build and test backend and web_frontend docker images"
What is in this MR
- Docker images are built automatically and used for testing
- They are pushed to the gitlab repository both to pass them around between CI jobs, but also pushed to the
baserow/testing
repo as a placeholder for Dockerhub.
Manual steps needed after merging
- After merging enable the morning rebuild job on develop https://gitlab.com/bramw/baserow/-/pipeline_schedules/205596/edit
Merge Request Checklist
-
changelog.md has been updated if required -
Documentation has been updated -
Quality Standards are met -
The UI/UX has been updated following UI Style Guide -
The redoc API pages have been updated for any REST API changes -
The per database user API docs page has been updated for any REST API changes made to endpoints which can be accessed via a user created token -
Has performance been considered and tested when appropriate? Ideally Baserow should be performant when working with hundreds of thousands of rows -
New/Changed Premium features are separated correctly in the premium folder -
There are tests for and it has been checked that any changed/new django ORM code is sensible, doesn't perform N queries and that table models are not generated needlessly or generated with all columns when only a few are needed.
Closes #736 (closed)
Edited by Nigel Gott