The pipeline is not setup to build from different manifest and so on,
and the dual_espresso manifest will probably go to a seperate repo
to keep it private.

BCS 746-000518

BCS 746-000637

* Split up build and package steps in separate files
* Add additional comments
* Add log output

BCS 746-000637

Rename variable JENKINSGUF_SSH_PRIVATE_KEY / SSH_PRIVATE_KEY to
GITLAB_PRIVATE_KEY on this occasion, because it contains a private key
that was generated exclusively for this use case. The according public
key has been added as a deploy key in GitLab to all repositories that
this repository needs access to.

Add more detailed documentation concerning this configurationdirectly in
the gitlab-ci files.

Tim Jaacks authored 2 years ago and Jonas Höppner committed 2 years ago

BCS DevOps-000035

Our settings refuse to merge if no pipeline has been run.

The deploy_gitlab_ci now creates the integration commit and branch in
each passed subproject and create an integration commit in the manifest
containing all these new revisions.
A build is then triggered on this commit to test the functionality.

Split the update_submodule functions to reuse them in different ways.
Remove some previously used files.

BCS 746-000740

Added additional log output for sdk upload.

Remove alphaplan_fwr debug code and run black and pylint.

To improve the readability of the package_release.py script.

BCS 746-000734

Now md5sums.txt can be assembled from different copy processes.
The build md5sums file is not overwritten by the license copy process
anymore.

BCS 746-000637 746-000734

The alphaplan FWR generation is now separated to make the manifest gitlab-ci
file more easy to understand and reduce the complexity of the
package_release file.

BCS 746-000637

The merge job of a subproject include in the merge request merged by
gitlab ci, should not merge the integration branch in the manifest by
themself. This is now disabled by checking the source branch name.

This allow to merge the manifests commit at last.

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.