CI/CD & Test Automation

Note

TL;DR - Hub for Jenkins CI/CD infrastructure at Amarula Solutions — covering pipeline design for embedded projects (Yocto, Android, firmware), Gerrit-triggered verification, static analysis (CodeChecker), memory checking (Valgrind), hardware-in-the-loop testing (Labgrid), and shared Groovy libraries for pipeline standardization.

Jenkins Pipeline Documentation

Our CI/CD documentation covers the full pipeline lifecycle:

  • Jenkins overview — architecture, folder organization, pipeline creation, job triggering, credentials. See ci/jenkins.

  • Gerrit trigger — automated verification on patchset creation, Verified label management. See ci/gerrit_trigger.

  • Gerrit trigger for repo projects — multi-repository dependency handling (AOSP-style). See ci/gerrit_repo_trigger.

Embedded Build Pipelines

Production pipeline patterns for specific build systems:

Code Quality & Security Scanning

Shared Libraries

Amarula Solutions’ reusable Groovy pipeline components:

  • ci_scripts — Build, Verification, AndroidBuild, Ui, Archiva, Sftp classes.

  • repo_jenkins_lib — Git, Gerrit, GerritChange, Repo for multi-repo projects.

  • codechecker_jenkins_lib — CodeChecker static analysis wrapper.

  • changelog_lib — Automated changelog generation.

See ci/sharedlibs/index for complete documentation.

Android CI/CD

Tip

Need a CI/CD pipeline for your embedded software team? Amarula Solutions designs and maintains Jenkins-based automation for Yocto, Android, firmware, and application builds with Gerrit integration and hardware-in-the-loop testing. Contact our CI/CD team