- Dec 13, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d5d8ebd1 CI:debug add timestamps -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@437cefe9 CI: Add test command to show ip settings before build -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a6f489db CI:deploy and uploadftp: extends infrastructe again to set the image correctly Without this the image was not defined and the runners default image is used. This is against the concept to store image revisions in the commits to keep things running after an upgrade and didn't work because the default image has no python. -- 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 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d6149039 Harmonize import order in all python files via isort -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8b4f3c38 Add isort job to analyze stage isort is a Python utility to sort imports alphabetically, and automatically separated into sections and by type. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@049a2268 common: add constant for default GitLab URL -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d04adeae common: use uppercase for constants -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@7a4255b7 CI-test: add simulated SDK build -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@de4adce6 CI-test: use infrastructure runner for build simulation -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@ba44c129 CI-test build: improve build simulation Instead of copying a packaged release from the SoftwareStore, download artifacts from an actual build job. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@37200614 build-common: add group headers -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@bdc50deb Yocto build: group commands for saving build.env
-
- Nov 21, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@9982711f Move deploy jobs to deploy runner
-
- Nov 10, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@e48b4c0b package_release: Do not fail if a file does not exist
-
- Oct 18, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a5e27f6e FTP upload: Add flag to hide FTP upload stage This is a workaround to prevent customer releases being uploaded to our public FTP area. It should be removed as soon as we support uploading to different FTP target folders.
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@543a2170 manifest_package: add release suffix Customer specific manifest projects can now set the RELEASE_SUFFIX variable, which then gets appended to the deployment folder names. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c763c43f alphaplan_fwr: change variable "release_name_local" to "release_name" Otherwise it can be assumed that it might be correlated with outputdir_local, which is not the case. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2d8d26a5 package_release: more refactoring - Make output-dir an argument that can be passed multiple times instead of hard-coding two dirs with certain meanings. - Remove LOCALDIR variable from package.env, because it is not used anywhere (only occurence was job class ".uploadsdkftp" which wasn't used anywhere either). -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@dc3698c8 package_release: refactoring Improve readability of package_release.py and its submodule generate_release_metadata.py. - Add describing comments throughout the file. - Remove duplicate code from functions. Simplify them, so that they do what their names say (and nothing more). - Rename variables and function arguments to make their purpose clearer. - Harmonize variable names with their corresponding command line arguments. - Add pydoc for functions. - Add type declarations to function arguments. - Generate MD5 and metadata files in the source directories so that they can be copied along with the rest of the files.
-
- Sep 27, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c831d1da get_integration_sources: check if CI is enabled Trying to query CI variables on a project which does not have the CI feature enabled leads to an HTTP 403 (forbidden) error. Check whether CI is enabled using the "jobs_enabled" flag.
-
- Sep 20, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5e3dfaea CI:deploy: fix fngsystem deployment path The match to detect fngsystem still contained 'guf'. Changed to 'seco'. BCS 746-001043
-
- Sep 14, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@f8d6de86 Make check error message more verbose -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@21e7edeb Improve ci-test build -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@76bd81d8 Fix check job rules -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a6721243 Move check job to parent pipeline -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@593784e1 Refactor check_if_integration_branch_is_up_to_date - Use "source" and "target" terminology in the script, just like in the GitLab CI variables. - Spefify data types for function arguments. - Rename function arguments to better reflect their data types. - Move determination of integration branch into main function, so that the successfull status message can be more verbose. - Remove parent_merge_request feature and checking for gitlab-ci integrations, because the check job does not run on gitlab-ci integration branches at all. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@45b49ee3 Remove build stage on master We don't need to explicitly trigger a build after merging changes in gitlab-ci. A master pipeline on the target projects runs automatically.
-
Jonas Höppner authored
As it is difficult/impossible to undo a remove, the item to remove was stored in a variable. This variable is reset here, to undo the remove.
-
- Sep 06, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a0f7e84f Rename pipeline stages to reflect YAML filenames
-
- Sep 05, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d25cdebf Really fix potential error message in retrigger job TypeError: 'NoneType' object is not subscriptable Example: https://git.seco.com/seco-ne/yocto/manifest/-/jobs/129201
-
- Aug 31, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@3eef782e deploy_gitlab_ci: integrate only correct projects into the manifest Previously we integrated all projects into the manifest, even those that belonged to a different manifest branch. That led to all manifests having the same project revisions, even if they should be different due to different intgrated project branches. Save a list of integration sources for each manifest branch separately now, so that we can check which project belongs to which manifest branch later. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@2b851ac6 Fix potential error message in retrigger job TypeError: 'NoneType' object is not subscriptable Example: https://git.seco.com/seco-ne/yocto/infrastructure/ci-test/minimal-manifest/-/jobs/127610 -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c3fd0ecc Check if variable is defined before checking it value -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c1be0f4b Fix jinja2 "or" operator -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8da534ec Run integration pipeline for target branch only When we're integrating a single branch into a single manifest branch, there is no need to run the intgeration pipeline for all configured integrations, but only for those that match the target branch of the current merge request. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8c94b725 ci-test: add job to check for correct foo branch This should catch an error where during a gitlab-ci merge process the wrong foo branch is integrated into the manifest, which happened in Yocto. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@163c7e1e Add yml extension to jinja2 templates -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@59523aa0 check job: disable verbose output -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@28bf0065 retrigger: add job states to log message
-
- Aug 30, 2022
-
-
GitBot authored
-- Commit: seco-ne/yocto/infrastructure/gitlab-ci@fd742017 deploy_gitlab_ci: fix target branch in integration merge request We need to pass the correct target branch to the merge request creation instead of using the project's default branch. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@38379173 Run yamllint job on gitlab-ci integrations Otherwise no pipeline is created at all in these merge requests, which prevents the MR from being merged. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@dce4f8a3 changelog_generator: Fix machine project ID We have deleted the original project due to git corruption. Replace with the new project's ID. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a7aa7c26 deploy_gitlab_ci: fix project argument passing -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@8a38f194 Put all manifest intgeration jobs into a single stage -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a09564c1 deploy_gitlab_ci: explicitly pass gitlab-ci project and branch -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@172e7625 Improve error messages -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@f0f5a370 Improve naming of functions and variables -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@c8b484ca Retrigger MRs from all integrating projects Instead of getting the projects from the manifest file, search them via their INTEGRATION variable. Improve log messages on this occasion: print URL instead of just IDs. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5e75bfc1 Deploy gitlab-ci to multiple branches Add different integration jobs for different manifest branches. The merge stage only has one job for each manifest, though, because otherwise we cannot guarantee a consistent state for all branches. Extend the deploy script for this purpose, so that it can deploy to multiple manifest branches at once. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@771dcff1 Fix temporary dir path We were passing the complete TemporaryDirectory object to the repo clone function instead of just the path string, resulting in the repo being cloned into a local dir "<TemporaryDirectory '/tmp/tmphwakypf8'>". Fix this to actually use the generated temp dir. This change makes it necessary to keep the TemporaryDirectory object reference until we don't need the directory anymore, otherwise it will be removed immediately. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@dce219c8 Print less important output in grey color -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@5e36261d deploy_gitlab_ci: remove hard-coded integration targets Get targets dynamically using the INTEGRATION variable instead. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@94cd6781 Recurse to child pipelines on retrigger This makes it possible to retrigger jobs that are not part of the given pipeline but in any nested child pipeline of it. -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@fb1219a7 Ignore __pycache__ in scripts directory -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@0c29c995 Refactoring: rename arguments for consistency -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@d461090b Remove hard coded project and branch variables MANIFEST_PROJECT, MASTER_BRANCH_MANIFEST, MASTER_BRANCH_PROJECT -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@a4aae414 Add rules for integration pipeline -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@bfa38b24 Improve log messages -- Commit: seco-ne/yocto/infrastructure/gitlab-ci@1c9670d9 commit_and_push: do not pass branch Branch can be implicitly determined via the repo.
-
- Aug 17, 2022
-
-
Tobias Kahlki authored
The packagegroup for the seco packages was still included via the old guf name.
-
Tobias Kahlki authored
The demo was renamed in the distro layer. Applied the change here as well.
-
Tobias Kahlki authored
We now use seconorth as prefix for all our images. Renamed the images without GPLv3 to reflect the change.
-
- Aug 03, 2022
-
-
Jonas Höppner authored
Also remove commented old exceptions from the license rules.
-
Jonas Höppner authored
-
Jonas Höppner authored
-
Jonas Höppner authored
-
- Aug 02, 2022
-
-
Jonas Höppner authored
-
Jonas Höppner authored
-
Jonas Höppner authored
Some of the removal was previously done in meta-seconorth-distro, but I think its better to do all this stuff inside this layer.
-
Jonas Höppner authored
-
Jonas Höppner authored
Because of licenses the following dep chain was failing: image-small -> packagegroup-core-tools-debug -> gdbserver
-
Jonas Höppner authored
ltp is in the DEPENDS list, as we use the ltp-headers, but ltp RDEPENDS a lot of tools not available without gplv3, thus we need to rewrite emc-test-suite or write a package to only provide the ltp headers.
-
Jonas Höppner authored
-
Jonas Höppner authored
-
Jonas Höppner authored
- qtbase -> mysql5 -> coreutils - qtbase -> sqlite -> readline - qtbase -> postgresql -> readline
-
Jonas Höppner authored
Also remove package-management from image-feature
-
Jonas Höppner authored
Both tools are not available without gplv3 or meta-gplv2
-
Jonas Höppner authored
diffutils and bash are only available as gplv3
-
- Aug 01, 2022
-
-
Jonas Höppner authored
The nogplv3 layer is supposed to do no changes the the seconorth distro when included into the bblayers but not selecting the nogplv3 distro. To achive this, all modifications done in bbappend files need to use the 'nogplv3' override to filter this out.
-
Jonas Höppner authored
-
Jonas Höppner authored
-
Jonas Höppner authored
-
Jonas Höppner authored
-
Jonas Höppner authored
-
- Jul 28, 2022
-
-
Jonas Höppner authored
-
- Jul 27, 2022
-
-
The explicit PACKAGE_EXCLUDE should not be necessary and prohibited by using INCOMPATIBLE_LICENSE. Further if a compatible package is available (i.e. for meta-gplv2) PACKAGE_EXCLUDE would prevent it from being included in an image.
-