-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
panic when getting pull request info #24
Comments
after reading the code, I found that it's normal to have an empty |
I tried to enable batch mode in the common options, and now have the following:
although I have a
and everything else is working (the controller-build is able to retrieve pull-request informations from github...) |
ok after copying the permissions from the controllerbuild role, I managed to make it work. I'll find the minimum required permissions and add them to #23 |
- adding missing read permissions on environments, which resulted in the following error ``` WARNING: error loading TeamSettings to determine if in GitHub app mode: failed to setup the dev environment for namespace 'jx': environments.jenkins.io is forbidden: User "system:serviceaccount:jx:jenkins-x-slack" cannot create resource "environments" in API group "jenkins.io" in the namespace "jx" ``` - adding missing read permissions on configmaps/serviceaccounts/vault, to be able to read git auth config - fixes jenkins-x-plugins#24 - move the role rules in the chart values, to allow customization of the rules without requiring updates of the chart
found it: it requires serviceaccounts and vault |
with version 0.0.17
after fixing the missing permissions #23 I got the following panic.
It is trying to create a git user, because it failed to retrieve the existing one. for some reason it failed to retrieve the ghOwner at https://github.com/jenkins-x/jx/blob/master/pkg/gits/provider.go#L512
I thought it was a missing permission to read the jx-auth-config configmap, but even after adding this permission it is still failing.
do you have an idea?
thanks
The text was updated successfully, but these errors were encountered: