Integrate gitlab-ci/lpag/new_board_config and 5 more

--

Commit: https://git.seco.com/edgehog/infrastructure/gitlab-ci/-/commit/205766c5c65468d3853ed729e972efec07369a25

[TEST] Include integration jobs for ci-test repos

Up to now, the ci-test group repositories were used for sporadic
tests but in the optic of a continuous CI/CD improvement they need
to be treated as 'production' repositories. With this approach,
every time a MR is created in the gitlab-ci repo, the modifications
introduced can be tested in the ci-test group repositories.

--

Commit: https://git.seco.com/edgehog/infrastructure/gitlab-ci/-/commit/bd49e5701d3e36c983e44f825dd3f84ddb9b062d

[BSP][RETRIGGER] Retrigger pipelines for BSP MRs

Every time a BSP related MR is merged, the SRCREV.conf file in the
corresponding meta-layer is updated and all other integration MRs in
that meta-layer can no longer be merged due to conflicts. For this
reason we add this steps every time a BSP related MR is merged:
* Search for all open MRs in the same BSP group of the project on which
the MR occurred.
* Retrigger the pipelines for all these MRs, that in turn updates the
integration branches in the meta-layer.
* All the integration MRs in the meta-layer are now mergeable so that if
two or more MRs are merged (tipically U-Boot and Kernel MRs are merged
almost at the same time) no conflict are expected to occur.
* Moreover, this procedure allows to have an integration MR in the
meta-layer always updated with the latest BSP version in the main
branch.

To make this work we also need to change the retrigger job, avoiding the
possibility to run 'check' jobs that are already running and that would
throw an error.

--

Commit: https://git.seco.com/edgehog/infrastructure/gitlab-ci/-/commit/8d1f688a32f3968a499c502cd9cc02f9e03f2d82

[CUSTOM] Add custom projects to gitlab-ci deploy

--

Commit: https://git.seco.com/edgehog/infrastructure/gitlab-ci/-/commit/647559c470f3f320f0885fa7732dc10cb1c3d1f6

[MR][CLEANUP] Insert script to perform MR cleanup

* This script is necessary for all the open MRs that were created by the
GitBot when performing meta-layers/manifest integration. Indeed, in case the source
MR is closed, the integration one created by the Gitbot remains opened
and shall be closed by hand. The script actually searches for this type
of MRs, close them and delete the source branch.
* This type of job is intended to be executed on a weekly schedule in
order to clean week by week the MR in the Edgehog group.

--

Commit: https://git.seco.com/edgehog/infrastructure/gitlab-ci/-/commit/492a3d3e0698c19f2f7cd5da6b84f163646b17fa

[CACHE][TAG] Use downloads and sstate-cache on tag

* In a first implementation of the build logic, the downloads and
sstate-cache were supposed to be used only on sheduled and MR builds.
However, as the number of supported boards increase, there is more necessity of
CPU and time to get all Yocto images built when a tag is performed. For
this reason we decide to remove the differentiation at least as long as
the build server is not upgraded.
* Increase the tiemout of the notify job. this is necessary because it
actually downloads the artifacts from build jobs.

--

Commit: https://git.seco.com/edgehog/infrastructure/gitlab-ci/-/commit/7f08d6e67677677824bb0e03307cb10547db840b

[CUSTOM] Add custom project to gitlab-ci deploy

.gitlab-ci @ 205766c5

-Subproject commit 9f7814ed3391117944a73568cfa32a9b574863be
+Subproject commit 205766c5c65468d3853ed729e972efec07369a25

.gitlab-ci.yml

@@ -4,11 +4,11 @@
 # ---------------------------------------------------------------------------------------
 include:
   - project: 'edgehog/infrastructure/gitlab-ci'
-    ref: 9f7814ed3391117944a73568cfa32a9b574863be
+    ref: 205766c5c65468d3853ed729e972efec07369a25
     file: 'layers-integration.yml'
 
 variables:
-  GITLAB_CI_REVISION: 9f7814ed3391117944a73568cfa32a9b574863be
+  GITLAB_CI_REVISION: 205766c5c65468d3853ed729e972efec07369a25
   # FIXME: This is only necessary due to the following GitLab limitation:
   # https://gitlab.com/gitlab-org/gitlab/-/issues/209904
   # As soon as this gets fixed upstream, the hard-coded branch name should be removed.