summaryrefslogtreecommitdiff
path: root/doc
AgeCommit message (Collapse)Author
5 daysdoc: Fix various typos and inconsistenciesPaul Cristian Sarbu
5 daysDocumentation: fix typosKlaus Aehlig
7 daysfuture-designs: Remove entries for debug fission and just-lockPaul Cristian Sarbu
...as these features have already been implemented and appropriately documented.
9 daysTutorial: also point to the computed root used in the justbuild repoKlaus Aehlig
9 daysDocumentation: fix default for "main" in repository-configKlaus Aehlig
9 daysDocumentation: fix some typosKlaus Aehlig
14 daysInvocation server: directly show only artifactKlaus Aehlig
When presenting a build, the output artifacts are hidden behind a "details" environment to not overload the user with long list of, e.g., test results (especially if generated by a test matrix). If, however, only a single artifact is built, there is no reason to hide it; so simply show it.
2025-06-13Extend invocation-logging tutorialKlaus Aehlig
Environment variables can be used to provide some context, why a particular invocation was run, and hence allow additional sharding. Also, remind that setting up a cronjob for log rotation might me a good idea.
2025-06-12Update documentationMaksim Denisov
2025-06-11Add design document for full GCMaksim Denisov
2025-06-05lint tutorial: hint on the discovered but not processed actionsKlaus Aehlig
Linting is a natural example where actions are discovered that are not neded for the artifact that is requested to be built. Use this opportunity to explain the difference between discovering an action and processing it.
2025-06-05tutorial lint: Update example outputPaul Cristian Sarbu
2025-06-03Invocation server: also show counts in headingsKlaus Aehlig
Often, the simple number, e.g., for failed actions can already give valuable information. For example, when investigating flakiness, the count of failed actions already gives a hint whether a change increased or decreased flakiness which can be valuable before even investigating if the nature of the failure has changed. As we have that information available and an additional number in a heading does not clutter the page too much, let's just show it.
2025-05-30Invocation server: add links back to the overview pageKlaus Aehlig
2025-05-30Invocation server: use "build stop time" for build wall-clock timeKlaus Aehlig
As the end of the build can be significantly ahead of the end of the incvocation, a new time stamp was added to the profile. Use this new time stamp in the invocation server when determining the wall-clock time of the build.
2025-05-28Invocation server: also show the build timeKlaus Aehlig
Also show only the build time in the invocations overview, as only for the build phase detailled timing information will be available in the log of a particular information.
2025-05-23tutorial: Update example outputs in all chaptersPaul Cristian Sarbu
...to match the ones produces by latest binaries and rules.
2025-05-23tutorial computed: Fix source of non-reproducibility in example scriptPaul Cristian Sarbu
While there, update outputs to what is expected with current released binaries and rules. Co-authored-by: Klaus Aehlig <klaus.aehlig@huawei.com>
2025-05-23tutorial: Add DWP and ADD_DEBUGFLAGSPaul Cristian Sarbu
...to example export targets and defaults.
2025-05-23tutorial debugging: Use ADD_COMPILE_FLAGSPaul Cristian Sarbu
...instead of replacing CFLAGS and CXXFLAGS, thus also fixing a mismatch introduced in c008c07656fff528c80add260397c7c7702aa2a8.
2025-05-23Extend tutorial on cross compiling showing how to use ["test", "matrix"]Klaus Aehlig
2025-05-22invocation server: add presentation of invocation wall-clock timeSascha Roloff
2025-05-21invocation server: fix download linksKlaus Aehlig
... to include only the basename of the requested artifact.
2025-05-20invocation server: add critical-path computationSascha Roloff
2025-05-20invocation server: move show_action macro into separate template fileSascha Roloff
... to allow reuse.
2025-05-20invocation server: move action_data function out of do_get_invocation methodSascha Roloff
... to allow reuse.
2025-05-20invocation server: fix typoSascha Roloff
2025-05-15just-mr: support invocation-specific artifacts-to-build loggingKlaus Aehlig
It is already supported to ask just-mr (via the rc file) to log for each invocation the artifacts that were built. Add a similar option for the artifacts that were to be built, i.e., for dumping the intensional description of the output artifacts. That information can be used, e.g., to compute the critical path.
2025-05-15invocation server: fix isintance statementKlaus Aehlig
2025-05-15Invocation server: add target filterSascha Roloff
2025-05-15Invocation server: add remote-execution address filterSascha Roloff
2025-05-15Invocation server: lexicographically sort filter keysSascha Roloff
2025-05-15Invocation server: print nothing for empty remote-execution propertiesSascha Roloff
2025-05-15Invocation server: print only non-empty dispatch listsSascha Roloff
2025-05-15Invocation server: add missing HTML-escape filters in templatesSascha Roloff
2025-05-15Invocation server: uncollapse first failed actionSascha Roloff
2025-05-15tutorial invocation logging: include --dump-artifactsKlaus Aehlig
A typical invocation logging would also include a value for "--dump-artifacts". Mention this in the tutorial.
2025-05-14tutorial, test: recommend ["test", "suite"] for combining testsKlaus Aehlig
... as this also works together with, e.g., linting. While there, also rerun the examples to get the latest output messages.
2025-05-14Invocation server: make command-line collapsibleSascha Roloff
2025-05-13Invocation server: load more invocations with reduced informationSascha Roloff
2025-05-13Invocation server: adapt styleSascha Roloff
2025-05-13Invocation server: lexicographically sort filter valuesSascha Roloff
2025-05-13Invocation server: include commandline when describing actionsKlaus Aehlig
2025-05-13Invocation server: show actions with console output separatelyKlaus Aehlig
Normally, actions are supposed to work silently, i.e., without writing to stdout/stderr. So, if an action produces console output, it is definitely worth looking at, even for cached actions. Therefore, add a section after the failed actions showing those actions (if not in the previous action). Also, always show duration (if known) and if an action is cached (which can happen for the ones producing console output).
2025-05-13Invocation server: add links to blob references in analysis errorsKlaus Aehlig
When using a serve endpoint, analysis errors my contain a reference to a build failure on serve, shown as 'blob <hash>'. For each such blob reference add a link offering to read this blob.
2025-05-13Invocation server: fix hash patternKlaus Aehlig
Currently the support hashes are SHA-1 (for git hashes), which has 160 bits and SHA-256 which has 256 bits. Therefore, we expect either 40 or 64 hex digits.
2025-05-13Tutorial: Update reference to rules-ccOliver Reiche
2025-05-12Invocation server: add css style fileSascha Roloff
2025-05-12Invocation server: add filter selector to overview pageSascha Roloff
2025-05-12Invocation server: support restricting to not-fully-cached buildsKlaus Aehlig