Closed
Bug 626405
Opened 14 years ago
Closed 14 years ago
fake out clamdscan on staging-stage/preproduction-stage
Categories
(Release Engineering :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
References
Details
Attachments
(1 file)
462 bytes,
patch
|
rail
:
review+
bhearsum
:
checked-in+
|
Details | Diff | Splinter Review |
During a staging release run I found that the pre_push_checks builder fails because clamdscan isn't installed. There's no real point in running a virus scan in either of these places, and they would be awfully slow. Rail suggested that we fake it out with a shell script, which seems like a good idea.
Assignee | ||
Comment 1•14 years ago
|
||
I haven't been able to test this because staging-stage isn't set-up w/ Puppet.
Attachment #504465 -
Flags: review?(rail)
Comment 2•14 years ago
|
||
Comment on attachment 504465 [details] [diff] [review]
sync fake clamd
Looks fine to me.
> I haven't been able to test this because staging-stage isn't set-up w/ Puppet.
Will see it in preproduction. :)
Attachment #504465 -
Flags: review?(rail) → review+
Assignee | ||
Comment 3•14 years ago
|
||
Comment on attachment 504465 [details] [diff] [review]
sync fake clamd
changeset: 263:b17d294d963a
Attachment #504465 -
Flags: checked-in+
Assignee | ||
Comment 4•14 years ago
|
||
I had to land a bustage fix (s/contents/content/), because I misread the docs. preproduction-stage picked it up after that.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•12 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•