| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2025-05-15 | Invocation server: print nothing for empty remote-execution properties | Sascha Roloff | |
| 2025-05-15 | Invocation server: print only non-empty dispatch lists | Sascha Roloff | |
| 2025-05-15 | Invocation server: add missing HTML-escape filters in templates | Sascha Roloff | |
| 2025-05-15 | Invocation server: uncollapse first failed action | Sascha Roloff | |
| 2025-05-15 | tutorial invocation logging: include --dump-artifacts | Klaus Aehlig | |
| A typical invocation logging would also include a value for "--dump-artifacts". Mention this in the tutorial. | |||
| 2025-05-14 | tutorial, test: recommend ["test", "suite"] for combining tests | Klaus Aehlig | |
| ... as this also works together with, e.g., linting. While there, also rerun the examples to get the latest output messages. | |||
| 2025-05-14 | Invocation server: make command-line collapsible | Sascha Roloff | |
| 2025-05-13 | Invocation server: load more invocations with reduced information | Sascha Roloff | |
| 2025-05-13 | Invocation server: adapt style | 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 | Top-level test target: support test matrix | Klaus Aehlig | |
| By supporting test matrix top-level of our test, which affects both the ALL and the UNIT_TESTS target, it is easy to run all tests for different tool chains, flags, or CC_TEST_LAUNCHER values. | |||
| 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-13 | Tutorial: Update reference to rules-cc | Oliver Reiche | |
| 2025-05-12 | Tests: Move symlink tests to remote suite | Oliver Reiche | |
| ... to make sure it is run in native and compatible mode. | |||
| 2025-05-12 | Tests: Enable compatible for normal CC tests | Oliver Reiche | |
| 2025-05-12 | Tests: Assume only parents of out_dirs exist | Oliver Reiche | |
| ... instead of the full out_dir path, which is not guaranteed by the RBE protocol. | |||
| 2025-05-12 | LocalAction: Fix collection of directory symlink | Oliver Reiche | |
| 2025-05-12 | TreeOperationsUtils: Fix Bazel Directory creation | Oliver Reiche | |
| ... which requires all entries to be sorted in lexicographical order. | |||
| 2025-05-12 | profile: gracefully handle empty response | Klaus Aehlig | |
| ... by ignoring it rather than trying to dereference a nullptr. | |||
| 2025-05-12 | Invocation server: add css style file | Sascha Roloff | |
| 2025-05-12 | ["test", "matrix"] Building a group of tests in many configurations | Klaus Aehlig | |
| Often it is desirable to run tests in a variety of configurations: different toolchain used, different target architecture, different protocol versions in end-to-end tests, etc. The rule ["test", "matrix"] allows running tests in those exponentially many combinations in a single target and thus makes full test coverage maintainable. | |||
| 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: also for action-artifacts, offer a download link | Klaus Aehlig | |
| 2025-05-12 | Invocation server: increase number of displayed invocations in the overview ↵ | Sascha Roloff | |
| to 100 | |||
| 2025-05-12 | Invocation server: cleanup html tags | Sascha Roloff | |
| 2025-05-09 | Add basic introduction to tree overlays | Klaus Aehlig | |
| 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: split invocation overview information into several lines | Sascha Roloff | |
| 2025-05-09 | Invocation server: format and spelling fixes | Sascha Roloff | |
| 2025-05-09 | invocation log: include seconds in directory name | Klaus Aehlig | |
| The directory name is designed to allow an easy rough sorting by time. This can also be used to identify the latest build for a specific user. However, users often run several builds in a single minute; therefore, increase time-stamp precission to include seconds as well. While still lexicographic and chronological order will disagree, at least for a single user it will be correct most of the times. | |||
| 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-08 | Invocation logging: add new field context variables | Sascha Roloff | |
| It allows to specify a list of environment variables, which are captured at invocation time and stored as key-value pairs in the metadata file. This allows to get some information about the invocation context such as username, merge-request ID or source branch (on a CI runner), or others. | |||
| 2025-05-08 | man pages: fix typos | Sascha Roloff | |
| 2025-05-08 | Fix some typos | Paul Cristian Sarbu | |
| 2025-05-08 | computed_roots: Fix missing return on fatal in evaluation async map | Paul Cristian Sarbu | |
| 2025-05-08 | rules: Allow all false values to disable DEBUG | Klaus Aehlig | |
| While activating DEBUG requires setting it to a non-empty map, providing information on whether and how debugg fission should be used, we should still allow any logically false value (rather than just null) to disable a debug build in order to make it easier for the user to explicitly disable debugging. Also adopt and fix the documentation strings. | |||
| 2025-05-07 | tests: add a target to run precisely the unit tests | Klaus Aehlig | |
| While there, also make sure we run unit tests that honor TEST_COMPATIBLE_REMOTE in both configurations. | |||
| 2025-05-07 | rules: Do not assume out_dirs exist | Oliver Reiche | |
| 2025-05-07 | Invocation server: also show information related to the used remote | Klaus Aehlig | |
| 2025-05-07 | profile: include remote-execution properties | Klaus Aehlig | |
| Include in the profile also the effective remote-execution endpoint, properties, and dispatch list. Software projects are often tested in a variety of environments or hardware configurations; as, obviously, the performance might differ significantly (especially depending on the used hardware) a proper analysis therefore requires the possibility to distinguish the various backends. Adding the effective configuration adds this posibility. | |||
| 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 | |
 |
index : ~aehlig/just-buildsystem/justbuild.git | |
| Main repository of just-buildsystem, containing the buildtool (just) in bootstrappable form, the multi-repository setup and launch tool (just-mr) and some auxilliary tools. | Klaus Aehlig |
| summaryrefslogtreecommitdiff |