gitlab_bots: Add bot token for buildbtw

Signed-off-by: Christian Heusel christian@heusel.eu

requested review from @raffomania

requested review from @svenstaro and @anthraxx

gluebuddy[325394]: -gitlab_member_access {
gluebuddy[325394]: -        namespace    = archlinux/buildbtw
gluebuddy[325394]: -        username     = project_84422_bot_97861d9e46abb5faf685117cb3d0f685
gluebuddy[325394]: -        access_level = developer
gluebuddy[325394]: -}
gluebuddy[325394]: thread 'main' panicked at src/components/gitlab/core.rs:895:18:
gluebuddy[325394]: called `Result::unwrap()` on an `Err` value: Gitlab { msg: "403 Forbidden" }
gluebuddy[325394]: note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
systemd[1]: gluebuddy.service: Main process exited, code=exited, status=101/n/a
systemd[1]: gluebuddy.service: Failed with result 'exit-code'.
systemd[1]: Failed to start gluebuddy service.

added statusdeployed label

added 3 commits

• 41fa4e51...8dec9f5e - 2 commits from branch master
• 3df3b3ec - gitlab_bots: Add bot token for buildbtw

Compare with previous version

@svenstaro @anthraxx I can't figure out why we need a bot token for the archlinux/buildbtw namespace. We have a token for the packaging-buildbtw-dev group, but that's not the one in this MR. Do you know why that token exists and why we still need it?

The buildbtw server deployment doesn't need a token as the container is publicly accessible.

Uhhhh I think archlinux/buildbtw was created in error as I actually wanted to create it for the packaging-buildbtw-dev group.

closed