I have previously constructed a Yocto Image for Rpi3 device manually and are now seeking to automate the Yocto Image building process using Azure DevOps pipelines.
The manual Yocto build process consists of the following steps:
- Cloning specific layers with a particular commit ID.
- Creating the source environment and making necessary configuration file modifications.
- Executing the 'bitbake' command to initiate the Yocto Image build.
- Downloading the successfully built Yocto Image from the "/tmp/deploy/images" directory.
I have little knowledge of where GitLab is used for maintaining the Yocto-related files, Jenkins is for building the image, Kubernetes will be as a backend to build the image into a runtime pod. and Nexus is to save the built Yocto Image.
Now, I have several questions that require clarification for setting up this automation process within the Azure DevOps pipeline.
Questions:
- Which Azure services are required to automate the process of building Yocto Image from cloning the layers to downloading the image?
- In order to automate the pipeline, including tasks such as starting from cloning specific layers, building Yocto Image, and saving the final Yocto image in Nexus kind of thing as an example, what kind of configuration file or script should be created, where should it be stored, and should it be maintained within the Git repository or elsewhere?
- To copy some Yocto-related files from Git to Kubernetes Service, how it can be done?
- Once the image is built successfully where we can save the image so that we can go and download the image?
- It will be great if you provide an end-to-end flow architecture diagram as well.
Thanks in Advance!