Tim suggested to use the same name scheme for all jobs and use the group
names yocto and gitlab-ci as base.

Initially the moved code was needed to create the files including the
new implementation.

Also set yocto deploy job to manual to test merge.

For projects like the kernel the git checkout needs a log of time and
space. Directly using the gitlab api only loads the infomation needed.

Integrates the changes done in the foobar- yml files to the yocto
projects.

This change should be reverted after once used.
It is needed to initially add the include .gitlab-ci.yml in
all subprojects.

As all projects are commited in the same branch the 'up-to-date' check
may not only check if the first parent commit points to the
master/dunfell branch. Now it is needed to loop through the history
until the integration branch's commit is found.

On fail a message is displayed which merge request needs to be
retriggered manually. This can now also be the 'parent'-MR that
triggered the complete chain.

The check job is used pipeline again.

The retrigger job also looks in the .gitlab-ci project for check jobs to
retrigger.

BCS 746-000646

Before only the ID was used but the CI_OPEN_MERGE_REQUESTS variable has
the complete path.

Allow deploy_gitlab_ci to change multiple projects at once.
Use it to create integration branches and merge requests in all
projects.

Add a python file to generate a job yml from jinja2 template.
Add a template for the jobs to trigger. These execute the actual
integration in all 'subprojects'.
Create the yml file in the deploy job and trigger it in a new trigger
job.

Create a merged version of the gitlab-ci files from the layers and the
repositoried referenced by the SRCREV file to be included in the
projects, to replace the project-individual implementation.

BCS 746-000646

Add update gitlab-ci file with function to adapt the include ref to a
given revision.
Add a 'pre-commit-hook' to the update-submodule function.
Adapt deploy_gitlab_ci to use these to update the include statement in
the base project .gitlab-ci.yml to use the same ref as the submodule
is set to.

BCS 746-000646

To have one repo for all the CI implementation move also the manifests
yml file here.

BCS 746-000646

This allows to increase the verbosity. Add --verbose in .gitlab-ci.yml
when the python script is called to view the output in the jobs log.

Also add all yml files to the yamllint check and replaces the project
path check with a more general project-root check.

BCS 746-000646

I did a test setup in the azure cloud. These are the notes how this was
done.

BCS 746-000594

The markdown2 Python module was added to the package_release.py script,
which resulted in a failed SDK deployment because it was missing from
the build container. Updated ci-images to the latest revision, in which
the module was added to the build container.
Modified package_release.py to skip the metadata generation when
deploying the SDK.

BCS 746-000727

BCS 746-000016

BCS 746-000716

BCS 746-000715