I was using drone 0.8 for a while, and have recently moved to 1.0. The
DRON_ADMIN does not work anymore, so I found this topic and tried the
DRONE_USER_CREATE to give my account (suppose my account name is “abc”) admin permissions:
However, this does not work.
docker user update abc --admin
Sets the flag
admin=true when I invoke
docker user info abc, however, there is no admin panel in the UI still.
Also, I don’t understand, how would it work, for the authentication using
Also, in my opinion, the drone permissions, if we are using oauth source, should be taken from the ouath source: if I am an administrator of gitea instance and we authenticate through gitea, the drone should use the same set of administrator accounts as gitea does.
But going back to the original topic, how do I set my existing account to be an administrator of drone?
This parameter works fine for me and we have not received any reports of this being a problem for anyone else. I would encourage you to enable debug logging and collect the log output. For example I see this:
"msg": "bootstrap: updating account",
"msg": "bootstrap: account already up-to-date",
When I login to Drone in the browser I am able to verify my administrative role by change the browser URL to
/api/user. I then see something like this:
As an aside I noticed your example commands are incorrect:
-docker user update abc --admin
+drone user update --admin abc
If you continue to experience issues I highly encourage inspecting the source code. You can find the bootstrap code and unit tests (with 100% coverage) in these files:
I also see the
"admin": true when I go to the
/api/user address, but I don’t see any administration panel. Maybe I just don’t see it. Could you please senda screenshot with it?
there is no administration panel.
Okay, how do I set a project-specific build timeout then? I have read recently somewhere in the internet that you could do it only in the graphics user interface, not via docker cli or environment variables.
My build on my poor VDS takes more than a hour and drone cancels it automatically.
You can the repository settings screen and set the timeout, and click save. The timeout field is visible to any system admin. You can also use the
drone repo update command to set the timeout.
Oh my god, I can’t believe it has always been there Thank you!