You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have a fairly complicated build process in qcom-deb-images, as
evidenced by the current README.md. Giving developers a one-command
build instead means:
1. Simplified instructions for developers, or in other words, moving
instructions for manual entry from README.md into automated invocation
via the build system.
2. Automated dependency/rebuild tracking, reducing the instances where a
full rebuild is required, or the easiest option, during development
iteration.
3. Building only what is necessary for a given target.
4. The opportunity to move towards running CI before submission in a PR,
rather than CI being entirely defined inside .github/workflows/ and
therefore inaccessible for running locally.
This is too complex to attempt all at once. Instead I'm doing it in
multiple small steps, and this is the first step. Overall, my plan is:
1. Introduce a basic Makefile that works.
2. Per item, implement in the Makefile what CI requires that is already
implemented in .github/workflows/.
3. Per item, replace complex build invocation steps made directly from
.github/workflows/ with calls to the Makefile instead.
4. Once the elements covered by README.md are all covered, I'll update
the instructions to use the Makefile instead.
Note that CI for the Makefile should therefore not be necessary to
implement directly; it'll happen step by step as CI is moved into it
through step 3 above. If there are gaps in CI coverage that the Makefile
does cover, then we can implement those as separate CI items to call
from .github/workflows/ as we wish.
In time, this should make .github/workflows/ simpler, and encode our
knowledge of how to invoke the various tools (including debos) into the
source tree itself, rather than via manual instructions in README.md
that are also duplicated in .github/workflows/
Signed-off-by: Robie Basak <[email protected]>
0 commit comments