Skip to content

[CICD] Insert Deploy to Azure and Test stages

Lorenzo Pagliai requested to merge seco/lf-5.10.y/develop-ci into seco/lf-5.10.y/develop
  • The pipeline can either be triggered on nightly schedule or from upstream pipeline (u-boot-seco-imx).
  • Insert separate build jobs for different type of boards (currently supported: a62, b08, c23, 928, c20, c26).
  • The built boot/ and lib/ kernel folders are used to create a tar.gz package that is uploaded to the Azure cloud storage (secosoftware-devops container) by tagging them with the date of the build.
  • The URL of the deployed package is passed as a parameter to the submit_test.py python script that is used to trigger the LAVA job.
  • The user can access the URL of the LAVA job from the log of the corresponding test job in GitLab.

Merge request reports