Dear KMyMoney-Developer readers, not all of you reading this list are active KMyMoney developers. Nevertheless, I want to spread the word about the below information about the upcoming move to a Gitlab based infrastructure provided by KDE sysadmin.
Since this will affect the way we access the code repository you all need to know about that move. Well, at least those of you who build from the source code out of the repo. A word of caution: some of our procedures will change in the future and some will stay as they are. Those that stay are easy to handle: business as usual. To the ones that change we will have to get used to in the upcoming weeks and months. This will certainly be a bit tricky and a rough ride here and there in the beginning since I am by far not a Gitlab expert. I would rather say, I start to learn the features and how to use it right now. So if one of you is experienced in Gitlab usage, please let me know so I can contact you in case of questions. So much for today. As more details are made available by sysadmin I will forward that to this list as well. Stay safe and healthy and have a nice remaining weekend Thomas ---------- Forwarded Message ---------- Subject: Migration to Gitlab -- Update Date: Sonntag, 10. Mai 2020, 09:48:50 CEST From: Ben Cooksley <bcooks...@kde.org> To: kde-core-devel <kde-core-de...@kde.org>, kde-devel <kde-de...@kde.org> CC: sysadmin <sysad...@kde.org> Good morning all, We recently had a rather lengthy discussion concerning the final manner in which Gitlab will be deployed for KDE. To ensure everything is clear, we'd like to summarise that and present the final structure which has been agreed upon, along with details on tools that will be able to assist Developers with the migration and working with Gitlab in the long term. -- Timeline -- At the moment we are intending to perform a bulk migration of all repositories from git.kde.org to invent.kde.org on 16 May 2020. When this transition commences, git.kde.org will be made read-only. Following this, the current system will be kept active in a read-only configuration for two weeks (until 30 May 2020) to allow for everyone to smoothly transition local clones and any automated systems over to the new Gitlab setup. -- Structure -- Following lengthy discussion in the original thread, it was agreed that the original sysadmin proposal of various categories would be implemented, with repositories organised according to that structure. You can find this documented at https://cgit.kde.org/sysadmin/repo-metadata.git/tree/projects-invent?h=bshah/invent -- Tooling -- To assist developers with the transition process, Sysadmin has developed a utility ('git kpull') which once setup on a developers system will automatically migrate any git.kde.org/anongit.kde.org to the new structure automatically, before proceeding with a regular 'git pull' when run in a Git repository. Additionally, as some developers had concerns regarding locating repositories, an additional utility known as 'git kclone' is being shipped as well. This will allow developers to run "git kclone <identifier>" to clone a repository. In the majority (95%) of cases we expect "<identifier>" to be identical to the repository name (frameworks/kcoreaddons being kcoreaddons for instance), however where the name is common (such as 'dialer') then it will be prefixed by the name of the originating project (so maui/dialer would have an identifier of maui-dialer) following the convention we use at the moment for projects wishing to have a repository using a common name. It should be noted that 'git kclone' is also able to perform bulk clones based on wildcard patterns (which you could use to clone all frameworks by running "git kclone frameworks/*" for example) Instructions on how to set this up on your system will be sent out closer to the migration commencing. -- Continuous Integration -- Following the migration, we will continue to use our existing Jenkins based setup. Migration to using Gitlab for CI purposes will take place at a later date once the necessary adjustments to the CI infrastructure have been completed. During the intervening time CI capability will be available on Gitlab for evaluation and testing purposes only. This is not supported as a standard production level service by Sysadmin and therefore should not be relied upon by projects as part of their workflow. -- Tasks -- Tasks will be migrated from Phabricator at a future point in time. These will remain on Phabricator for the time being and are not affected by the migration. Projects wishing to start entirely new boards and not needing to work with existing boards on Phabricator should feel free to begin making use of their new Gitlab boards following the migration. -- Migration from Phabricator -- Existing code reviews will not be migrated from Phabricator as part of this migration process and will need to be completed using the usual process on Phabricator. It is expected that following the completion of the migration of code hosting that no further new reviews will be started on Phabricator. Please note that because Phabricator is dependent on the existing git.kde.org/anongit.kde.org setup, once those are shutdown the hooks that automatically close reviews will no longer operate. Tasks will be migrated in a future step, following which Phabricator will be shutdown. Based on initial testing we expect to be able to provide a static copy of Phabricator (for reviews only as tasks will have been migrated at this stage) for long term archival purposes. -- Conclusion -- Should anyone have any questions regarding the above, please let us know! Thanks, Ben Cooksley KDE Sysadmin ----------------------------------------- -- Regards Thomas Baumgart https://www.signal.org/ Signal, the better WhatsApp ------------------------------------------------------------- There's a fine line between a numerator and denominator. Only a fraction of people will get the joke. -------------------------------------------------------------
signature.asc
Description: This is a digitally signed message part.
