Closed
Bug 656286
Opened 14 years ago
Closed 12 years ago
virus scan e-mails from staging are confusing
Categories
(Release Engineering :: Release Automation: Other, defect, P5)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: massimo)
Details
(Whiteboard: [release][automation])
Attachments
(3 files)
548 bytes,
patch
|
bhearsum
:
review-
|
Details | Diff | Splinter Review |
3.55 KB,
patch
|
Details | Diff | Splinter Review | |
3.49 KB,
patch
|
bhearsum
:
review+
|
Details | Diff | Splinter Review |
I did part of staging release today and a AV vendor e-mail went to release@mozilla.com. This is good, but the subject is confusing. In staging/preproduction it would be helpful to tag them the same way we do other release mails: with [staging] or [preprod-release].
Updated•14 years ago
|
Priority: -- → P5
Whiteboard: [release][automation]
Updated•13 years ago
|
Blocks: hg-automation
Reporter | ||
Updated•13 years ago
|
No longer blocks: hg-automation
Reporter | ||
Comment 1•13 years ago
|
||
Mass move of bugs to Release Automation component.
Blocks: hg-automation
Component: Release Engineering → Release Engineering: Automation (Release Automation)
Reporter | ||
Updated•13 years ago
|
No longer blocks: hg-automation
Assignee | ||
Comment 2•12 years ago
|
||
Attachment #669926 -
Flags: review?(bhearsum)
Reporter | ||
Comment 3•12 years ago
|
||
Comment on attachment 669926 [details] [diff] [review]
patch for bug 656286
This looks OK, but let's make sure the behaviour in consistent with similar options in createReleaseMessage by factoring out to getSubject() and getMessageTag():
https://github.com/mozilla/buildbotcustom/blob/master/process/release.py#L164
https://github.com/mozilla/buildbotcustom/blob/master/process/release.py#L205
Attachment #669926 -
Flags: review?(bhearsum) → review-
Assignee | ||
Comment 4•12 years ago
|
||
added getMessageTag()
Attachment #672540 -
Flags: review?(bhearsum)
Reporter | ||
Comment 5•12 years ago
|
||
Comment on attachment 672540 [details] [diff] [review]
added getMessageTag()
Review of attachment 672540 [details] [diff] [review]:
-----------------------------------------------------------------
::: process/release.py
@@ +271,5 @@
> + def getMessageTag():
> + return releaseConfig.get('messagePrefix', '[release] ')
> +
> + def getSubject():
> + subject = getMessageTag() + '%(productName)s %(version)s release'
We should actually drop this, since it's not used everywhere, and put this assignment create in createReleaseAVVendorsMessage. Looks fine otherwise.
Reporter | ||
Comment 6•12 years ago
|
||
Comment on attachment 672540 [details] [diff] [review]
added getMessageTag()
Need the below addressed, removing review.
::: process/release.py
@@ +271,5 @@
> + def getMessageTag():
> + return releaseConfig.get('messagePrefix', '[release] ')
> +
> + def getSubject():
> + subject = getMessageTag() + '%(productName)s %(version)s release'
We should actually drop this, since it's not used everywhere, and put this assignment create in createReleaseAVVendorsMessage. Looks fine otherwise.
Attachment #672540 -
Flags: review?(bhearsum)
Assignee | ||
Comment 7•12 years ago
|
||
resending patch. In the last upload I have sent the wrong one. My fault.
Attachment #673961 -
Flags: review?(bhearsum)
Reporter | ||
Comment 8•12 years ago
|
||
Comment on attachment 673961 [details] [diff] [review]
patch for 656286
Review of attachment 673961 [details] [diff] [review]:
-----------------------------------------------------------------
Looks good now, thanks! I landed this on the default branch.
Attachment #673961 -
Flags: review?(bhearsum) → review+
Reporter | ||
Updated•12 years ago
|
Assignee: nobody → mgervasini
Comment 9•12 years ago
|
||
In production
Reporter | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•