The scheduled run of the wiki workflow (9 passages, no note) of the configuration repository (note: Configuration repository), next to the runs a push or a dispatch (6 passages, no note) triggers: every morning the build pipeline reads the two content repositories (note: Knowledge repository) at their main ref (4 passages, no note) and publishes the site (3 passages, no note) again, so that the freshness (8 passages, no note) entry of the home page and the stale-source (note: Stale source) findings (note: Finding) follow the calendar even when nothing was pushed, and so that a dispatch lost for want of a token is caught up within a day.
Nightly build
Properties5
- Application
- Concordance command line
- Domain
- Ingestion
- Status
- valid
- Schedule
- every day at 05:00 UTC
- Window
- a few minutes; the clones are refreshed from the pipeline cache
5 declared keys. The rest of the file is free text.
See the neighbourhood map6 pages6Neighbourhood mapNightly build
Neighbourhood map Nightly build
Distance1 hop
15 neighbours in total, more than the map shows.
The 6 neighbourstextual equivalent
- ModelBusiness objectaccesses1
- BuildBusiness objectaccesses1
- SourceBusiness objectaccesses1
- FindingBusiness objectaccesses1
- Build pipelineProcessis related to1
- HomeScreenis related to1
Six neighbours at most, always named. Beyond that the map teaches nothing: the list takes over.