Hi all,
We’re going to trial a new approach for platform contributions that require both TF-A and CI changes.
This is intended to address synchronisation issues that can arise when TF-A and corresponding CI patches are merged at the same time. In some cases, the CI configuration can take effect before other in-flight patches have had an opportunity to rebase onto the associated TF-A change, causing unrelated patches to fail CI.
For the time being, we’re asking contributors to:
* Submit the Coverity configuration and build configuration as separate CI patches. * Test both CI patches together with the corresponding TF-A change. * Submit the Coverity configuration alongside the TF-A change, but hold back the build configuration for one week. * After the one-week period, the maintainer should return to the CI change and submit the build configuration.
The one-week delay is intended to give the TF-A change time to propagate through other in-flight patches before the new build configuration becomes active.
We’ll trial this approach for now and review how well it works in practice.
Thanks, Harrison