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

Rename 'check_pipeline_status' to 'mirror_pipeline_result' in order to
better reflect what the function does.

Move determination of the pipeline out of this function to a new
function 'get_pipelines' so that this can be tested separately and we
can do different things depending on whether a pipeline exists or not.

Add function 'trigger_pipeline' to trigger a pipeline on a branch.

BCS 746-000635

The project name is matched with the predefined gitlab var CI_PROJECT_NAME,
which uses lower case.

Add .yamllint.yml to configure the yamllint usage, should
be used as master yamllint config from other stages also.
Apply small changes to yml files to match yamllint.

BCS 746-000640

The main install file for u-boot changed to imx-boot.tar.gz, so this
should be added to alphaplan. Leaving the imx-boot implementation
as fallback.

BCS 746-000600

Added default source revision file name to common.py.
Modified the integration_into_manifest function to set the
corresponding subproject hash in the SRCREV.conf file if the
repository is not found in the default.xml file. The
merge_into_manifest function now works even if the names of
the master branches in the manifest and in the project
repository are different.

BCS 746-000016

BCS 746-000669

The job was used to check if all scripts are able to run in the yocto
CI image. Tim and Jonas decided to remove the job and plan to change
the CI, that the yocto image does not need to execute special python
scripts. That way we may use the plain crops/poky container for the
yocto build and remove this dependency thats hard to track.

BCS 746-000643

BCS 746-000303

BCS 746-000303

BCS DevOps-000032

BCS DevOps-000032

The variable use in the deploy name was not replaced in the UI. This
hopefully cleansup the UI, and uses the project root variable in the job
only.

BCS 746-000629

Explicitly triggering a pipeline in the target repository does not work
easily from this place because we would have to distinguish between the
manifest (which uses branch pipelines) and the sub-projects (which use
merge request pipelines). This separation should not be hard-coded here,
so we move the decision whether or not to run a pipeline to the
.gitlab-ci.yml file of the target. Reverting these two commits:

63279799
    deploy_gitlab_ci: trigger pipeline only if it has not run before

dfc6204a
    deploy_gitlab_ci: trigger pipeline on integration branch

The function used to rely on the given merge request object without
checking its current state. If the given object was not in one of the
"unchecked" states, it returned immediately. The state, however, could
have changed between its last query and the call of this function, so
it now checks the state first before deciding anything.

Fix pylint errors introduced with new pylint version:
* unspecified-encoding: explicitly set encoding when opening a file
* assigning-non-slot: use "set_reference()" function instead of assigning
  a value to the "reference" attribute
* unused-variable: remove "e" variable on exceptions when not referenced

A bug in python-gitlab > 2.7.0 [1] brought this up: In the past we
relied on the merge request's setting, whether the source branch should
be deleted or not after a merge. Since we're using the API's merge
function in a fully automated task, however, the branch should always be
deleted. Add the according argument explicitly.

[1]: https://github.com/python-gitlab/python-gitlab/issues/1750

* Combine two return statements into one.
* Switch if statement order to remove else branch.

The outdated YAML 1.1 specification allowed values like 'yes' or 'no'
for boolean fields [1]. The newer spec 1.2 allows only 'true' and
'false' [2], so we update them to be conform with it.

[1]: https://yaml.org/type/bool.html
[2]: https://yaml.org/spec/1.2.2/#10212-boolean

Remove the trigger source parameter again because it did not serve the
use case. Add ref parameter instead.

BCS DevOps-000023 DevOps-000024

alphaplan_fwr.py: Creates alphaplan software packages for the build
release artifacts. According to the release, all relevant artifacts are
collected in a list structure and the corresponding aphaplan
information are added for each artifact (attributes, md5sum, path, etc.).
The list is attached to major software package structure. This structure
is written in a json file for documentation. Afterwards the structure is
send to an AlphaPlan webservice that creates the FWR articles.
alphaplan_keys.py: Generates a dictionary which contains all AlphaPlan
specific information for the artifacts. Flag classes are used to define
unique keys for the dictionary accesses.

Previously the default branch was allways used to generate the tests
from, now it is possible to specify the branch as cmdline option.
Additionally, the revision of the test repository is added to the
call of the test generator, so the tests run at a fix rev.

BCS 746-000547

Uses submit_all instead of submit.
Some code cleanup also.