Problem
Users who have admin access to a Bitbucket Data Center repository through a project group (not individually assigned) cannot trigger builds via /test comments if the PaC technical user is NOT licensed . The error in the PAC controller logs is:
unable to verify event authorization: No message available
Users must be individually added to the project or repository to trigger builds, which defeats the purpose of group-based access management.
Root Cause
The vendored go-scm library uses a Bitbucket API endpoint (/rest/api/1.0/admin/groups/more-members) to resolve group membership. This endpoint requires a LICENSED_USER, so your PAC technical user must be a licensed user.
Tracked upstream: jenkins-x/go-scm#521
Workaround
Add users individually to the project or repository permissions (not through a group).
EDIT: Corrected LICENSED_USER info
Problem
Users who have admin access to a Bitbucket Data Center repository through a project group (not individually assigned) cannot trigger builds via
/testcomments if the PaC technical user is NOT licensed . The error in the PAC controller logs is:Users must be individually added to the project or repository to trigger builds, which defeats the purpose of group-based access management.
Root Cause
The vendored
go-scmlibrary uses a Bitbucket API endpoint (/rest/api/1.0/admin/groups/more-members) to resolve group membership. This endpoint requires a LICENSED_USER, so your PAC technical user must be a licensed user.Tracked upstream: jenkins-x/go-scm#521
Workaround
Add users individually to the project or repository permissions (not through a group).
EDIT: Corrected LICENSED_USER info