Closed
Bug 688669
Opened 14 years ago
Closed 13 years ago
Send the "all signed builds available" to r-d
Categories
(Release Engineering :: General, defect, P5)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: lsblakk, Unassigned)
References
Details
(Whiteboard: [simple][automation][signing])
No description provided.
Comment 1•14 years ago
|
||
After signature verification too?
| Reporter | ||
Updated•14 years ago
|
Summary: Don't send the "all signed builds available" email for Fennec until after signed builds are uploaded properly to ftp → Don't send the "all signed builds available" email for Fennec until after signed builds are uploaded properly to ftp and sigs have been verified
Comment 2•14 years ago
|
||
If we do signature verification as a part of signing process and put an extra file to FTP to be watched by automation (like win32 signing log), we'll just need to modify the URL being polled.
Comment 3•14 years ago
|
||
I'm going to verify the passphrases and signatures before uploading in bug 608432.
We can do the same in signing-on-demand in bug 705807.
If I add the r-d email to the end of the mozharness script, I can dupe this bug to 608432. Otherwise we may be in the middle of creating snippets and uploading partner signed bits when the email is sent.
Comment 4•14 years ago
|
||
I suppose I'll follow Rail's suggestion and upload a final dummy file at the end of the mozharness script. In signing-on-demand, it'll be when the final repack job has finished.
Depends on: 608432
Comment 5•14 years ago
|
||
The mozharness signing script verifies the signature, so no worries there.
We get the "all signed builds available" email sent to release@, but nothing to r-d@.
We should probably go back to sending it to r-d@ until we get android signing on demand.
Morphing this bug.
Summary: Don't send the "all signed builds available" email for Fennec until after signed builds are uploaded properly to ftp and sigs have been verified → Send the "all signed builds available" to r-d
Updated•13 years ago
|
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
| Assignee | ||
Updated•13 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•