Integrate gitlab-ci/CI-deploy-yocto and 19 more
CI: Remove debug, enable yocto manifest deploy
--
CI: Add function to merge the gitlab-ci MRs
--
CI: Add function to merge the gitlab-ci MRs
--
CI: Harmonize foobar and yocto CI files
Also set yocto deploy job to manual to test merge.
--
CI: Enable analyze stage again in .gitlab-ci.yml again
--
CI: Add common.yml containing common code for manifest and integration.
--
CI: Use only one stage for integration to allow parallel execution
--
CI: Rewrite check job python file to use gitlab api (no clone anymore)
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.
--
CI: Limit clone depth to 1 for speed
--
CI: Adapt manifests-integration.yml and manifest.yml for yocto projects
Integrates the changes done in the foobar- yml files to the yocto projects.
--
CI: Add all yocto projects to the job list
--
CI: Generate .gitlab-ci.yml with include commands in deploy step
This change should be reverted after once used. It is needed to initially add the include .gitlab-ci.yml in all subprojects.
--
CI: Check: integration branch may have multiple commits
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.
--
CI: Disable foobar manifest build for integration branch
BCS 746-000646
--
CI: Create integration branch optionally also when no submodule change is detected
--
CI: Implement that a merge-request may also be specified with project!number
Before only the ID was used but the CI_OPEN_MERGE_REQUESTS variable has the complete path.
--
CI: Multideploy: Detect exiting integration branch
--
CI: Deploy: create integration branches and trigger pipelines in subprojects
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.
--
CI: Add common gitlab-ci file for all yocto repositories.
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
--
CI: Update include file's ref in gitlab-ci.yml when deploying changes
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