concrete
concrete copied to clipboard
ci: add remote configuration for slab ci bot
Description
In the next Slab CI bot release, the inner workings of the server change a bit. In order to have more flexibility on command declaration and EC2 profile definitions for each repositories, the configuration belongs now to each repo.
Each time a command is run from a PR, the file ci/slab.toml
will be fetched and read from the branch the PR refers to. A great aspect of this behavior is the ability to add a new command/profile in your PR to test your code in other conditions. Another one is to avoid having hardcoded profiles structs and commands in Slab, and thus remove the need to make a release or reboot Slab in case of global configuration changes.
Checklist
- [ ] ~~Tests for the changes have been added (for bug fixes / features)~~
- [ ] ~~Docs have been added / updated (for bug fixes / features)~~
- [ ] ~~The PR description links to the related issue (to link an issue, use '#XXX'.)~~
- [ ] ~~The draft release description has been updated~~
- [x] Check for breaking changes (including serialization changes) and add them to commit message following the conventional commit specification
We are likely to change the aws instances used to get shorter test execution time
Ok let's wait then for your choice.