Page History

...

At 0830 UTC, the build/mkupdates/run_nightly script is run from svn trunk. This runs the script build/mkupdates/listpromotable, which queries the rule-QA web app for the previous day's rule accuracy figures, and determines which rules from the rules source dirs (rulesrc/core and rulesrc/sandbox/*) are to be promoted to the active ruleset, as described in RuleLifeCycle.

Promotion Criteria

Wiki MarkupYou can see the previous day's accuracy figures \[http://ruleqa.spamassassin.org/?daterev=last-night at this URL\]. Promotable rules show up in dark text on the [RuleQaApp], non-promoted-by-default rules show up in light grey text.

The promotion criteria are detailed on some other wiki page, RulesProjPromotion perhaps? (TODO).

...

• "tflags nopublish" rules are never published
• rules with a T_ prefix to their names are never published - if you're getting these in a normal installation, you should probably report a bug.
• rules do not currently need rules without an explicit "tflags publish" line are never publishedto be published but the existence of either "tflags publish" or "tflags nopublish" is recommended to make it clear that the rule is intended to be published if it meets the promotion criteria.
• "tflags net", "userconf" or "learn" rules are always published
• rules that fail lint – if that can be attributed to the rule! – are not published
• rules that require a plugin that build/mkupdates/listpromotable thinks is not part of the default plugin set, are not published
  

...

30 8 * * * bash /home/updatesd/svn/spamassassin/build/mkupdates/run_nightly > /var/www/buildbot.spamassassin.org/updatesd/mkupdates.txt 2>&1
50 8 * * * bash /home/updatesd/svn/spamassassin/build/mkupdates/run_part2 > /var/www/buildbot.spamassassin.org/updatesd/mkupdatespt2.txt 2>&1

SA-Update Mirrors

sa-update uses the MIRRORED.BY file to provide distributed update capabilities. The setup for a mirror is described in SaUpdateMirrorSetup.

The Other End

See RuleUpdates for details on running "sa-update".