# RIOT CI meeting 10/22

## Details

When: 05.10.22 10h Berlin time
Where: https://meet.jit.si/RealFlowersLaughFlatly

Previous meeting notes: https://hackmd.io/I4G2FKZ8RmSlRI37VlYl2g

## Participants

- Tom
- Alex
- Kaspar

## Agenda

- Murdock Migration
- Murdock speedup

## Notes

### Murdock Migration

- status:
copied from https://hackmd.io/GOvgvGGeTkCpP7hwiGFImg:
- preparation:
- [x] ...
- [ ] prepare alternate murdock-worker "ssh" folder & .env settings pointing to "ci-prod.riot-os.org" @kaspar030
=> better: prepare second checkout of "RIOT-OS/murdock-worker" (cheap, easy rollback)
- [ ] get GO from community

- on migration day:
- [ ] let everyone know that we'll be switching over.
- [ ] stop all builds
- [ ] switch workers to prepared ssh&env settings
- [ ] drop "required status" of old murdock

- [ ] switch dns to tatooine
- [ ] do some test builds
- [ ] done

- fallback:
- switch back dns
- roll back worker config

- after migration:
- [ ] remove old webhook

- next steps:
- write up migration steps in some pad (@kaspar030) => [migration steps](https://hackmd.io/rP3h5_F7Rdq9AjhF20ufBQ)
- start new instance on each worker (with one job?)
- at some point when all are working, stop old instance, scale up new

- merge badge PR => https://github.com/RIOT-OS/RIOT/pull/18685

### Speeding up

- Limiting builds
- More hardware
- Speeding up RIOT
- Failed jobs
- After the migration we can test to see if any jobs actually fail
- fast-fail (by default)
- Also after the migration
- lossy builds:
- already doing with kconfig
- option: tier builds
- option: 1 app all boards, all apps one board
- bors only if the lossy build can catch +99? %

#### Two metrics for CI
- How long for murdock to complete a single run
- How long for something to get merged in master