Continuous integration/Documentation generation/fr

La documentation est générée et publiée automatiquement sur doc.wikimedia.org. For increased flexibility and security, the static sites are generated inside WMCS instances. The docs are then fetched from the instance to the CI production host, and pushed with rsync to the documentation host ( as of March 2022). Cette page documente le flux de travail, une partie de la mise en œuvre technique et la définition d'un nouvel emploi.

Zuul
Our reacts on two kinds of Gerrit events which are matched by two different pipelines:

could cover the changes being merged since the target branch is updated, but the event is not associated with a Gerrit change number which prevents us from reporting back to the Gerrit interface. We thus use:


 * pipeline to report back in Gerrit so the user knows the documentation has been generated
 * pipeline which solely handles references updates matching.

In both cases, ( or  ) we trigger the same job to generate the documentation for any branch or tag. We thus need to namespace the documentation under https://doc.wikimedia.org based on the branch name or the tag name. The information is carried differently between events and the reference is slightly different between branch updates and tags. The conversion logic is carried by a which is applied to all the publish jobs. It injects to the Gearman function (and thus the Jenkins job environment) a variable  which represents the version.

Example:


 * A change merged on  branch:
 * updated:

Reference:

We can thus reuse that  parameter to easily namespace the jobs per version. As an example, https://doc.wikimedia.org/mediawiki-core/ has documentation for both release branches (https://doc.wikimedia.org/mediawiki-core/REL1_37/) and tags (https://doc.wikimedia.org/mediawiki-core/1.36.2).

Jenkins job builder definitions
Most of the logic is defined in Jenkins Job Builder  configuration file.

In a job definition, a  defines what steps to execute. We provide a builder macro called  that takes care of transferring the generated files to the web server of https://doc.wikimedia.org/. It takes two parameters:


 * 1)   Directory holding documentation files relative to workspace (without trailing slash)
 * 2)   Directory under https://doc.wikimedia.org/.

Example job definition:

This will invoke the build scripts (doxygen and jsduck) and publish their results (respectively in doc/html and docs) to https://doc.wikimedia.org/myproject/.

To namespace the documentation based on project version, use the Zuul-generated  (derived from branch or tag name). Simply insert it in the  parameter. You will need to invoke the builder assert-env-doc_subpath. Example for MediaWiki (mediawiki-core-doxygen-publish job):

This publishes the documentation at https://doc.wikimedia.org/mediawiki-core/master/php/, and also publishes release branch documentation such as https://doc.wikimedia.org/mediawiki-core/REL1_34/php/, and tagged releases such as https://doc.wikimedia.org/mediawiki-core/1.34.0/php/

Architecture
For architecture overview and runbooks, see Doc.wikimedia.org