Closed Bug 707941 Opened 14 years ago Closed 14 years ago

Improve token generation step

Categories

(Release Engineering :: General, defect, P2)

x86_64
Linux
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: rail, Assigned: rail)

References

Details

(Whiteboard: [automation])

Attachments

(1 file)

* shuffle servers * add more logging To be tested.
Comment on attachment 579303 [details] [diff] [review] token generation improvements example output on failure: Slave: linux-ix-slave05 IP: 10.250.50.212 Duration: 7200 URI: https://signing2.build.scl1.mozilla.com:9010/token <buildbotcustom.steps.signing.SigningServerAuthenication instance at 0x10147fc8>: token generation failed, error message: 401 Authorization Required URI: https://signing2.build.scl1.mozilla.com:9010/token <buildbotcustom.steps.signing.SigningServerAuthenication instance at 0x10147fc8>: token generation failed, error message: 401 Authorization Required URI: https://signing2.build.scl1.mozilla.com:9010/token <buildbotcustom.steps.signing.SigningServerAuthenication instance at 0x10147fc8>: token generation failed, error message: 401 Authorization Required
Attachment #579303 - Flags: review?(catlee)
Attachment #579303 - Flags: review?(catlee) → review+
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: