canmove, Confirmed users
1,635
edits
QA/Automation/Projects/Mozmill Automation/Mozmill CI: Difference between revisions
QA/Automation/Projects/Mozmill Automation/Mozmill CI (view source)
Revision as of 01:58, 9 December 2010
, 9 December 2010→Things needed eventually
| Line 45: | Line 45: | ||
==Things needed eventually== | ==Things needed eventually== | ||
* Queuing mechanism (this will primarily be needed for L10N testing, where all locales land simultaneously and need to be queued on platform) | * Queuing mechanism (this will primarily be needed for L10N testing, where all locales land simultaneously and need to be queued on platform) | ||
** Check out celery (http://celeryproject.org/). You could run it through pulse if you want or have your own dedicated host. Then you could easily throw more slaves to process the jobs and scale. AMO and Pulse use celery. --Christian | |||
* RelEng wants to do this in their infrastructure eventually if at all possible. | * RelEng wants to do this in their infrastructure eventually if at all possible. | ||
** If not possible, we'll need a way to report directly back to RelEng | ** If not possible, we'll need a way to report directly back to RelEng | ||
** Not there yet, though. For now want to run it on our side to make sure of robustness before putting in critical path. | ** Not there yet, though. For now want to run it on our side to make sure of robustness before putting in critical path. | ||