Age | Commit message (Collapse) | Author | |
---|---|---|---|
2025-05-30 | Invocation server: use "build stop time" for build wall-clock time | Klaus 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-28 | Invocation server: also show the build time | Klaus 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-22 | invocation server: add presentation of invocation wall-clock time | Sascha Roloff | |
2025-05-21 | invocation server: fix download links | Klaus Aehlig | |
... to include only the basename of the requested artifact. | |||
2025-05-20 | invocation server: add critical-path computation | Sascha Roloff | |
2025-05-20 | invocation server: move action_data function out of do_get_invocation method | Sascha Roloff | |
... to allow reuse. | |||
2025-05-15 | invocation server: fix isintance statement | Klaus Aehlig | |
2025-05-15 | Invocation server: add target filter | Sascha Roloff | |
2025-05-15 | Invocation server: add remote-execution address filter | Sascha Roloff | |
2025-05-15 | Invocation server: lexicographically sort filter keys | Sascha Roloff | |
2025-05-15 | Invocation server: print only non-empty dispatch lists | Sascha Roloff | |
2025-05-13 | Invocation server: load more invocations with reduced information | Sascha Roloff | |
2025-05-13 | Invocation server: lexicographically sort filter values | Sascha Roloff | |
2025-05-13 | Invocation server: include commandline when describing actions | Klaus Aehlig | |
2025-05-13 | Invocation server: show actions with console output separately | Klaus 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-13 | Invocation server: add links to blob references in analysis errors | Klaus 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-13 | Invocation server: fix hash pattern | Klaus 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-12 | Invocation server: add css style file | Sascha Roloff | |
2025-05-12 | Invocation server: add filter selector to overview page | Sascha Roloff | |
2025-05-12 | Invocation server: support restricting to not-fully-cached builds | Klaus Aehlig | |
2025-05-12 | Invocation server: explicitly set methods | Klaus Aehlig | |
While there, sort filter URLs | |||
2025-05-12 | Invocation server: increase number of displayed invocations in the overview ↵ | Sascha Roloff | |
to 100 | |||
2025-05-09 | Invocation server: print invocation context | Sascha Roloff | |
2025-05-09 | Invocation server: use json.dumps to render remote-execution properties | Sascha Roloff | |
2025-05-09 | Invocation server: fix config calculation | Sascha Roloff | |
2025-05-09 | Invocation server: support filtering by remote-execution property | Klaus 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-07 | Invocation server: also show information related to the used remote | Klaus Aehlig | |
2025-05-07 | Invocation server: fix access to configuration in overview list | Klaus Aehlig | |
2025-05-07 | Invocation server: also mention the number of artifacts | Klaus Aehlig | |
... in the summary, so that the user knows what to expect when looking into the details-environment. | |||
2025-05-07 | Invocation server: include action count | Klaus Aehlig | |
2025-05-06 | Invocation server: present new exit codes and analysis erros | Klaus Aehlig | |
2025-04-25 | Invocation server: also present the artifacts of an invocation | Klaus Aehlig | |
... if available. This can be useful, when presenting builds that are mainly there to have artifacts available for manual use. | |||
2025-04-25 | Invocation http server: indicate incomplete data | Klaus 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. | |||
2025-04-24 | Invocation server: support download of all blobs | Klaus Aehlig | |
For many text files it is useful to read them directly in the browser. However, many files that are better analysed by machines (like large repository configurations) also come as plain-text files. Therefore, always offer to download a file currently being viewed. Use the URL scheme in such a way that the name to download the file as can be specified; in this way, we are prepared if we decide to also log the artifacts to be built and offer those to be downloaded. | |||
2025-04-23 | Add simple http server allowing to browse an invocation-log directory | Klaus Aehlig | |
Being able to browse through past invocations of the build tool can actually be useful and doing so in the browser is a way many users prefer. Therefore, add a small WSGI application (written in python, using werkzeug and jinja) serving a directory of invocation logs via http. |