- Jul 18, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@6bfa1bad Make distro and image combos dynamic -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@414ebe6d Add python code analysis via sourcery Disable all checks which do not pass currently. These should be enabled in the future along with a code refactoring to make them pass. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@df817ecf README: Add howto to create a new project.
-
- Jun 02, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@31e5a427 CI: package: Increase timeout to 90 We had timeouts during the upload of the artifacts so I increase it to 90 minutes.
-
- Apr 24, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@23680f48 Fix check for branch protection state Since the changes of 939ade2b9f98b3e1569332270a7ab16ce7d70b4a we observe that pipelines are executed on non-protected branches, which is not what we want. GitLab's documentation was a bit unclear on the according CI variables CI_COMMIT_REF_PROTECTED and CI_MERGE_REQUEST_TARGET_BRANCH_PROTECTED, as stated in this stack overflow answer: https://stackoverflow.com/a/59023344/3018229 We need to explicitly check for the variable values to be "true" instead of just checking whether they are set.
-
- Apr 04, 2023
-
-
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@939ade2b Depend intgration pipeline execution on branch protection state Previously we had the master branch hard-coded in a variable in order to determine whether to run the integration pipeline (on non-master branch) or the merge pipeline (on master branch). This variable had to be adapted everytime we copy a branch, which can potentially be forgotten and lead to problems. Remove the hard-coded branch and use the branch protection state for this decision instead in order to make this more flexible. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@dbc49ad0 Simplify yamllint job rules The rules for the yamllint jobs have been defined in the .yamllint class before. They were overridden in the manifest pipeline's yamllint job, though, which has its own rules, so we don't need them to be inherited in this case. And in the manifest integration pipeline the rules can be much easier, so define them there instead of at the class-level. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@cd8de4ff .gitlab-ci: add analyze stage for limiting YAML script blocks
-
- Mar 21, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@e943a55e Use project path instead of name in integration branch name Usually project name and path are identical after project creation. It is possible, though, to change the name of a project without changing its path. When triggering a pipeline on the integration branch, we are using the CI_PROJECT_NAME variable to reference the project. Unexpectedly, this variable contains the *path*, not the *name* of the project (see https://gitlab.com/gitlab-org/gitlab/-/issues/20030). Hence we have to use the project path in all other places where the integration branch name is constructed in our Python code.
-
- Mar 20, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@bd7025b8 Manifest: run automatic pipeline on tags
-
- Mar 09, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@068749c7 Manifest build: add support for SSH_CONFIG variable
-
- Feb 28, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d67898a2 Manifest: skip build if "skip build" label is set -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@bffc6097 Manifest: switch from branch pipelines to merge request pipelines This will make the manifest project support the "skip build" label. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5ba1ac68 Revert "Skip build if "skip build" label is set" This reverts commit 4db257d36052c74eabed7ef43a05d98d3998ffec. It does not work on the manifest, because we do not run merge request pipelines there, so CI_MERGE_REQUEST_LABELS is not set at all. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@4db257d3 Skip build if "skip build" label is set
-
- Feb 20, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@9d430fe8 Manifest integration: do not cancel previous pipelines on master -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8b08a083 Fix error handling on merge GitLab API has changed: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/94164/diffs#diff-content-c201dae00b72426693ddcb40edf6005e7702e935
-
- Feb 10, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a59a93a0 Package: Add needs to changelog, to package changelog also
-
- Feb 07, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8edbf2a6 Changelog generator: fix typo -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@e6ae06dd Changelog generator: pass projects as arguments Instead of hard-coding the project list in the changelog generator script, make them passable via arguments. This way we can have different changelogs in different envrionments. Hence we're adding the changelog job in the ci-test environment as well.
-
- Feb 06, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ed36b465 mirror_mr_pipeline: include pipeline-not-found message in output -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5ee69ab9 mirror_mr_pipeline: fix error when no pipeline found This case should trigger a new pipeline instead of reporting an error.
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@e69d303e Changelog generator: remove debug output
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0264fe09 Changelog generator: get all merge requests This fixes older releases not appearing in the changelog.
-
- Jan 10, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c657f31f mirror_mr_pipeline: improve debug output -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@473f12b1 mirror_mr_pipeline: add main call -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@88708b64 Convert CRLF to LF -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@169b2fa7 Improve mirroring MR pipeline Refactor three scripts into one in order to support triggering a new pipeline in the case of a skipped MR pipeline. This was not possible to implement with the previous three-script design. The single scripts were not used in other places anyway.
-
- Jan 09, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@897ba059 Manifest integration: remove dynamic job generation The dynamic job was only necessary because GitLab did not expand variables in the "trigger:project" keyword: https://gitlab.com/gitlab-org/gitlab/-/issues/347469 This has been fixed in GitLab 15.3, so we don't need it anymore: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/92346
-
- Jan 03, 2023
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ea1f3bad cancel_pipelines: include downstream pipelines -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c8f97623 Add job to cancel outdated pipelines in merge requests Everytime we push a new commit to a branch, a new pipeline is created. Often the pipeline for the previous commit has not finished yet, and GitLab does not automatically cancel it. It consumes valuable build time, even if we don't need the results anymore. Adding a MR pipeline job to search for previous pipelines on the same branch and cancel them explicitly.
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@bab6f811 Package: move SDK files to subfolder "sdk" -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8bcaa426 scripts: Add delete_job_artifacts script to delete all artifacts from untagged jobs For a given project all artifacts may be deleted. This was needed due to space limitations on the gitlab server.
-
- Dec 20, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@28906544 Reduce artifact expiration of build jobs to 1 week
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d404f257 Alphaplan: allow failure on import Otherwise the parent pipeline is stuck in "running" state until the manual action has been performed. See for reference: https://gitlab.com/gitlab-org/gitlab/-/issues/361574 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@dd2a6d7d Fix error message -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@04ac29ad CI-Test: fix deploy-files job -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@22c519f1 Move FTP jobs to FTP runner -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@84d0616b Add new deploy pipeline to Yocto -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@f0436868 Move reusable parts from CI-Test to common -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3d3b4d09 Yocto: fix SDK package -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@37360288 Yocto: fix SDK build -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2b6fc739 Package: add comment -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@95d6e368 alphaplan_fwr_import: add error handling -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@277d4af7 Package & deploy: do not allow missing dotenv file -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3c68ccab Alphaplan: add script for importing alphaplan data The script has mostly been copied from alphaplan_fwr.py, but with different input data. Adding a job to the CI-test environment for testing this. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3b3238a1 Alphaplan: add script for generating alphaplan data This script has mostly been copied from alphaplan_fwr.py, but with different input data (artifacts from the SoftwareStore deploy job) and without actually importing the data to the Alphaplan database. Adding a job to the CI-test environment for testing this. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@387b8184 Deploy: save variables in deploy.env -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@902c9276 Deploy: save rsync file list for later stages -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@15622149 CI-test: use caching between the pipeline stages -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a96a923e CI-test: add deploy stages for SoftwareStore and FTP Rename all stages to uppercase on this occasion, since we're adding stages with names containing multiple words. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@056f1af1 Add package class and stage -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a1972724 Add script to query job logs filtered by status, tag, and log pattern -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d501fed4 Update isort config
-
- Dec 06, 2022
-
-
-
-
disabled internal window visibility manipulation and implemented moving of non-existing surfaces, based on the frozen IVI-ID.
-
-
-
-
-
-
-
-
all requests bearing an iviId are now internally mapped to the pid and window manipulation operations now affect all windows belonging to a pid.
-
-
-
-
fixed hanging on unknown compositor-message and added feature to open new surfaces on the same screen as their parents, even if they have been moved or destroyed by then.
-
Lots of cleanup to do but this should work as a demo/test
-
-
IVI surface handling works without crashes now. PID based approach doesn't seem to have an easy way of manipulating windows.
-
first working PoC of PID based window switching approach. getScreen function is implemented, window management functions need to be adjusted.
-
- Nov 21, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@9982711f Move deploy jobs to deploy runner
-