Gitlab CI - Inbound

[Vlad Zahorodnii]

On 9/7/21 1:21 PM, Ben Cooksley wrote:
> On Tue, Sep 7, 2021 at 10:14 PM Vlad Zahorodnii <vlad.zahorodnii at kde.org 
> <mailto:vlad.zahorodnii at kde.org>> wrote:
> 
>     On 9/7/21 12:22 PM, Ben Cooksley wrote:
>      > On Tue, Sep 7, 2021 at 8:48 PM Vlad Zahorodnii
>     <vlad.zahorodnii at kde.org <mailto:vlad.zahorodnii at kde.org>
>      > <mailto:vlad.zahorodnii at kde.org
>     <mailto:vlad.zahorodnii at kde.org>>> wrote:
>      >
>      >     On 9/5/21 3:18 PM, David Faure wrote:
>      >      > On dimanche 5 septembre 2021 12:26:50 CEST Ben Cooksley wrote:
>      >      >> On Sun, Sep 5, 2021 at 10:22 PM David Faure
>     <faure at kde.org <mailto:faure at kde.org>
>      >     <mailto:faure at kde.org <mailto:faure at kde.org>>> wrote:
>      >      >>> For frameworks, I think we should be able to write a
>     one-time
>      >     script that
>      >      >>> generates .kde-ci.yml files using the dependencies listed in
>      >     kde-build-
>      >      >>> metadata (and the platforms listed in metainfo.yaml) ?
>      >      >>
>      >      >> Yes, that should work nicely (although that information
>     now lives in
>      >      >> sysadmin/repo-metadata, dependencies folder)
>      >      >
>      >      > All done for Frameworks.
>      >      >
>      >      > The script that collects platforms from metainfo.yaml won't be
>      >     useful for
>      >      > other KDE modules, but the script that collects deps from
>      >     dependency-data-kf5-
>      >      > qt5 is attached, in case it's useful to anyone else.
>      >
>      >     Is there a file that maps legacy project paths to gitlab
>     project paths?
>      >     dependency-data-kf5-qt5 lists projects with their legacy paths.
>      >
>      >
>      > The individual project YAML files in sysadmin/repo-metadata
>     contain this
>      > information.
>      > The legacy project path can be found under 'projectpath' while the
>      > Gitlab paths are under 'repopath'
> 
>     Thanks! I've attached a quick and dirty python script that parses
>     project dependencies from repo-metadata and prints corresponding gitlab
>     project paths.
> 
>     Example usage
> 
>         python project-deps.py --repo-metadata
>     /data/projects/src/repo-metadata/ kde/workspace/kwin
> 
>     Output
> 
>     Dependencies:
>         'requires':
>           'frameworks/extra-cmake-modules': '@stable'
>           'plasma/kdecoration': '@stable'
>           'plasma/kscreenlocker': '@stable'
>           'plasma/kwayland-integration': '@stable'
>           'plasma/breeze': '@stable'
>           'plasma/kwayland-server': '@stable'
> 
> 
> Please note that the above is missing a 'on' section as required for 
> each Dependencies section in the .kde-ci.yml file.
Yeah... Is there a database or something that can be queried to fill in 
the "on" section?