Skip to content

Automatic rebase of Pull requests

Pull most recent code from master branch and put your work on top within your pull request.

How to use it? Make a comment


to trigger the action

Merge request pipelines

On each merge reqest we are running:

  • shell script analysis
  • creating Docker image
  • creating desktop variants
  • if label is set to “desktop”
  • when PR is switched between “draft” and “ready for review”
  • when PR is approved
  • building changed kernels

Those runs are for security reasons executed on public Github runners servers which are very limited. One build cycle takes around one hour and it produces two types of artefacts:

  • script anylysis report
  • debian packages for kernel, device treee, headers, sources

Those build artefacts are available up to 14 days.


Build beta kernel packages

Pipeline is extended version of merge requests pipeline. Pipeline is scheduled to run every day at 6am CET. It builds all changed kernels and update package repository in case it succeeds.

What is affected by this pipeline?

  • edge branch in stable repository
  • all branches in beta repository

Trigger: every day at 6am CET
Condition: change in packages, upstream sources, patches or configuration

Build all beta images

  • triggered manually or uppon completion of nightly / edge builds;
  • running the job manual is possible,
  • pipeline is always using packages from repository.

Build selected stable images

If you have a commit rights to the repository, go to Armbian build system actions and select Build selected:

Updating selected stable images

You can recreate image(s) at main download location from sources - set packages from repository to no - or from packages that are already in repository (default). In case you choose to build from sources, stable repository is going to be populated with newly created u-boot, kernel and BSP packages for all boards under (patched) stable version ( which is incremented automatically if process succeeds.

kanban screenshot

When new artifacts are created for stable builds, content is uploaded to CDN, then download and repository indexes are updated. The process is typically complete in 1 to 2 days for major releases.

Back to top