ReleaseEngineering/Queue directories

From MozillaWiki
< ReleaseEngineering
Revision as of 16:02, 16 September 2011 by Catlee (talk | contribs) (Created page with "Our buildbot masters make use of several queuedirs to perform out of process tasks such as pushing events to pulse or uploading logs. == queuedirs == A queuedir is a simple dire...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Our buildbot masters make use of several queuedirs to perform out of process tasks such as pushing events to pulse or uploading logs.

queuedirs

A queuedir is a simple directory structure on disk where individual jobs are stored in files. The files are moved between directories depending on what state they're in.

  • tmp: write out new job files here before moving into new.
  • new: when job files are moved into here, the queue processors will pick them up and move them into cur to indicate they're currently being processed.
  • cur: jobs currently in progress are here.
  • logs: output and debugging information for current and finished jobs are here. Logs older than 5 minutes get deleted.
  • dead: failed jobs go here. this is bad.

We currently have two queuedirs: /dev/shm/queue/commands, and /dev/shm/queue/pulse

processors

We currently have two processors: command_runner.py and pulse_publisher.py. These are run as services, start on boot, and are managed by puppet. They both run out of a virtualenv in /builds/buildbot/queue.

We have nagios checks in place to ensure that the queue processors are running, and that there are no dead jobs. NB not finished yet - bug 685980

implementation

http://hg.mozilla.org/build/tools/file/739018ba9ff1/lib/python/buildtools/queuedir.py

http://hg.mozilla.org/build/tools/file/739018ba9ff1/buildbot-helpers/command_runner.py

http://hg.mozilla.org/build/tools/file/739018ba9ff1/buildbot-helpers/pulse_publisher.py

Retrieved from "https://wiki.mozilla.org/index.php?title=ReleaseEngineering/Queue_directories&oldid=348890"