Named build definitions (v0.9.14)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
mhoennig
2026-08-28 20:47:28 +02:00
co-authored by Claude Fable 5
parent 0e8db18e69
commit 3ff27dac0b
2 changed files with 17 additions and 1 deletions
+1 -1
View File
@@ -12,7 +12,7 @@ group = "de.hoennig"
// bump at least the patch version for every deployment — and only then, not per commit — // bump at least the patch version for every deployment — and only then, not per commit —
// so the UI footer (BuildProperties), --version and the release notes identify what is // so the UI footer (BuildProperties), --version and the release notes identify what is
// actually running; a deployment bundles whatever was committed since the last one // actually running; a deployment bundles whatever was committed since the last one
version = "0.9.13" version = "0.9.14"
java { java {
toolchain { toolchain {
@@ -7,6 +7,22 @@
<div th:replace="~{fragments :: nav(${view})}"></div> <div th:replace="~{fragments :: nav(${view})}"></div>
<div class="panel release-notes"> <div class="panel release-notes">
<h2>v0.9.14 <span class="muted">— 2026-08-28</span></h2>
<ul>
<li>Named build definitions (ADR 0007): the <code>builds</code> section of
<code>.gittally.yml</code> now defines jobs with <code>onPush</code>/<code>atTimes</code>
triggers, branch selectors (name globs, <code>activeWithin</code> age filter), and
overrides of the branch settings — e.g. a nightly <code>pitest</code> build running a
fuller check than the quick on-push builds. A named build records under its own
<code>&lt;branch&gt;@&lt;build&gt;</code> pool with its own branches-view row, retention
count, and permanent latest-green artifact link.</li>
<li>Restart, <code>gittally retry</code>, and the startup recovery re-run a build under its
recorded definition, resolving the settings from the current configuration.</li>
<li><strong>Changed:</strong> the v0.9.13 per-slot <code>buildCommand</code>/<code>name</code>
syntax in <code>autoBuild.times</code> is gone again — use a build definition instead.
<code>branches.*.autoBuild</code> with plain times keeps working but is deprecated.</li>
</ul>
<h2>v0.9.13 <span class="muted">— 2026-08-28</span></h2> <h2>v0.9.13 <span class="muted">— 2026-08-28</span></h2>
<ul> <ul>
<li>A scheduled auto-build slot (<code>autoBuild.times</code> entry) can carry its own <li>A scheduled auto-build slot (<code>autoBuild.times</code> entry) can carry its own