Closed Bug 711673 Opened 13 years ago Closed 12 years ago

x86 builds not being signed

Categories

(Release Engineering :: General, defect, P1)

Product:
Release Engineering
Component:
General
Platform:
x86_64
Windows 7
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: bbondy, Unassigned)

Details

The x86 builds done here are not being signed:
http://ftp.mozilla.org/pub/mozilla.org/firefox/try-builds/bbondy@mozilla.com-f59703783c85/try-win32/

We would like to land bug 481815 tonight but I'm not sure if this is a common problem across all machines or just this one specific builder.
Note: unlike the previous x64 builds, both the installer and the files inside are not signed.
Recent tbox m-c builds are signed and the latest try builds are not. This might be specific to try.
If someone from RelEng can confirm Comment 2 then we can probably land with tests for the service disabled.
signing is only enabled on m-c, m-a, oak and elm
oh ok, I thought the bins were signed with the dep/try keys.
Can it be enabled or was it decided to dangerous to do so? Do the try have the registry key and if not is there anything special about a try server where we could disable the tests there?
I think we will break everyone's try builds if we push.  Is there any way that we can detect this or is there any way that you can enable the same signing as Elm for Try builds and other similar builds (mozilla-inbound) etc?
yes, it can be enabled for try and other branches, but what's going to happen for developers doing local builds and tests?
We are disabling the tests when the registry key doesn't exist for now. We are also adding a check for whether the binary is signed and if not it disabled the test for now.
Component: Release Engineering → Release Engineering: Automation
QA Contact: release → catlee
Not an issue anymore, we sign all the Windows builds now.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
Component: General Automation → General
You need to log in before you can comment on or make changes to this bug.