gluebuddy issueshttps://gitlab.archlinux.org/archlinux/gluebuddy/-/issues2024-03-22T04:31:11Zhttps://gitlab.archlinux.org/archlinux/gluebuddy/-/issues/13Set repository default branch2024-03-22T04:31:11ZChristian HeuselSet repository default branchWhen testing for https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/186 I had pushed to https://gitlab.archlinux.org/archlinux/packaging/packages/yolo-test-package-please-ignore. Since I first pushed to the branch 'unstable...When testing for https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/186 I had pushed to https://gitlab.archlinux.org/archlinux/packaging/packages/yolo-test-package-please-ignore. Since I first pushed to the branch 'unstable' this also became the repositories default branch.
I think when the branch exists gluebuddy should make the 'main' branch the default & protected branch for repos in the packaging namespace.https://gitlab.archlinux.org/archlinux/gluebuddy/-/issues/12[FEATURE] automatic packaging repo archival2024-03-21T17:20:46ZChristian Heusel[FEATURE] automatic packaging repo archivalSo when talking about https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/166 we realized that it would be great if gluebuddy would archive repos which:
- are not in the official package repositories. This can be done via t...So when talking about https://gitlab.archlinux.org/archlinux/devtools/-/merge_requests/166 we realized that it would be great if gluebuddy would archive repos which:
- are not in the official package repositories. This can be done via the newly created endpoint in AURweb that maps maintainers to packagebases
- did not recieve a commit in X weeks (i.e. 4-8 weeks)
All other solutions for repo archival (via issue on the package repo, issues on a separate repo etc.) seem rather clunky.
The only problem that could arise with this design is that a person crates a repo for a package but doesnt push to it after the initial commits so there is no package (yet) in the repos and it gets archived. This should be an edge case though.https://gitlab.archlinux.org/archlinux/gluebuddy/-/issues/17[FEATURE] disable signed commit requirement for new repos2024-03-21T17:20:46ZChristian Heusel[FEATURE] disable signed commit requirement for new reposWhen importing new packages from the AUR they already bring a git history for which requiring each commit to be signed is not really of much use.
Disable the signed push requirement for new repos until the first tag is set.When importing new packages from the AUR they already bring a git history for which requiring each commit to be signed is not really of much use.
Disable the signed push requirement for new repos until the first tag is set.https://gitlab.archlinux.org/archlinux/gluebuddy/-/issues/16Integration tests2024-02-18T10:28:05ZJelle van der WaaIntegration testsWe would like to have some form of integration tests, the services we depend on are:
* keycloak
* GitLab (query repos)
* archweb (soon => archive feature)
* mailman (soon => automatic onboarding)
## Keycloak
We can run a container eas...We would like to have some form of integration tests, the services we depend on are:
* keycloak
* GitLab (query repos)
* archweb (soon => archive feature)
* mailman (soon => automatic onboarding)
## Keycloak
We can run a container easily enough with a pre-created realm settings which can be auto-imported
## Archweb
We rely in a single http endpoint in the future for archiving
## Mailman
Either mock two endpoints or look if we can run the [container images](https://github.com/maxking/docker-mailman)
@dvzrv used rstest and podman-api in the past.https://gitlab.archlinux.org/archlinux/gluebuddy/-/issues/15[Feature]: automatic onboard to Gitlab teams based on keycloak groups2023-10-23T14:59:26ZLeonidas Spyropoulos[Feature]: automatic onboard to Gitlab teams based on keycloak groupsManaging the teams in Gitlab should be driven from Keycloak. Currently if you want to add a main key holder to the keyringctl project you have to join as admin in the gitlab and adjust the team to add the user. This should be driven from...Managing the teams in Gitlab should be driven from Keycloak. Currently if you want to add a main key holder to the keyringctl project you have to join as admin in the gitlab and adjust the team to add the user. This should be driven from gluebuddy Groups instead.
- Create a new group for Each Team we would like to manage
- Adjust the gluebuddy to add users to Teams in Gitlab and maintain themhttps://gitlab.archlinux.org/archlinux/gluebuddy/-/issues/5Create GitLab subgroup for every "role"2023-10-23T14:39:33ZKristian KlausenCreate GitLab subgroup for every "role"By creating a [Subgroup](https://docs.gitlab.com/ee/user/group/subgroups/) we can assign a issue to ex: all the forums mods or wiki admins or give everyone in X group access to Y project.By creating a [Subgroup](https://docs.gitlab.com/ee/user/group/subgroups/) we can assign a issue to ex: all the forums mods or wiki admins or give everyone in X group access to Y project.https://gitlab.archlinux.org/archlinux/gluebuddy/-/issues/14Handle gitlab admin on/off boarding2023-10-20T22:05:04ZKristian KlausenHandle gitlab admin on/off boardingOn/off boarding DevOps as admin in GitLab is currently [handled by GitLab on login](https://gitlab.archlinux.org/archlinux/infrastructure/-/blob/0a952609be845b989eb958257555ab7ec063667e/roles/gitlab/tasks/main.yml#L81). This may not be t...On/off boarding DevOps as admin in GitLab is currently [handled by GitLab on login](https://gitlab.archlinux.org/archlinux/infrastructure/-/blob/0a952609be845b989eb958257555ab7ec063667e/roles/gitlab/tasks/main.yml#L81). This may not be the best approach, as gluebuddy should handle it .https://gitlab.archlinux.org/archlinux/gluebuddy/-/issues/11make sure to not include none archlinux group membership2023-04-12T16:39:19ZLevente Polyakanthraxx@archlinux.orgmake sure to not include none archlinux group membershipCheck and make sure via gluebuddy that:
- [ ] no project contains group members outside of archlinux/teams
- [ ] no group contains group members outside of archlinux/teamsCheck and make sure via gluebuddy that:
- [ ] no project contains group members outside of archlinux/teams
- [ ] no group contains group members outside of archlinux/teamshttps://gitlab.archlinux.org/archlinux/gluebuddy/-/issues/4Use gluebuddy to onboard Staff to mailinglists with the mailman REST API2023-03-26T11:29:42ZJelle van der WaaUse gluebuddy to onboard Staff to mailinglists with the mailman REST APIMailman 3 once deployed has a REST API which in theory should allow us to onboard/offboard staff automatically. The mailman REST API is documented [here](https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/rest.htm...Mailman 3 once deployed has a REST API which in theory should allow us to onboard/offboard staff automatically. The mailman REST API is documented [here](https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/rest.html#rest-api-documentation).
For membership https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/rest/docs/membership.htmlhttps://gitlab.archlinux.org/archlinux/gluebuddy/-/issues/6Add subcomment to show missing users not on gitlab2021-12-05T11:25:23ZJelle van der WaaAdd subcomment to show missing users not on gitlabNow shown as warning in the log
```
[2021-12-05T11:19:53Z WARN gluebuddy::components::gitlab::gitlab] Failed to query GitLab user for pid1
```
But maybe we'd rather want to query them directly via a subcommand.Now shown as warning in the log
```
[2021-12-05T11:19:53Z WARN gluebuddy::components::gitlab::gitlab] Failed to query GitLab user for pid1
```
But maybe we'd rather want to query them directly via a subcommand.