Archive:ALP/Workgroups/Git-Packaging-Workflow/Minutes/20220803

Attendees

Status update:
- coolo refreshed all git repositories with the latest state, performance for updating was good
- dirk started working on the gitea 1.17 update, still wip
announcement of the git-packaging-workflow group to the factory mailing list led to feedback:
- Interaction with server-side OBS services could be problematic (currently forbidden by policy in (open)SUSE dists)
Some problems in the expected behaviour of git-LFS and forks. Please, test it and gain experience
Aplanas is still refactoring the migration script. Do not focus on speed (the cache can be filled before the migration) but in clarity and remove code duplication
coolo started in a playground with the git packaging workflow
- modifying requires creating a fork and detaching, which feels awkward
- requires using “osc vc” for maintaining the .changes files
- AI: all: use it and identify the quirks
Eduardo that OBS has CI/CD integration with GitLab and GitHub, but not yet Gitea
- Progress of Gitea support within the CI/SCM integration from the Build Solution team is kept here: https://trello.com/c/S4WdyCJW/185-support-gitea
What is the high level plan?
- Not yet defined
- Best next steps is to identify the missing steps
- Test scmsync workflow, feel the pain and provide feedback

AI: all: start using the git packaging workflow and identify the quirks
AI: help dan to update documentation on how to use git based packages (add to https://openbuildservice.org/help/manuals/obs-user-guide/ ?)
AI: enavarro research how Gitea can be added to the list of existing CI/CD integrations
AI: dcermak experiment with git tags for replacing the .changes file ?

~~AI: Dirk: post initial proposal from alberto and this meeting minutes to the relevant community channels~~
AI: Adrian and snbarth to see how build status can be reported in the gitea webui for a particular source state