Continuous integration
Note
TL;DR - Amarula Solutions’ CI/CD documentation covering Jenkins, Gerrit, Docker, SonarQube, Artifactory — with guides on pipeline design, project organization, build throttling, shared libraries, Android application pipelines, and AOSP builds. - All pipelines leverage Amarula Solutions’ custom Groovy shared libraries for consistent build verification, changelog generation, code analysis, and deployment across projects.
Contents:
- Jenkins
- How do Jenkins pipelines orchestrate CI/CD?
- How is Jenkins organized at Amarula?
- How do you create a new pipeline job?
- How do you write and manage pipeline script code?
- How do you trigger Jenkins jobs?
- How do you access pipeline outputs?
- What are the best practices for Jenkins pipelines?
- Gerrit trigger
- How do you manage credentials in Jenkins?
- Jenkins Shared library
- Global environment variables
- Using Docker in pipeline jobs
- Plugins
- How do you test pipelines?
- How are jobs executed on nodes?
- Android application
- AOSP Android build project
- Build Dependency Cache for Docker Jobs
- Configure editor using GDSL
- Gerrit trigger
- Gerrit trigger for repo projects
- Global variables
- Import credential certificate
- Jenkins pipeline autocompletion in Intellij Idea IDE
- Jenkins projects organization
- Jenkins script console
- Jenkins slave
- Pipeline script snippets
- Shared libraries
- Sonarqube
- Throttling of builds
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. Contact our CI/CD team