Age | Commit message (Collapse) | Author |
|
|
|
Adds documentation for the new proto requests required for the
'to_git' pragma root handling, as well as general syncing of root
trees. Also adds clarifying comments on handling of absent roots by
just-mr.
|
|
|
|
|
|
The implicit extensional projection of target-level caching and
garbage collection interact in a subtile way. Add a design document
describing how we keep the invariant required by target-level
caching in the presence of garbage collection. While, techincally,
this just describes how to fix a bug, a careful design is still
needed, as some fundamental changes are made.
|
|
|
|
|
|
When explaining CC tests, the option --request-action-input is used
to get hold of the actual test binary. This is the first time in
the tutorial where the action graph is larger than the part that
that is traversed during the build. Use this oportunity to explain
the difference between those concpets as, reportedly, some users
got confused about this.
|
|
|
|
|
|
|
|
|
|
... as an overlay for the configuration, not the configuration
to be used for the target to configure.
|
|
|
|
|
|
|
|
Remove wrong (un-needed) design specifications. When we compute the
TargetCacheKey of an export target, there is no need to check if any
of (recursively) referenced trees is absent. As soon as we deal with
an "absent target" we query just serve. If it is not able to provide
the target cache value, we error out.
|
|
|
|
...and reword content to move from proposal to implemented state.
|
|
This improves clarity while maintaining specificity of the JSON
file entries. Also fixes the typo in the design document name.
|
|
... ensuring that just-mr passes on the specified environment
variables (and only those) to the tree-generating action.
|
|
|
|
|
|
Co-authored-by: Paul Cristian Sarbu <paul.cristian.sarbu@huawei.com>
|
|
... and point to the repository with machine-readable instructions
on how to properly build them.
|
|
|
|
- Document that `just serve` can be asked to back up a tree to the
remote execution end point.
- Specify, that similar to getting the tree of a commit, just serve
can also be asked to provide the tree of an unpacked archive
given by its blob identifier.
- Document the auxilliary request by which `just build` can get
the needed information about the flexible variables of an export
target in order to construct the correct cache key.
|
|
|
|
|
|
|
|
|
|
While there,
- remove the outdated claim that in package build of just the prebuilt
library aproach of a header-only library with link dependencies
is chosen, and
- remove a wrong footnote separator.
|
|
... while providing a native descirption still is the cleaner approach.
Nevertheless, hinting on this fact early avoids scaring off novice
users having a lot of dependencies.
|
|
... as a way to find out more about the defining rule of a target.
While there, also be a bit more explicit about target naming and the
fact that the default target is a target of the rules repository.
|
|
... emphasizing that source files are just targets and that we
could as well use a defined target there.
|
|
|
|
|
|
While a foldl is enough to implement a reverse functionality,
adding it as a built in allows doing so in linear time.
|
|
... to obtain from a list of strings a map with those entries
as keys and true as value. In this way, repeated membership tests
in lists can be implemented more efficiently.
|
|
|
|
We now allow restrictive use of upwards symbolic links when
importing filesystem directories and archives to git.
|
|
|
|
... but an implemented concept. Update the documentation accordingly.
|
|
Also link it in the README.
|
|
|
|
via a 'SYMLINK' constructor function. This works similarly to the
'FILE' construct, but the name given must point to a non-upwards
symlink and a symlink artifact is being generated from it.
Also updates the relevant tests.
|
|
|
|
... as the result of evaluating "timeout scaling" or "execution
properties". This implicit default is already implemented and
allow simple access to variables without having to care for default
values, thus having simpler rules.
|
|
|
|
... so that users who want use just as an execution service for
other build tools are aware and don't run into errors due to
incompatible hashes.
|