ALP Git-Packaging-Workflow group created
Git Packaging Workflow Exploration A few colleagues from SUSE, namely the build service team and others like myself are exploring the options on what the best way would be to use Git, rather than the current open Build Service source handling, for storing openSUSE / SLE package sources. This was originally launched under the ALP Workgroup umbrella but for now is timeline wise decoupled from this effort, except that if we would decide to switch, that it would have to happen before the first commercially supported Alp release would be branched off openSUSE Factory. For now, all of this is in the exploration and experimentation phase and no decision in either way has been taken. Meanwhile, we do however feel confident and organized enough to be open to wider feedback. If you're interested in any of the topics please let the work package driver know, or if in any doubt contact me. Here's the current list of work packages and their state: * Exploration of the Git Hosting options (run by me) openSUSE already has some experience with Pagure.io (used by https://code.opensuse.org/ for example) and GitHub (used by various openSUSE projects under https://github.com/openSUSE) as well as some projects also in GitLab (used by a few community efforts as well as SUSE-internally for hosting) so we explored another option named Gitea, which is now available to the community under https://gitea.opensuse.org/. Please note that this is not a production service, and can lose data or disappear at any point in time, it is only being operated in the context of the Git packaging workflow exploration. * Exploration of the history import from the SUSE and openSUSE build service source history (run by Stephan Kulow). Stephan Kulow has managed to import the majority of existing history of packages that landed in released products or in openSUSE Tumbleweed as history into package-git repositories and published under https://gitea.opensuse.org/rpm . As an example the history of zlib is here: https://gitea.opensuse.org/rpm/zlib/commits/branch/factory which is significantly more detailed than a similar effort implemented by Bernhard Wiedemann a couple of years ago on our code.opensuse.org instance: https://code.opensuse.org/package/zlib/commits/master Your feedback on the history import quality and how it could be made better is very much appreciated. The key difference compared to the pagure setup is that we use Git LFS for storing large files (like tarballs for example) and currently these large files are mapped via a small redirector proxy directly to the openSUSE build service source service. With that the git repository history is extremely small and very manageable for local cloning. * Exploration of the git packaging workflow going forward. Alberto Planas, with contributions by others, has written up ideas and options in the following document: https://github.com/aplanas/openSUSE-git/blob/main/notes-about-git.md Please provide feedback either as a pull request or as a discussion entry in the forum here: https://github.com/aplanas/openSUSE-git/discussions * Exploration of build and status integration. This one is less well-defined, but for now it is about automatically syncing new changes in the git repository with the state of the Build Service instance that is used for building as well as exploring the options for reporting back the build status into the Git Hosting infrastructure. This is currently worked on by Adrian Schroeter. We store the meeting time and minutes under https://en.opensuse.org/openSUSE:ALP/Workgroups/Git-Packaging-Workflow In case there are any questions, feel free to reach out to related work package owners or myself. Greetings, Dirk
participants (1)
-
Dirk Müller