MDBF-1109 - Auto update the Debian Sid environment #832
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
RazvanLiviuVarzaru
force-pushed
the
MDBF-1109
branch
from
d4890c9 to
38e8d3b
Compare
grooverdan
approved these changes
Sep 1, 2025
Member
grooverdan
left a comment
grooverdan
left a comment
There was a problem hiding this comment.
very optional comment.
Thanks!
RazvanLiviuVarzaru
force-pushed
the
MDBF-1109
branch
2 times, most recently
from
c47b78f to
d9d5ad6
Compare
Collaborator
|
Very good doc, can you create a link from the README.md file that is in the root of the repo? I will handle the cleaning of this file when I find time. |
[skip ci] Quick recap on how images are deployed to production: 1. On Pull Request : an image is only built 2. On Push to DEV branch: the image is built and pushed to quay / ghcr but with a `dev_` prefix tag. `buildbot.dev.mariadb.org` uses images starting with`dev_` 3. On push to MAIN branch: the `dev_` tag is moved in quay / ghcr replacing the production image that doesn't have `dev_` in its name. `buildbot.mariadb.org` looks for images not having `dev_` in their name. On schedule goal: - on schedule event (which by GitHub laws is triggered on the default branch >>dev<<). We want to build the container image, push it to dev and then deploy it to prod. Framework: The dispatcher is scheduled to run on the third of the month. Child workflows having `is_scheduled_event` input will be triggered. In the child workflow only the images with `deploy_on_schedule: true` are rebuilt. In the workflow template `bbw_build_container_template.yml`: - the job runs if the run is scheduled and the matrix item has 'deploy_on_schedule: true` or for any other event type (pull request, push) If `is_scheduled_event` is True then tags are moved to Production.
RazvanLiviuVarzaru
force-pushed
the
MDBF-1109
branch
from
d9d5ad6 to
07ea14b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Quick recap on how images are deployed to production:
dev_prefix tag.buildbot.dev.mariadb.orguses images starting withdev_dev_tag is moved in quay / ghcr replacing the production image that doesn't havedev_in its name.buildbot.mariadb.orglooks for images not havingdev_in their name.On schedule goal:
Framework:
The dispatcher is scheduled to run on the third of the month. Child workflows having
is_scheduled_eventinput will be triggered.In the child workflow only the images with
deploy_on_schedule: trueare rebuilt.In the workflow template
bbw_build_container_template.yml:deploy_on_schedule: trueor for any other event type (pull request, push)If
is_scheduled_eventis True then tags are moved to Production.