Repository navigation
CI: Push on more branches can trigger CI check #382
Description
The following branches are tracked and every push triggers a CI check.
SOF/linux github: topic/sof-dev, topic/sof-dev-rebase, topic/sof-rcX-rebase, topic/sof-next-rebase
Plbossart github: all branches
"I am clearly not asking this for every PR since there are usually multiple updates from developers, but it makes sense once the PR is approved and merged/rebased on topic/sof-dev.
Likewise for all the -rebase branches it’ll ensure there was no issue with the squash/rebase operation." - by Pierre.
Activity
[-]CI: Push on multiple branches can trigger CI check[/-][+]CI: Push on more branches can trigger CI check[/+]plbossart commentedon Mar 24, 2019
@xiulipan can you provide the list of branches that are tracked by CI?
xiulipan commentedon Mar 25, 2019
@plbossart
Now only topic/sof-dev is supported.
We are working on multiple branch support now and we are extend our storage server memory space.
lgirdwood commentedon Mar 25, 2019
@xiulipan CI should not be cloning and building a clean kernel for every PR. Our CI should be using a pre-cloned and pre-built (using a golden config) so that every git update and build is incremental.
xiulipan commentedon Mar 26, 2019
@lgirdwood
For our own Jenkins CI. PR and Daily is done this way.
But for Travis, their test logic is to start an empty ENV every time. And we could not do anything on it.
mengdonglin commentedon Mar 13, 2020
No longer track CI requirements or bugs in this repo
ARM: 9063/1: mm: reduce maximum number of CPUs if DEBUG_KMAP_LOCAL is…
Merge branch 'arm32-bpf-add-support-for-cpuv4-insns'
drm/xe: Fix xe_device_probe() failure
drm/xe: Fix xe_device_probe() failure