blogilo sneaked into Applications openSUSE builds, even if not in kde-build-metadata
Closed, ResolvedPublic

Description

See
https://build.kde.org/view/Applications/job/Applications%20blogilo%20kf5-qt5%20SUSEQt5.9/
https://build.kde.org/view/Applications/job/Applications%20blogilo%20stable-kf5-qt5%20SUSEQt5.9/

Confusing to me is that blogilo not listed in logical-module-structure, and since this morning also gone from dependency-data-*. Still after a run of DSL Job Seeds the build jobs are present.

Blogilo though is still listed as maintained in repo-metadata, cmp.
https://cgit.kde.org/sysadmin/repo-metadata.git/tree/projects/kde/pim/blogilo

Seems CI gracefully deals with no info in kde-build-metadata? Intended?

I meanwhile poked the release managers about the need to also update repo-metadata on dumping projects/repos, so issue might resolve. Still found this surprising CI behaviour, so reported as feedback :)

kossebau created this task.Nov 15 2017, 2:06 PM
Restricted Application added a subscriber: sysadmin. · View Herald TranscriptNov 15 2017, 2:06 PM
bcooksley closed this task as Resolved.Nov 18 2017, 7:30 AM
bcooksley claimed this task.
bcooksley added a subscriber: bcooksley.

The CI supports wildcard rules in the dependency data, which in many instances will fill the needs of most projects (assuming just dependence on Frameworks). The current wildcard rules are:

*: Qt5[stable]
*: kdesupport/extra-cmake-modules
extragear/kdevelop/plugins/*: extragear/kdevelop/kdevelop
playground/devtools/plugins/*: extragear/kdevelop/kdevelop
playground/devtools/kdev-*: extragear/kdevelop/kdevelop
kde/kdenetwork/ktp*: kde/kdenetwork/ktp-common-internals
kde/*: frameworks/kf5umbrella
extragear/*: frameworks/kf5umbrella

Also note that for non-wildcard rules, as well as when processing the RHS of a dependency rule (where wildcards aren't supported) the CI system ignores the path and just references the actual project/repository name at the end. This is to allow for things to move around while minimizing breakage.

In regards to logical-module-structure, similar support for wildcards is also available, for instance:

"frameworks/*" : {
    "stable-qt4": "",
    "latest-qt4": "",
    "kf5-qt5": "master",
    "kf5-minimum": "master",
    "stable-kf5-qt5": "master"
},

So this is all intended behaviour. Most of the entries in LMS these days are probably duplicative from the initial Qt 4 -> Qt 5 port and can probably be retired subject to being reviewed.