CI/CD direction

Basic references

• Generic info: Use CI/CD to build your application
• Debian-specific info: Salsa CI pipeline

CI/CD tasks

• !31 (closed) -- draft

  • Spell check of English source with codespell
  • Syntax check of English source with build

• !39 (merged) -- draft

  • Spell check of asciidoc source with ispell
  • Syntax check of non-English PO with custom script checking as XML
  • cd asciidoc; make to test asciidoc-level errors
  • make html css to test xml level errors
  • No automation yet

• Optimized CI/CD invocation -- !33

  • How frequent should full package build happen --> only for -2, -3, ... releases.
  • How to ensure pre-merge test. --> Not by package build but via specific tests which require no upstream tarball. (Or should we move to native package?)

CI/CD friendly build

• easy CJK PDF build on/off -- done !34 (merged)
• easier identification of failed language (Makefile? "make -j1"?)

FYI: Web page publication infrastructure

Currently, debmake-doc is deployed as:

• its unstable package hits repository
• https://salsa.debian.org/webmaster-team/cron pick it up
• Package contents are used to generate www.debian.org pages with some URL tweaking.