Re: Copying po/docbook files to repositories nightly
El dissabte, 3 de setembre de 2022, a les 0:29:34 (CEST), David Edmundson va escriure: > >Opinions? Comments? > > So our releases will end up a 1:1 with a git tag? Yes [*] > That would be > super-duper amazing for many cleanup things, including the security > aspect +1 > > What's the plan for stable branches? > We'll either need to port all active stable branches at the same time > or we will have to make sure releaseme either has multiple branches or > a runtime toggle. Yes, plan is to do everything at once. > > >My plan would be to enable this scripts over Akademy > > FYI: > Plasma beta is tagged Thu 2022-09-22 > Plasma 5.26 is tagged Thu 2022-10-06 > > Akademy is in the middle of those. > I don't see how there can be too much fall-out so it's probably fine, > but if we are expecting lots of fixes to be needed that's not the best > timing from our side. I'd say any fallout should be defenitely be sorted out before October 6th. Cheers, Albert [*] For KDE Gear we still have some fixing to do with the data/ folders https://phabricator.kde.org/T13618 > > David
Re: Copying po/docbook files to repositories nightly
El dissabte, 3 de setembre de 2022, a les 1:01:47 (CEST), Ömer Fadıl USTA va escriure: > Just wanted to learn one thing , isn't this will populate the logs with > lots of entries on git log history ? > I mean right now I am tracking git changes based on changes in history but > this will add a new entry > each night or I understand this wrong ? If you look a the example URL i posted you can see there's not a new entry each night. Cheers, Albert > Also wouldn't it be possible to fetch related translation on the fly from > the software side after releases ? > I mean translation of language X might be getting a little back lets say > 5.26 released but team X > might be late to complete their translation on time but user should have > chance to download it > after the release of it (without waiting for the next tagging ). Wouldn't > it be possible to download and install the latest > language data in applications just like users do with themes? > > Thank you > > Ömer Fadıl Usta > PGP key : 0xfd11561976b1690b > about.me/omerusta > > > Albert Astals Cid , 3 Eyl 2022 Cmt, 00:25 tarihinde şunu > > yazdı: > > As you may know, translations for apps don't live in the same place as the > > code for the apps themselves. > > > > This greatly benefits translators but is not awesome for the release > > management > > side of things since it means that for each release we need to not forget > > to > > copy the appropriate files to the appropriate place, makes tagging > > somewhat > > harder, etc. > > > > For a while now we have been running an "experimental" copy-po-qm-docbook- > > back-to-repository in a number of "select" repositories and it seems to > > have > > worked quite well, you can seem one example in > > https://invent.kde.org/plasma-mobile/alligator/-/commits/master/po > > > > The idea is to enable this for all repositories. > > > > This is a heads up, as a developer there's nothing you need to do, at most > > remove the po/ folder from .gitignore if for some reason it is there. > > > > If you're a packager you will need to make sure your scripts don't try to > > copy > > po/qm/docbook files anymore when doing a release once this is activated. > > > > My plan would be to enable this scripts over Akademy so we have the high > > bandwidth there to fix things if needed. > > > > Opinions? Comments? > > > > Cheers, > > > > Albert
Re: Copying po/docbook files to repositories nightly
Hi, this is great. For GCompris, we have some stuff to handle translation that differs from the usual (for example, the po files are in po/gcompris_.po, not po//gcompris_qt.po). I'll take a look to harmonise it with the usual. For the stable branch, we don't plan to do a release before December so it would be better to not apply it at Akademy (except if the change on GCompris side is easily backportable but I have to check). Cheers, Johnny Le sam. 3 sept. 2022 à 09:47, Albert Astals Cid a écrit : > El dissabte, 3 de setembre de 2022, a les 1:01:47 (CEST), Ömer Fadıl USTA > va > escriure: > > Just wanted to learn one thing , isn't this will populate the logs with > > lots of entries on git log history ? > > I mean right now I am tracking git changes based on changes in history > but > > this will add a new entry > > each night or I understand this wrong ? > > If you look a the example URL i posted you can see there's not a new entry > each night. > > Cheers, > Albert > > > Also wouldn't it be possible to fetch related translation on the fly from > > the software side after releases ? > > I mean translation of language X might be getting a little back lets say > > 5.26 released but team X > > might be late to complete their translation on time but user should have > > chance to download it > > after the release of it (without waiting for the next tagging ). Wouldn't > > it be possible to download and install the latest > > language data in applications just like users do with themes? > > > > Thank you > > > > Ömer Fadıl Usta > > PGP key : 0xfd11561976b1690b > > about.me/omerusta > > > > > > Albert Astals Cid , 3 Eyl 2022 Cmt, 00:25 tarihinde şunu > > > > yazdı: > > > As you may know, translations for apps don't live in the same place as > the > > > code for the apps themselves. > > > > > > This greatly benefits translators but is not awesome for the release > > > management > > > side of things since it means that for each release we need to not > forget > > > to > > > copy the appropriate files to the appropriate place, makes tagging > > > somewhat > > > harder, etc. > > > > > > For a while now we have been running an "experimental" > copy-po-qm-docbook- > > > back-to-repository in a number of "select" repositories and it seems to > > > have > > > worked quite well, you can seem one example in > > > https://invent.kde.org/plasma-mobile/alligator/-/commits/master/po > > > > > > The idea is to enable this for all repositories. > > > > > > This is a heads up, as a developer there's nothing you need to do, at > most > > > remove the po/ folder from .gitignore if for some reason it is there. > > > > > > If you're a packager you will need to make sure your scripts don't try > to > > > copy > > > po/qm/docbook files anymore when doing a release once this is > activated. > > > > > > My plan would be to enable this scripts over Akademy so we have the > high > > > bandwidth there to fix things if needed. > > > > > > Opinions? Comments? > > > > > > Cheers, > > > > > > Albert > > > > >
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
Re: Gitlab CI Dashboards and retirement of build.kde.org
Hi Ben, Thanks for the reminder! On a related note: would it be possible to add badges for CI/CD status to repositories? Quite a few projects (used to) have this in their README.md, but if I unterstand the situation correctly, Gitlab CI doesn't produce a build-status badge that one can link to. Examples: https://invent.kde.org/multimedia/kdenlive/-/blob/master/README.md[1] https://invent.kde.org/graphics/kphotoalbum/-/blob/master/README.md[2] https://invent.kde.org/graphics/digikam/-/blob/master/README.md[3] Cheers, Johannes Am Samstag, 3. September 2022, 06:45:31 CEST schrieb 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, 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. > > 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. > > > 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 [1] https://invent.kde.org/multimedia/kdenlive/-/blob/master/README.md [2] https://invent.kde.org/graphics/kphotoalbum/-/blob/master/README.md [3] https://invent.kde.org/graphics/digikam/-/blob/master/README.md
Getting Involved Into KDE Developing
Hi, I'm a KDE enthusiast who wants to get involved into KDE developing. I have been learning about KDE Frameworks nowadays but I don’t know how I do serve the needs of KDE. Is there any list of tasks or something else? By the way, I need to say that I’m relatively new to C++/Qt. A mentoring would be good for me if possible. Thanks, Emre.
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
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
Re: Gitlab CI Dashboards and retirement of build.kde.org
On Sun, Sep 4, 2022 at 2:13 AM Michael Reeves wrote: > 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. > At this time the Binary Factory is unaffected by these changes, however steps will be made in the coming weeks/months to migrate away from the Binary Factory to equivalent Gitlab jobs (although they won't be available for Merge Requests due to various technical limitations) Regards, Ben > > > 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, 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. >> > > 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. > > >> >> 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 > >
Re: Gitlab CI Dashboards and retirement of build.kde.org
On Sat, Sep 3, 2022 at 10:12 PM Johannes Zarl-Zierl wrote: > Hi Ben, > Hey Johannes, > > Thanks for the reminder! > > On a related note: would it be possible to add badges for CI/CD status to > repositories? > > Quite a few projects (used to) have this in their README.md, but if I > unterstand the situation correctly, Gitlab CI doesn't produce a > build-status badge that one can link to. > > Examples: > > https://invent.kde.org/multimedia/kdenlive/-/blob/master/README.md > > https://invent.kde.org/graphics/kphotoalbum/-/blob/master/README.md > > https://invent.kde.org/graphics/digikam/-/blob/master/README.md > 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 (replace project path and "master" as appropriate) Note that the Release badge relies on the Gitlab Releases feature being utilised, so that will likely not be usable for any of our projects. Likewise, our Cobertura coverage job currently doesn't have the necessary regular expression configured so that one also won't work - however the general "Pipeline" one should work fine. Unfortunately Gitlab does not support generating per job badges based on job names. > > > Cheers, > > Johannes > Regards, Ben > > Am Samstag, 3. September 2022, 06:45:31 CEST schrieb 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, 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. > > > > > > 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. > > > > > > > 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 > > >
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
Hi Ben, Am Samstag, 3. September 2022, 21:37:53 CEST schrieb Ben Cooksley: > On Sat, Sep 3, 2022 at 10:12 PM Johannes Zarl-Zierl > wrote: > > On a related note: would it be possible to add badges for CI/CD status to > > repositories? > > 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 > > (replace project path and "master" as appropriate) Cool, thanks for the quick and detailed reply! > Note that the Release badge relies on the Gitlab Releases feature being > utilised, so that will likely not be usable for any of our projects. > Likewise, our Cobertura coverage job currently doesn't have the necessary > regular expression configured so that one also won't work - however the > general "Pipeline" one should work fine. Good to know. > Unfortunately Gitlab does not support generating per job badges based on > job names. Not what I wanted to hear, but also not a deal-breaker... Cheers, and keep up the good work ;-) Johannes
Re: Gitlab CI Dashboards and retirement of build.kde.org
On Sun, Sep 4, 2022 at 7:54 AM Johnny Jazeix wrote: > > > 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. > Oops. That is an oversight on my part - apologies - and has now been corrected (although the URLs will have changed) Cheers, Ben > > > Cheers, > Johnny >
