@vadim-k_6062 @jjones Seems like this was fixed in the latest update. I just upgraded and now I can create server roles.

@jjones I have just encountered the same error. I just installed Otter (on the same machine as Buildmaster), added a server and then try to create a role which fails with the above error. It doesn't matter whether I select a server when creating the role or not. I tried enabling debug logging but that didn't provide any more information.

Thanks,
Frederik

@jjones It looks like it is working from within the plan editor - I get autocomplete suggestions for groups and projects now.
I then tried the resource credentials again, and it doesn't work there. Also, I just spotted that when I have added a group to the credential, I cannot remove it again. When clearing the field and saving it simply puts in the old value again.

[Update] I played a bit with it, and now git pulls are working and I am in process of building stuff, so yay!
It does however still seem like there is a bug in the credential editor page with the autocompletion of group/project, and also where you cannot delete a group once it is set.

@jjones Yes I am using a self-hosted Gitlab CE. I have just tried with a gitlab.com account but I get the same error there. Looking through the source code for the gitlab extension, it looks like it never gets the groupname or username parameter to use in the CoalesceString function.
https://github.com/Inedo/inedox-git/blob/master/Git/GitLab.InedoExtension/SuggestionProviders/CredentialsGroupNameSuggestionProvider.cs#L17

I tried filling the group name manually in the configuration for the credential to see if the project would then autocomplete, but it still throws the same exception as in the first post here.

Thanks,
Frederik

Hi Jason,

Sorry fro the late reply - haven't had time to deal with it until now.

I just tried installing a brand new server today with a brand new Buildmaster install and I still have the same issue.

Running wireshark on the server I don't see any traffic to the gitlab server at all. Checking the database on the buildmaster server, the credential entry looks fine to me in there as well.
This is the Configuration_Xml entry from the database:

<Inedo.Extensions.GitLab.Credentials.GitLabCredentials Assembly="GitLab"><Properties ApiUrl="https://my-gitlab-server/api" UserName="user"><Password Encrypted="aes128">aesencryptedpasswordhere</Password></Properties></Inedo.Extensions.GitLab.Credentials.GitLabCredentials>