[
https://issues.apache.org/jira/browse/SPARK-61458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ruifeng Zheng updated SPARK-61458:
----------------------------------
Description:
CI builds documentation, but the daily GitHub Pages workflow independently
rebuilds the same site.
Publish every upstream documentation build as a branch-specific
docs-preview-<branch> artifact retained for one day. Include a UTC timestamp,
workflow run ID, and run attempt in the archive filename. Preserve the
In-Progress branding on master previews and include Python API documentation in
all upstream artifacts.
Have Pages deploy the unexpired docs-preview-master artifact with the newest
creation date across all result pages, downloading the selected artifact by ID.
Keep the existing daily schedule and manual dispatch. Fail if no preview
artifact is available, leaving the current deployment in place. A successful
documentation build can be reused even when unrelated jobs in the same CI run
fail.
Artifacts from different workflow runs coexist even when their artifact names
match; newer runs do not overwrite older runs. Pages selects by creation
timestamp rather than filename date or API result order.
was:
Sampled post-merge CI builds documentation on master, but the daily GitHub
Pages workflow independently rebuilds the same site.
Publish the generated master preview as a docs-preview artifact retained for
three days. Preserve the In-Progress branding and always include the Python API
documentation in published previews.
Have Pages deploy the newest unexpired master preview artifact on its existing
daily schedule or manual dispatch. Fail if no preview artifact is available,
leaving the current deployment in place. A successful documentation build can
be reused even when unrelated jobs in the same CI run fail.
> Reuse post-merge documentation artifacts for GitHub Pages
> ---------------------------------------------------------
>
> Key: SPARK-61458
> URL: https://issues.apache.org/jira/browse/SPARK-61458
> Project: Spark
> Issue Type: Improvement
> Components: Project Infra
> Affects Versions: 5.0.0
> Reporter: Ruifeng Zheng
> Priority: Major
> Labels: pull-request-available
>
> CI builds documentation, but the daily GitHub Pages workflow independently
> rebuilds the same site.
> Publish every upstream documentation build as a branch-specific
> docs-preview-<branch> artifact retained for one day. Include a UTC timestamp,
> workflow run ID, and run attempt in the archive filename. Preserve the
> In-Progress branding on master previews and include Python API documentation
> in all upstream artifacts.
> Have Pages deploy the unexpired docs-preview-master artifact with the newest
> creation date across all result pages, downloading the selected artifact by
> ID. Keep the existing daily schedule and manual dispatch. Fail if no preview
> artifact is available, leaving the current deployment in place. A successful
> documentation build can be reused even when unrelated jobs in the same CI run
> fail.
> Artifacts from different workflow runs coexist even when their artifact names
> match; newer runs do not overwrite older runs. Pages selects by creation
> timestamp rather than filename date or API result order.
--
This message was sent by Atlassian Jira
(v10.3.26#10030026)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]