QA/Test Automation/2010-12-01: Difference between revisions

QA/Test Automation/2010-12-01 (view source)

Revision as of 19:00, 1 December 2010

157 bytes added , 1 December 2010

→‎Triggered software updates (Geo)

Gmealer

canmove, Confirmed users

2,041

edits

@@ Line 36: / Line 36: @@
 ==Triggered software updates (Geo)==
 * Proposed structure:
-** Trigger comes from somewhere on build landing, contains current build id
+*# Trigger comes from somewhere on build landing, contains current build id
-*** Open question: Pulse vs. Email from Releng? In discussions now on both sides.
+*#* Open question: Pulse vs. Email from Releng? In discussions now on both sides.
-** Polling script on VM catches trigger
+*# Trigger polling script on VM catches trigger
-** Current build downloaded and saved off for next trigger.
+*# Current build downloaded and saved off for next trigger.
-** Queuing mechanism (directory full of semaphores or a flat file) for queuing landed builds
+*# Trigger polling script adds build to queue (directory full of semaphores or a flat file) for processing.
-*** May not be needed for initial PoC as builds don't typically come frequently enough to queue. This would be an edge case handler.
+*#* May not be needed for initial PoC as builds don't typically come frequently enough to queue. This would be an edge case handler.
-** Build saved off from last trigger will be updated and compared to expected build id.
+*# Queue polling script pulls the job off the queue, does two things:
+*## Downloads current build and saves it off for next trigger.
+*## Build saved off from last trigger will be updated and compared to expected build id.
 ** Initial reporting to brasstacks, possiblly email on failures
 ** Initial version for trunk, en_US only. Still targeting multi-platform.