(Some?) nightly uploads newly on Taskcluter are broken

[SimonSapin]

#23304 has landed, but unfortunately our PR testing does not exercise at all the CI code that runs for daily tasks, such as Nightly builds upload. There was multiples issues:

• The daily decision task did not have scopes for the new entries in the Secrets API #23304 (comment)
• These scopes were not forwarded to the new tasks #23316
• taskcluster-proxy was not installed on macOS workers #23319
• taskcluster-proxy was not installed in the AMI for Windows workers #23327
• The macOS x64: Nightly build and upload goes over its two hours time budget (though after successfully uploading a Nightly) because it also runs WPT tests (to update expectations).
  • Let’s increase the timeout or split it into two tasks #23327
• ./mach upload-nightly maven looks for both ARMv7 and x86 builds, but they are built in separate tasks #23327
• The mac build machines are missing jq which the WPT sync job uses #23338
• This line should reference SECRET_RESPONSE instead of OPEN_PR_RESPONSE #23338
• WPT job fails to push the git branch, probably due to an incorrect secret #23346
• Other issues?

After changes land in master, they can be tested by clicking the Trigger button on https://tools.taskcluster.net/hooks/project-servo/daily. Testing a different branch is possible by changing the GIT_REF env variable. Don’t forget to revert such changes after triggering the test run.

[SimonSapin]

Windows Nightly build and upload task https://tools.taskcluster.net/groups/GLEPxdzkRNmILrCbKsk_NQ/tasks/IY-N1eQKR56kuWFLq2HbGA/runs/0 ran into its 60 minutes timeout.

[jdm]

All nightly jobs are chugging along now.