Mender provides support for application updates in the form of CI/CD pipelines to implement all kinds of specific use-cases. This section describes possible ways to integrate your workflow with Mender and most popular CI/CD providers.
To help you in creating CI/CD pipelines, we created GitHub repository containing ready to use, battle-tested CI/CD pipeline code snippets that can be used in your workflows. Additionally, we provide mender-ci-tools Docker image based on Alpine Linux and providing command-line utilities,mender-artifact and mender-cli installed.
To locally inspect the Docker image, pull it with the following command:
docker pull mendersoftware/mender-ci-tools:1.0.0The Docker image definition and CI/CD templates can be found here.
Mender currently supports three major CI/CD providers:
This scenario uses mender-artifact tool to package your software as a Mender Artifact. A Mender Artifact can optionally be signed, so the examples provided allow for signing the Artifact too.
The input for the scenario is the software being packaged and the output is a Mender Artifact.
You can read about artifact creation details here.
More details about signing Mender Artifacts here.
This scenario uses mender-cli tool to upload your Mender Artifact to the Mender server.
The input for the scenario is the Mender Artifact generated in the previous stage, and the output is upload result.
You can read about uploading the Mender Artifact to the file storage here.
You can use Personal Access Tokens with necessary permissions to perform automated actions on Mender server on your behalf.
This scenario uses the Mender server API to trigger a deployment on your fleet.
The inputs for this scenario are the device group to deploy on and previously uploaded Mender Artifact, and the output is the deployment result.
© 2023 Northern.tech AS