Integrate gitlab-ci/lpag/custom_conf and 7 more
Commit: edgehog/infrastructure/gitlab-ci@400ff327
[NOTIFY] Increase timeout for notify job
- The notify job needs to pull the artifacts from all previous jobs and as the number of boards increase the timeout needs to increase accordingly.
--
Commit: edgehog/infrastructure/gitlab-ci@34e9c6dd
[SHA] Insert SHA of the manifest in artifacts name
- Instead of inserting the "weekly" string in the artifacts name, which is already defined in the Azure path, we insert the short SHA for not tagged version of Edgehog.
- Remove TAG_NAME variable from "latest" tagged artifacts
--
Commit: edgehog/infrastructure/gitlab-ci@b8dd7a1d
[KERNEL] Get main kernel version from bitbake
- Instead of setting the kernel version by variable, the kernel main version is derived from the PREFERRED_VERSION of virtual/kernel used by Yocto using bitbake commands.
- The following algorithm does not actually apply on the 'c31' and 'tanaro' boards, for which a different handling is applied.
--
Commit: edgehog/infrastructure/gitlab-ci@9314c567
[ARTIFACTS][NAME] Handle equal variables
- Since for Intel boards the PROCESSOR and BOARD variable values coincides, it is necessary to handle this case and remove one of the two variables from the artifact name.
--
Commit: edgehog/infrastructure/gitlab-ci@74498c1c
[INTEL] Add "intel" generic machine handling
- From now on, the compiled image for all Intel CPU-based SECO boards will be unique and not separate for different processor generations/flavours.
- Bump of the kernel version for all Intel architectures to rel. 6.1.
- Set KERNEL variable separately for each board and avoid the override of the value set in the generic yocto variables.
--
Commit: edgehog/infrastructure/gitlab-ci@88420cc8
[C72NL] Insert c72 Nano Lite configuration
--
Commit: edgehog/infrastructure/gitlab-ci@21286ffc
[ARTIFACTS PATH] Fix on Azure path for imx8 boards
- Insert 'imx8' string in the path instead of the specific processor type.
--
Commit: edgehog/infrastructure/gitlab-ci@b6968f78
[CONF] Add handling of custom lines in local.conf
- Since custom projects may require to insert some flags in the 'conf/local.conf' file (e.g. software products commercial licences) we define the handling of the CUSTOM_CONF variable to contain the lines that need to be inserted in the file.
- Update documentation accordingly.