- Nov 15, 2022
-
-
Tim Jaacks authored
-
- Nov 10, 2022
-
-
Jonas Höppner authored
-
- Oct 18, 2022
-
-
Tim Jaacks authored
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.
-
Tim Jaacks authored
Customer specific manifest projects can now set the RELEASE_SUFFIX variable, which then gets appended to the deployment folder names.
-
Tim Jaacks authored
Otherwise it can be assumed that it might be correlated with outputdir_local, which is not the case.
-
Tim Jaacks authored
- 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).
-
Tim Jaacks authored
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
-
-
Tim Jaacks authored
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 19, 2022
-
-
Jonas Höppner authored
The match to detect fngsystem still contained 'guf'. Changed to 'seco'. BCS 746-001043
-
- Sep 14, 2022
-
-
Tim Jaacks authored
-
Tim Jaacks authored
-
Tim Jaacks authored
-
Tim Jaacks authored
-
Tim Jaacks authored
- 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.
-
- Sep 12, 2022
-
-
Tim Jaacks authored
We don't need to explicitly trigger a build after merging changes in gitlab-ci. A master pipeline on the target projects runs automatically.
-
- Sep 06, 2022
-
-
Tim Jaacks authored
-
- Sep 05, 2022
-
-
Tim Jaacks authored
TypeError: 'NoneType' object is not subscriptable Example: https://git.seco.com/seco-ne/yocto/manifest/-/jobs/129201
-
- Aug 31, 2022
-
-
Tim Jaacks authored
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.
-
Tim Jaacks authored
TypeError: 'NoneType' object is not subscriptable Example: https://git.seco.com/seco-ne/yocto/infrastructure/ci-test/minimal-manifest/-/jobs/127610
-
Tim Jaacks authored
-
Tim Jaacks authored
-
Tim Jaacks authored
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.
-
- Aug 30, 2022
-
-
Tim Jaacks authored
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.
-
Tim Jaacks authored
-
Tim Jaacks authored
-
Tim Jaacks authored
-
Tim Jaacks authored
We need to pass the correct target branch to the merge request creation instead of using the project's default branch.
-
Tim Jaacks authored
Otherwise no pipeline is created at all in these merge requests, which prevents the MR from being merged.
-
Tim Jaacks authored
We have deleted the original project due to git corruption. Replace with the new project's ID.
-
Tim Jaacks authored
-
- Aug 29, 2022
-
-
Tim Jaacks authored
-
Tim Jaacks authored
-
Tim Jaacks authored
-
Tim Jaacks authored
-
Tim Jaacks authored
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.
-
Tim Jaacks authored
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.
-
Tim Jaacks authored
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.
-
Tim Jaacks authored
-
Tim Jaacks authored
Get targets dynamically using the INTEGRATION variable instead.
-
Tim Jaacks authored
This makes it possible to retrigger jobs that are not part of the given pipeline but in any nested child pipeline of it.
-