mirror of
https://github.com/odoo/runbot.git
synced 2025-03-17 16:35:47 +07:00
24d35988a4
One of the most common custom trigger is to restore a build before starting some test, either to create a multibuild or make the execution and debug of some test faster. It is somethimes tedious to use because we need to give an url of a build to restore. This build must correspond to the right commits, must still exixt, ... this means that the dump url must be adapted everytime a branch is rebased. The way the dump_url is defined is by going on the last batch, following the link to the `base_reference_batch_id`, finding a slot corresponding to the right repo set, (ex: Custom enterprise -> enterprise), and copying the dump_url in this build. The base_reference_batch_id is eay to automated but we have to find the right trigger, this is now a parameter of the custom trigger wizard. There are actually 2 strategy now to define how to download the dump: - `url`, using `restore_ dump_url` - `auto`, using `restore_trigger_id` and `restore_database_suffix` To ease the setup, a `restore_trigger_id` is added on a trigger, so that when selecting a trigger, lets say `Custom enterprise`, the defined `trigger.restore_trigger_id` is automatically chosen for the `custom_trigger.restore_trigger_id` and the `restore_mode` is setted to auto. Two actions are also added to the header of a bundle, a shorcut to setup a multi build (restore in children) or a restore and test build (restore in parent). |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| common.py | ||
| test_branch.py | ||
| test_build_config_step.py | ||
| test_build_error.py | ||
| test_build_stat.py | ||
| test_build.py | ||
| test_command.py | ||
| test_commit.py | ||
| test_cron.py | ||
| test_dockerfile.py | ||
| test_event.py | ||
| test_host.py | ||
| test_repo.py | ||
| test_runbot.py | ||
| test_schedule.py | ||
| test_upgrade.py | ||
| test_version.py | ||