I have never been able to find any real documentation about this. In DevOps, the description of the advancedquery permission is:
It is an special permission controlling who can run advanced queries (cm query command, issuing plain SQL queries towards the database schema). By default it is not granted to anyone.
And there’s this blog mention:
And this Unity page which is just he cm query help:
https://docs.unity.com/ugs/en-us/manual/devops/manual/uvcs-cli/query
It has a few examples, but is far from thorough. It’d probably help a lot if there was a database schema somewhere. If I was using an on-premises server, I could just open it and look. But this is impossible with cloud.
Even better would be an annotated schema, pointing out which tables/views contain what information, and what the columns mean.
I’m afraid that the “cm query” command is internal and it’s not publicly documented. I can see that this blog post is quite old (when Plastic was using SQL-based databases instead of file based: Jet).
It was announced as a public facing feature there, though.
Does advancedquery permissions cover anything else? I’m trying to figure this out as we had a jenkins job that broken when that permission was denied. The engineer is out so I can’t be certain, but I’m pretty sure they don’t even know about cm query, much less use it.
Let me check with the team. This blog post is from 2007 and at some point it was decided to keep this command for internal use.
The “advancedquery” permissions are related to the “cm query” command but it’s not related to any command run by the Jenkins plugin. If we can help with the Jenkins plugin issue, please open a new thread/ticket with the details. The Jenkins plugin internally uses “cm” so you may need to enable the “cm” logs: Plastic SCM - Technical article - Enabling logging
I should clarify that we’re not using any jenkins plugin AFAIK. But I’ll have to double-check on that when the engineer is back.
What I can say is that our job broke when I reorganized our permission setup. But as soon as I added just that permission, it was working again. We can try a more targeted test when the engineer is back.
Oh, sorry I misunderstood you! Please let us know the details of your environment when your engineer is back. I would like to understand how the “advancedquery” permission is relevant in your setup.