Re: Gitlab CI Dashboards and retirement of build.kde.org
On Sun, Sep 4, 2022 at 8:51 PM Gilles Caulier wrote: > Hi Ben, > HI Gilles, > > With build/binary-factory , it was possible to get an Embeddable Build > Status Icon as this one : > > > https://binary-factory.kde.org/view/AppImage/job/Digikam_Nightly_appimage-centos7/badge/ > > Does this feature still exist with Gitlab infrastructure ? > Yes, quoting my earlier email: [quote] Gitlab provides a limited selection of badges - which can be found at: - https://invent.kde.org/multimedia/kdenlive/badges/master/pipeline.svg - https://invent.kde.org/multimedia/kdenlive/badges/master/coverage.svg - https://invent.kde.org/multimedia/kdenlive/-/badges/release.svg [/quote] You'll need to swap multimedia/kdenlive to graphics/digikam but otherwise that should work fine. Please note that the Binary Factory is not impacted by this, so anything relating to the Binary Factory is unchanged at this time. > > Thanks > > Gilles > Regards, Ben > > Le sam. 27 août 2022 à 11:45, Ben Cooksley a écrit : > > > > 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 >
Re: Gitlab CI Dashboards and retirement of build.kde.org
Hi Ben, With build/binary-factory , it was possible to get an Embeddable Build Status Icon as this one : https://binary-factory.kde.org/view/AppImage/job/Digikam_Nightly_appimage-centos7/badge/ Does this feature still exist with Gitlab infrastructure ? Thanks Gilles Le sam. 27 août 2022 à 11:45, Ben Cooksley a écrit : > > 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
Re: Gitlab CI Dashboards and retirement of build.kde.org
I now have no way to even test macosx builds for kdiff3, I have no access to a 64bit Intel mac. What are the plans for this and Windows builds. I have a functional windows based craft installed locally. Sep 3, 2022 12:47:06 AM Ben Cooksley : > On Sat, Aug 27, 2022 at 9:44 PM Ben Cooksley wrote: >> 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[http://build.kde.org], i'd like to proceed with retiring and >> shutting down build.kde.org[http://build.kde.org] as soon as possible so the >> capacity it occupies can be released and reallocated to Gitlab. > > As previously indicated, I have now shutdown > build.kde.org[http://build.kde.org] along with the domain that supported it's > version of the CI tooling. > The repository containing that tooling has now also been archived, and the > former build.kde.org[http://build.kde.org] domain has been redirected to > metrics.kde.org[http://metrics.kde.org]. > > The server which was acting as a builder for > build.kde.org[http://build.kde.org] will be rebuilt in the coming days and > reallocated to support Gitlab CI workloads. > >> >> 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 > > Thanks, > Ben signature.asc Description: PGP signature
Re: Gitlab CI Dashboards and retirement of build.kde.org
Le sam. 3 sept. 2022 à 21:28, Ben Cooksley a écrit : > On Sat, Sep 3, 2022 at 9:29 PM Gleb Popov <6year...@gmail.com> wrote: > >> On Sat, Sep 3, 2022 at 7:46 AM Ben Cooksley wrote: >> > >> > As previously indicated, I have now shutdown build.kde.org along with >> the domain that supported it's version of the CI tooling. >> > The repository containing that tooling has now also been archived, and >> the former build.kde.org domain has been redirected to metrics.kde.org. >> > >> > The server which was acting as a builder for build.kde.org will be >> rebuilt in the coming days and reallocated to support Gitlab CI workloads. >> > >> > Thanks, >> > Ben >> >> What should be used instead of binary-factory? How do I transform this >> link? >> >> >> https://binary-factory.kde.org/view/Windows%2064-bit/job/Kate_Release_win64/1762/artifact/kate-22.08.0-1762-windows-msvc2019_64-cl.exe > > > At this time the Binary Factory is not impacted by this. > > Regards, > Ben > Hi, I think the issue mentioned by Glen is that this link (and all other artifacts from binary-factory) is redirected to https://build-artifacts.kde.org/binary-factory/Kate_Release_win64/1762/kate-22.08.0-1762-windows-msvc2019_64-cl.exe which does not exist. Cheers, Johnny
Re: Gitlab CI Dashboards and retirement of build.kde.org
On Sat, Sep 3, 2022 at 7:46 AM Ben Cooksley wrote: > > As previously indicated, I have now shutdown build.kde.org along with the > domain that supported it's version of the CI tooling. > The repository containing that tooling has now also been archived, and the > former build.kde.org domain has been redirected to metrics.kde.org. > > The server which was acting as a builder for build.kde.org will be rebuilt in > the coming days and reallocated to support Gitlab CI workloads. > > Thanks, > Ben What should be used instead of binary-factory? How do I transform this link? https://binary-factory.kde.org/view/Windows%2064-bit/job/Kate_Release_win64/1762/artifact/kate-22.08.0-1762-windows-msvc2019_64-cl.exe
Notice of impending change to Gitlab CI
Hi all, Currently our Gitlab CI jobs for Linux (SUSE) and Android (Ubuntu) run their respective jobs as root within the Docker containers that Gitlab spawns for them. This is a restriction that was previously required by the simultaneous use of these same images by Jenkins, which following the shutdown of build.kde.org this weekend is no longer a problem. I will look into making this adjustment to our CI image(s) in the coming week for Linux (SUSE). Once implemented, tests which made use of root privileges may begin to fail (and those that were incompatible with it will begin to pass). Android Qt 5 builds still share the image with the Binary Factory and therefore will have to continue to run as root at this time until we are able to discontinue the BInary Factory (or at least, Android's use of it). Thanks, Ben
