1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
|
## Release `1.2.3` (2023-11-15)
Bug fixes on top of release `1.2.2`.
### Fixes
- The cache key used for an export target is now based on the
export target itself rather than that of the exported target. The
latter could lead to spurious cache hits, but only in the case
where the exported target was an explicit file reference, and a
regular target with the same name existed as well. Where the new
cache keys would overlap with the old ones, they would refer to
the same configured targets. However, we used the fact that we
changed the target cache key to also clean up the serialization
format to only contain the JSON object describing repository,
target, and effective configuration, instead of a singleton list
containing this object. Therefore, old and new cache keys do not
overlap at all. In particular, no special care has to be taken
on upgrading or downgrading. However, old target-level cache
entries will not be used leading potentially to rebuilding of
some targets.
- Fixed a race condition in an internal cache of `just execute` used for keeping
track of running operations.
- Also symlinks are properly unlinked before installing on that
location.
## Release `1.2.2` (2023-10-17)
Bug fixes on top of release `1.2.1`.
### Fixes
- Proper handling of fetch errors in `just-mr`
- Portability improvements: bootstrapping with `-Wno-pedantic`,
case-insensitive naming, fixed version ranges in conditionals
## Release `1.2.1` (2023-08-29)
Bug fixes on top of release `1.2.0`.
### Fixes
- Portability improvements to support a wider range of
system dependencies.
- Portability improvement of the bundled absl version.
- Typos in man pages fixed.
## Release `1.2.0` (2023-08-25)
A feature release on top of `1.1.0`, backwards compatible.
### Major new features
- Actions can now define additional execution properties and in
that way chose a specific remote execution image, as well as a
factor to scale the time out. This also applies to the built-in
`generic` rule. Additionally, the remote-execution endpoint can
be dispatched based on the remote-execution properties using
the `--endpoint-configuration` argument.
- Relative non-upwards symbolic links are now treated as first-class
objects. This introduces a new artifact type and allows the free use
of such symbolic links throughout the build process.
- `just-mr` can now optionally resolve symlinks contained in archives.
### Other changes
- `just-import-git` now supports an option `--plain` to import a
repository without dependencies.
- Minor changes to the layout of the local build root; in particular,
left-over execution directories, as well as left-over temporary
directories of `just-mr`, will eventually get cleaned up by
garbage collection.
- `just-mr` now supports unpacking tar archives compressed with
bzip2, xz, lzip, and lzma.
- The option `-P` of `build` and `install-cas` can be used to
inspect parts of a tree.
- `just-mr` now supports unpacking 7zip archives (with default
compression) when provided as `"zip"` type repositories.
- The configuration variable `COMPILER_FAMILY` is replaced by the more
flexible `TOOLCHAIN_CONFIG`, an object which may contain the field
`FAMILY`. From now on, this object is used to set the compiler family
(e.g., for GNU, set `{"TOOLCHAIN_CONFIG":{"FAMILY":"gnu"}}`).
### Fixes
- Removed potential uses of `malloc` between `fork` and `exec`.
This removes the risk of deadlocks on certain combinations of
`C++` standard library and `libc`.
- The link flags for the final linking now can be set via the
configuration variable `FINAL_LDFLAGS`; in particular, the stack
size can easily be adapted. The default stack size is now set to
8M, removing an overflow on systems where the default stack size
was significantly lower.
- The man pages are now provided as markdown files, allowing to
potentially reduce the build dependencies to more standard ones.
- `just-mr` now correctly performs a forced add in order to stage
all entries in a Git repository. Previously it was possible for
entries to be skipped inadvertently in, e.g., imported archives
if `gitignore` files were present.
- Temporary files generated by `just execute` are now created inside
the local build root.
- `just install-cas` now correctly handles `--raw-tree` also for
remote-execution endpoints.
- `just install-cas` now, like `just install`, removes an existing
destination file before installing instead of overwriting.
- Only actions with exit code 0 that generated all required outputs
are taken from cache, instead of all actions with exit code 0.
This only affects remote execution, as purely local build didn't
cache actions with incomplete outputs.
### Changes since `1.2.0~beta3`
- Only actions with exit code 0 that generated all required outputs
are taken from cache, instead of all actions with exit code 0.
This only affects remote execution, as purely local build didn't
cache actions with incomplete outputs.
- Splitting off libraries from the main binary targets to simplify
cherry-picking future fixes from the head development branch.
- Improvements of the bundled dependency descriptions.
- Update of documentation.
## Release `1.2.0~beta3` (2023-08-22)
Third beta release for the upcoming `1.2.0` release; see release
notes there.
### Changes since `1.2.0~beta2`
- Update and clean up of bundled dependency descriptions
- Improvement of documentation
## Release `1.2.0~beta2` (2023-08-18)
Second beta release for the upcoming `1.2.0` release; see release
notes there.
### Changes since `1.2.0~beta1`
- Clean up of the internal build description of bundled dependencies.
- Clean up of the internal rules, in particular renaming of
implicit dependency targets.
- Various documentation improvements.
## Release `1.2.0~beta1` (2023-08-16)
First beta release for the upcoming `1.2.0` release; see release
notes there.
## Release `1.1.0` (2023-05-19)
A feature release on top of `1.0.0`, backwards compatible.
### Major new features
- new subcommand `just execute` to start a single node execution
service
- New subcommand `just gc` to clean up no longer needed cache and
CAS entries
- `just` now supports authentication to remote execution via TLS
and mutual TLS
- `just-mr` is now available as C++ binary and supports fetching in parallel
### Important changes
- The option `-D` now accumulates instead of ignoring all but the
latest occurrence. This is an incompatible change of the command
line, but not affecting the backwards compatibility of the build.
- The option `-L` of `just-mr` now is an alternative name for option
`--local-launcher` instead of `--checkout-locations`, and thus
matching its meaning in `just`. This is an incompatible change of
the command line, but not affecting the backwards compatibility of
the build.
### Other changes
- `just install` and `just install-cas` now have a new `--remember`
option ensuring that the installed artifacts are also mirrored in
local CAS
- `just analyse` now supports a new option `--dump-export-targets`
### Note
There is a regression in `libgit2` versions `1.6.1` up to and
including `1.6.4` with a fix already committed upstream. This
regression makes `just` unusable when built against those versions.
Therefore, the third-party build description for `libgit2` is still
for version `1.5.2`.
## Release `1.1.0~beta2` (2023-05-15)
Second beta release for the upcoming `1.1.0` release; see release
notes there.
### Changes since `1.1.0~beta1`
- fix a race condition in our use of `libgit2`
- a fix in the error handling of git trees
- fixes to the third-party descriptions of our dependencies; in particular,
the structure of the `export` targets is cleaned up. These changes should
not affect package builds.
- various minor fixes to documentation and tests
### Note
There is a regression in `libgit2` versions `1.6.1` upto and
including `1.6.4` with a fix already committed upstream. This
regression makes `just` unusable when built against those versions.
Therefore, the third-party build description for `libgit2` is still
for version `1.5.2`.
## Release `1.1.0~beta1` (2023-04-28)
First beta release for the upcoming `1.1.0` release; see release
notes there.
## Release `1.0.0` (2022-12-12)
Initial stable release.
### Important changes since `1.0.0~beta6`
- built-in rule "tree" added
- clean up of user-defined rules for C++
- various documentation improvements
## Release `1.0.0~beta6` (2022-10-16)
### Important changes since `1.0.0~beta5`
- The "configure" built-in rule now evaluates "target". Also,
a bug in the computation of the effective configuration
was fixed.
- Option `--dump-vars` added to `just analyse`
- Rule fixes in propagating `ENV`
- Launcher functionality added to `just-mr`
- `just` now takes the lexicographically first repository as default
if no main repository is specified
## Release `1.0.0~beta5` (2022-10-19)
First public beta version.
|
