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
Dilec Padovani edited this page Aug 6, 2022
·
3 revisions
Source code is added to the sources directory via git submodule add <github url> or updated, then is committed to master
When a push on master is detected a custom GitHub action Build the sources is activated
How does Build the sources work?
It checkout the master branch and it also loads the submodules
Saves the private gpg locates in GitHub secrets in a file and imports it using gpg --import
Each script in the script folder is run (more about it later)
Targets of build are located in temp/<project_name> and each script constructs a dedicated .deb file in temp
.debs are copied to the ubuntu folder alongside the public key and necessary files, then a series of commands generate and sign all apt related files. At last temp is removed
A separate branch is created, rebased with master, and pushed. In this way, the master creates the ubuntu folder but it is then moved to the other branch, to be visible via the GitHub page (set on branch website)
TO-DO !!
At the moment each script takes approximately 90 seconds. Not bad, but if there are many the build time get too long. The goal is to run all scripts in parallel to minimized build time.