Re: Gitlab CI Dashboards and retirement of build.kde.org
On Sun, Aug 28, 2022 at 4:40 AM Albert Astals Cid wrote: > El dissabte, 27 d’agost de 2022, a les 11:44:47 (CEST), Ben Cooksley va > escriure: > > Hi all, > > > > This evening I completed the necessary setup required to complete our > > Gitlab CI dashboards, which can now be found at > > https://metrics.kde.org/dashboards/f/aNxvXJW4k/gitlab-ci (KDE Developer > > account login required) > > > > These allow any developer to get a view on the current CI status of > > projects and groups of projects on a branch and platform basis - and > should > > hopefully provide useful insight into the overall status that can > currently > > be obtained from Jenkins. > > > > As this was the last thing holding us back from shutting down > build.kde.org, > > i'd like to proceed with retiring and shutting down build.kde.org as > soon > > as possible so the capacity it occupies can be released and reallocated > to > > Gitlab. > > > > If anyone would like to experiment with customised views for their own > > purposes (where the above provided ones are insufficient) please file a > > Sysadmin ticket. > > > > Please let me know if there are any questions on the above. > > Looks great. > Yay! > > One thing that i'm not sure i understand correctly, currently in the > General > Overview, it says that there are 3 projects currently failing kwin, > kpackage > and kphotoalbum, but then if i go to the Per Platform View i get that > rkward > is failing on windows. Shouldn't rkward also be listed as failing on the > general overview? > That is a rather curious bug, caused by the fact it was looking at things on a Pipeline vs. Job basis. The query you were looking at was looking at the list of most recent pipeline runs on a per project basis, which in the case of rkward means the last push by scripty - which was skipped (so not a failure). I've tweaked the query to look at things on a per job basis now, which skips over that issue. > > Cheers, > Albert > Cheers, Ben > > > > > Thanks, > > Ben > > > > >
Re: Gitlab CI Dashboards and retirement of build.kde.org
El dissabte, 27 d’agost de 2022, a les 11:44:47 (CEST), Ben Cooksley va escriure: > Hi all, > > This evening I completed the necessary setup required to complete our > Gitlab CI dashboards, which can now be found at > https://metrics.kde.org/dashboards/f/aNxvXJW4k/gitlab-ci (KDE Developer > account login required) > > These allow any developer to get a view on the current CI status of > projects and groups of projects on a branch and platform basis - and should > hopefully provide useful insight into the overall status that can currently > be obtained from Jenkins. > > As this was the last thing holding us back from shutting down build.kde.org, > i'd like to proceed with retiring and shutting down build.kde.org as soon > as possible so the capacity it occupies can be released and reallocated to > Gitlab. > > If anyone would like to experiment with customised views for their own > purposes (where the above provided ones are insufficient) please file a > Sysadmin ticket. > > Please let me know if there are any questions on the above. Looks great. One thing that i'm not sure i understand correctly, currently in the General Overview, it says that there are 3 projects currently failing kwin, kpackage and kphotoalbum, but then if i go to the Per Platform View i get that rkward is failing on windows. Shouldn't rkward also be listed as failing on the general overview? Cheers, Albert > > Thanks, > Ben
Re: Aura Browser in KDE Review
Am 26.08.22 um 12:27 schrieb Aditya Mehra: Hi, Aura Browser is in KDE Review and would like to release it along with Plasma Bigscreen Aura browser is a web browser specifically designed to work with remote controls and key navigation for Plasma Bigscreen, it supports a virtual mouse cursor and multiple tabs it also includes a third party AdBlock from brave browser based on easy list. You can find the repository here: https://invent.kde.org/plasma-bigscreen/aura-browser Request to please review Aura Browser. Regards, Aditya Hi, - There is no Gitlab CI, please add that - There is no support for Qt6. Please look into that and report any blockers (e.g. missing API in Qt) you find. (not a blocker for kdereview) - In https://invent.kde.org/plasma-bigscreen/aura-browser/-/blob/master/app/CMakeLists.txt#L36 the desktop file is configured but only static values are passed in. Why? - According to the desktop file the app can open .deb and .rmp files. Why would a browser be able to open those? - The executable name (AuraBrowser) is somewhat unconventional. Usually we use lowercase names, i.e. aurabrowser or aura-browser I also have some nitpicks about the CMake code, but it's probably more productive if I just make a MR instead of listing every single one. Cheers Nico
Gitlab CI Dashboards and retirement of build.kde.org
Hi all, This evening I completed the necessary setup required to complete our Gitlab CI dashboards, which can now be found at https://metrics.kde.org/dashboards/f/aNxvXJW4k/gitlab-ci (KDE Developer account login required) These allow any developer to get a view on the current CI status of projects and groups of projects on a branch and platform basis - and should hopefully provide useful insight into the overall status that can currently be obtained from Jenkins. As this was the last thing holding us back from shutting down build.kde.org, i'd like to proceed with retiring and shutting down build.kde.org as soon as possible so the capacity it occupies can be released and reallocated to Gitlab. If anyone would like to experiment with customised views for their own purposes (where the above provided ones are insufficient) please file a Sysadmin ticket. Please let me know if there are any questions on the above. Thanks, Ben
