785215 - increase signing token expiry time for release repack jobs

Status: RESOLVED FIXED

(Release Engineering :: Release Automation: Other, defect)

Description

[[e-mail] (:bhearsum)]

The maximum signing token right now is 4h. Windows release repack jobs take about 2 hours each right now. Each additional partial version we do adds about 45min to each chunk, which means we're limited to doing 2 extra partials (3 total) right now. This might be mitigated by bug 784848, which will probably speed up repacks on Windows. We should make sure we have the ability to do more than that, which probably means increasing the token expiry time for at least these jobs.

Comment 1

[Rail Aliiev [:rail]]

Attachment: bump max_token_age to 6hrs

TODO:
1) Deploy this change to master1-puppet
2) wait 30 minutes so signing servers get the update via puppet
3) before reloading signing instances, make sure that the change delivered

Comment 2

[[e-mail] (:bhearsum)]

Comment on attachment 654973 [details] [diff] [review]
bump max_token_age to 6hrs

Review of attachment 654973 [details] [diff] [review]:
-----------------------------------------------------------------

Looks fine. I think https://github.com/mozilla/buildbotcustom/blob/master/steps/signing.py#L50 needs to be updated afterwards, too.

Comment 3

[Rail Aliiev [:rail]]

Attachment: buildbotcustom

Comment 4

[Rail Aliiev [:rail]]

Attachment: buildbotcustom

Sorry, wrong patch

Comment 5

[Rail Aliiev [:rail]]

Comment on attachment 654986 [details] [diff] [review]
buildbotcustom

http://hg.mozilla.org/build/buildbotcustom/rev/b15d0c5755e4

Comment 6

[Rail Aliiev [:rail]]

Comment on attachment 654986 [details] [diff] [review]
buildbotcustom

Transplanted to production-0.8: http://hg.mozilla.org/build/buildbotcustom/rev/d8a823c46260