summaryrefslogtreecommitdiff
path: root/doc/invocations-http-server
AgeCommit message (Collapse)Author
39 hoursInvocation server: fix total count of non-cached actionsHEADmasterKlaus Aehlig
While our presentation shows the details of only up to 30 non-cached actions, the count reported in the heading should still be the total count of all non-cached actions. Fix this.
2025-06-18Invocation 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-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-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-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-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-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
2025-05-12Invocation server: explicitly set methodsKlaus Aehlig
While there, sort filter URLs
2025-05-12Invocation server: also for action-artifacts, offer a download linkKlaus Aehlig
2025-05-12Invocation server: increase number of displayed invocations in the overview ↵Sascha Roloff
to 100
2025-05-12Invocation server: cleanup html tagsSascha Roloff
2025-05-09Invocation server: print invocation contextSascha Roloff
2025-05-09Invocation server: use json.dumps to render remote-execution propertiesSascha Roloff
2025-05-09Invocation server: fix config calculationSascha Roloff
2025-05-09Invocation server: split invocation overview information into several linesSascha Roloff
2025-05-09Invocation server: format and spelling fixesSascha Roloff
2025-05-09Invocation server: support filtering by remote-execution propertyKlaus Aehlig
When looking at an invocation, it can be helpful to quickly get all other invocation that coincide with a specific remote-execution property (like the build image). Support this use case by adding appropriate filtering and links.
2025-05-07Invocation server: also show information related to the used remoteKlaus Aehlig
2025-05-07Invocation server: fix access to configuration in overview listKlaus Aehlig
2025-05-07Invocation server: also mention the number of artifactsKlaus Aehlig
... in the summary, so that the user knows what to expect when looking into the details-environment.
2025-05-07Invocation server: include action countKlaus Aehlig
2025-05-06invocation server: actions are also meaningful for exit code 0Klaus Aehlig
With the introduction of new exit codes, the presentation of an invocation was changed to refrain from showing actions in abnormal case failure already during analysis phase. However ca8fd841736ca65fa4292887052c78243512962a did not include the case of a successful build into the cases of normal circumstances. Fix this.
2025-05-06Invocation server: present new exit codes and analysis errosKlaus Aehlig
2025-04-25Invocation server: also present the artifacts of an invocationKlaus Aehlig
... if available. This can be useful, when presenting builds that are mainly there to have artifacts available for manual use.
2025-04-25Invocation http server: for tree entries offer direct download linksKlaus Aehlig
When showing a tree, we have for each entry already a designated file name. Use this, to offer direct dowload links for blobs with the intended name.
2025-04-25Invocation http server: indicate incomplete dataKlaus Aehlig
With just-mr supporting a custom prefix to be shown at the beginning of a logged invocation, users might be pointed to the web server very early. Therefore, properly indicate if the invocation data is not yet complete.