ReleaseEngineering/Applications/Tooltool: Difference between revisions

Line 86: Line 86:
* You need tooltool! https://github.com/mozilla/build-tooltool/blob/master/tooltool.py
* You need tooltool! https://github.com/mozilla/build-tooltool/blob/master/tooltool.py


=== How to request a tooltool upload account ===
=== How to enable a user to run tooltool uploads ===
Request addition to "vpn_tooltooleditors" group, via "Infrastruture & Operations::Infrastructure:LDAP".
First, request addition to "vpn_tooltooleditors" group, via "Infrastruture & Operations::Infrastructure:LDAP".
Once that's done, it's an hour or two for the change to propagate from LDAP to Puppet to the upload servers.
Once that's done, it's an hour or two for the change to propagate from LDAP to Puppet to the upload servers.
They should request an ACK on the bug from someone in release engineering for that.
They should request an ACK on the bug from someone in release engineering for that.
You then need to check the following:
* an upload folder for each visibility level exists for the user
* the email address for the user is correctly configured in the configuration file for the sync script
If this does not mean anything to you, have a look to the section below dedicated to the sync script


== Let's update a bunch of files! ==
== Let's update a bunch of files! ==
Confirmed users
107

edits