This is an automated email from the ASF dual-hosted git repository.
asf-gitbox-commits pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/hop-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 84c6a8d912 Website updated to 481ea60
84c6a8d912 is described below
commit 84c6a8d91241e9b375de9257c263a022f37207b1
Author: jenkins <[email protected]>
AuthorDate: Wed Oct 14 14:49:53 2026 +0000
Website updated to 481ea60
---
dev-manual/next/writing-documentation.html | 52 ++++++++++++++++++++++++---
manual/next/hop-server/json-api.html | 2 +-
manual/next/hop-server/rest-api.html | 2 +-
manual/next/pipeline/transforms/execinfo.html | 9 +++--
4 files changed, 56 insertions(+), 9 deletions(-)
diff --git a/dev-manual/next/writing-documentation.html
b/dev-manual/next/writing-documentation.html
index 252bd4ab3f..6a76eb2e0e 100644
--- a/dev-manual/next/writing-documentation.html
+++ b/dev-manual/next/writing-documentation.html
@@ -624,7 +624,8 @@
<div class="sectionbody">
<div class="paragraph">
<p>Documentation lives in the Hop repository next to the code it describes, in
<code>docs/</code>.
-Changing it is an ordinary pull request, which makes it one of the easiest
ways to make a first contribution.</p>
+Changing it is an ordinary pull request, which makes it one of the easiest
ways to make a first contribution.
+The <a
href="https://hop.apache.org/community/contribution-guides/documentation-contribution-guide/";>Documentation
Contribution Guide</a> on the website walks through forking the repository and
opening that pull request.</p>
</div>
</div>
</div>
@@ -703,6 +704,52 @@ The pull request build rejects cross-manual xrefs without
a version.</p>
<div class="paragraph">
<p>Anything a plugin developer needs — rather than a user — belongs in this
manual instead.</p>
</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="_previewing_the_documentation_locally"><a class="link"
href="#_previewing_the_documentation_locally">Previewing the documentation
locally</a></h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>The manuals are published by the Antora playbooks in the <a
href="https://github.com/apache/hop-website"; rel="noopener"
target="_blank">apache/hop-website</a> repository, not this one.
+Its <code>run-website-local.sh</code> script builds the website with the
documentation from your Hop checkout and serves it.</p>
+</div>
+<div class="olist arabic">
+<ol class="arabic">
+<li>
+<p>Install Node.js 22, the version the pull request build uses.</p>
+</li>
+<li>
+<p>Check out apache/hop-website next to your Hop checkout.
+The build reads <code>../hop</code>, so the Hop checkout has to be in a folder
named <code>hop</code>:</p>
+<div class="listingblock">
+<div class="content">
+<pre>work/
+├── hop/ your Hop checkout, on the branch you want to preview
+└── hop-website/ a checkout of apache/hop-website, on main</pre>
+</div>
+</div>
+</li>
+<li>
+<p>In <code>hop-website</code>, run the script:</p>
+<div class="listingblock">
+<div class="content">
+<div class="code-lang" data-pagefind-ignore>bash</div><pre class="highlightjs
highlight is-highlighted"><code class="language-bash hljs"
data-lang="bash">./run-website-local.sh</code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>It reads the working tree of <code>../hop</code>, so uncommitted edits are
included.
+When the server is up, the manuals are at
<code>http://localhost:4000/manual/latest/</code> and
<code>http://localhost:4000/dev-manual/latest/</code>.</p>
+</div>
+</li>
+</ol>
+</div>
+<div class="paragraph">
+<p>After the first build, <code>./run-website-local.sh --fast</code>
re-renders only the manuals, which takes seconds.
+Run a full build again when you delete or rename a page: <code>--fast</code>
does not remove the pages it built before.</p>
+</div>
+<div class="paragraph">
+<p>The pages are under <code>latest</code>, not <code>next</code> as on the
website: the build only contains the version on your branch, so Antora
publishes it as the latest one.</p>
+</div>
<div class="admonitionblock note">
<table>
<tr>
@@ -716,9 +763,6 @@ The pull request build rejects cross-manual xrefs without a
version.</p>
<div class="ulist">
<ul>
<li>
-<p>Building the documentation locally to preview it. The Antora playbook lives
in the Hop website repository, not this one; the exact steps need writing
down.</p>
-</li>
-<li>
<p>The AsciiDoc conventions this project actually follows: one sentence per
line, admonition usage, image sizing, how snippets under
<code>pages/snippets</code> are included.</p>
</li>
<li>
diff --git a/manual/next/hop-server/json-api.html
b/manual/next/hop-server/json-api.html
index b22dbce4c4..89029f040f 100644
--- a/manual/next/hop-server/json-api.html
+++ b/manual/next/hop-server/json-api.html
@@ -3267,7 +3267,7 @@ They are the JSON equivalent of the
<code>hop/getExecInfo</code> and <code>hop/r
<tr>
<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>GET</code></p></td>
<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>location/{location}/executions/{id}/parent</code></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Find the
parent execution ID.</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Find the
parent execution ID. This is the workflow or pipeline that owns the execution.
Before Hop 2.20 it was the action or transform that started it.</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>GET</code></p></td>
diff --git a/manual/next/hop-server/rest-api.html
b/manual/next/hop-server/rest-api.html
index f7c08cac2b..22c9d984d3 100644
--- a/manual/next/hop-server/rest-api.html
+++ b/manual/next/hop-server/rest-api.html
@@ -4755,7 +4755,7 @@ The <code>type</code> parameter selects the kind of query
to perform, and determ
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>PARENT_ID</code></p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">Get the
parent id of a child execution</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">Get the id
of the workflow or pipeline that owns the execution. Before Hop 2.20 this was
the action or transform that started it.</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">id</p></td>
</tr>
<tr>
diff --git a/manual/next/pipeline/transforms/execinfo.html
b/manual/next/pipeline/transforms/execinfo.html
index 5f282fc0cf..d786102b3a 100644
--- a/manual/next/pipeline/transforms/execinfo.html
+++ b/manual/next/pipeline/transforms/execinfo.html
@@ -3096,7 +3096,7 @@ First use Generate rows to create your fields and values
to use (children: Boole
<td class="tableblock halign-left valign-top"><p class="tableblock">Execution
parent ID</p></td>
</tr>
<tr>
-<td class="tableblock halign-left valign-top"><p class="tableblock">One output
row per child execution, with execution and state columns</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">One output
row per child execution, with execution and state columns. The id may be the
owning workflow or pipeline, or the action or transform that started the
child.</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Find last
execution</p></td>
@@ -3132,7 +3132,7 @@ First use Generate rows to create your fields and values
to use (children: Boole
<td class="tableblock halign-left valign-top"><p class="tableblock">Execution
ID</p></td>
</tr>
<tr>
-<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>id</code></p></td>
+<td class="tableblock halign-left valign-top"><p
class="tableblock"><code>id</code> of the workflow or pipeline that owns the
execution. Before Hop 2.20 this was the action or transform that started it.
That id is now <code>launchedById</code> on the execution.</p></td>
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">Get
execution data</p></td>
@@ -3161,7 +3161,10 @@ First use Generate rows to create your fields and values
to use (children: Boole
<p>Find last execution / Find previous successful execution / Get execution
and state add:</p>
</div>
<div class="paragraph">
-<p><code>executionId</code>, <code>parentId</code>, <code>name</code>,
<code>executionType</code>, <code>filename</code>, <code>executorXml</code>,
<code>metadataJson</code>, <code>registrationDate</code>,
<code>executionStartDate</code>, <code>runConfigurationName</code>,
<code>logLevel</code>, <code>updateTime</code>, <code>loggingText</code>,
<code>failed</code>, <code>statusDescription</code>,
<code>executionEndDate</code>.</p>
+<p><code>executionId</code>, <code>parentId</code>, <code>name</code>,
<code>executionType</code>, <code>filename</code>, <code>executorXml</code>,
<code>metadataJson</code>, <code>registrationDate</code>,
<code>executionStartDate</code>, <code>runConfigurationName</code>,
<code>logLevel</code>, <code>updateTime</code>, <code>loggingText</code>,
<code>failed</code>, <code>statusDescription</code>,
<code>executionEndDate</code>, <code>launchedById</code>.</p>
+</div>
+<div class="paragraph">
+<p><code>launchedById</code> is the action or transform that started the
execution. It is empty when nothing did, and it is the last column so a
pipeline that reads these fields by position keeps the columns it already
uses.</p>
</div>
<div class="paragraph">
<p>If no execution matches, the transform writes no output row for that
input.</p>
