Saket configuration

This page summarizes how to add, remove or change build and test configuration from the nightly builds using SAKET.

Files and directories.

• /afs/cern.ch/project/gd/dms/saket
  • SAKET- * .sh These are bash scripts that are executed every night through acrontab. The service accounts saket and saketemi are the ones that have them set.
  • python Cheetah is used to generate the HTML reports and mails, but it is not installed in the AFS machines, so it is placed here.
  • etics The ETICS client is installed under this directory. SAKET does not need etics-workspace-setup.py to be executed.
  • saket Here is where SAKET itself is installed.
    • cli/
      • saket-agent.py Triggers build and tests. Wait until they finish to summarize everything into a report.
      • saket-build.py Triggers only the builds. It does not wait or generate any kind of report.
      • saket-test.py Triggers only the tests. It does not wait or generate any kind of report.
      • saket-regenerate.py Regenerates the index page using the stored reports.
      • Config The configuration files are here.

Configuration files

The configuration files are Python scripts themselves. What have to be built and tested (and how) is defined inside the dictionary "PROJECTS", where everything is organized as key/value pairs, following a tree-like schema. Configuration parameters are inherited. This means, if a build sub-set does not specify the project configuration, it will use the one defined in upper levels.

How to run...

SAKET has its own "User Guide" that explains briefly the command usage. Hopefully, it should be clear enough.

-- AlejandroAlvarez - 15-Feb-2012