[ 
https://issues.apache.org/jira/browse/SPARK-61458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ruifeng Zheng updated SPARK-61458:
----------------------------------
    Description: 
Sampled post-merge CI on master builds documentation that the daily GitHub 
Pages workflow also builds.

Skip the documentation job for pushes to apache/spark master and add a comment 
in build_main.yml explaining that Pages provides the documentation build 
coverage. Other upstream branches continue to request documentation, and forks 
retain their change-based job selection.


  was:
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>-<sha>-<attempt> artifact retained for one day. Name the 
archive site-<sha>-<attempt>.tar.bz2. Use the built commit hash and workflow 
run attempt so retries can upload without overwriting existing artifacts. Pages 
selects the newest artifact by its creation date, independently of commit-hash 
order.

Keep CI source versions unchanged, retain the initial build without API docs, 
and perform one complete Jekyll build. Upstream builds export SKIP_RDOC=1 to 
skip R API documentation; forks retain change-based Python and R API 
documentation builds.

Have Pages select the unexpired master preview artifact with the newest 
creation date across all result pages and download it by ID. After extraction, 
apply In-Progress Spark/PySpark labels, the search version filter, and PySpark 
version-switcher/documentation-options metadata to the generated site. Pages 
does not rebuild the documentation.

Keep the daily schedule and manual dispatch. Fail if no artifact is available, 
leaving the existing deployment in place. A successful documentation build can 
be reused even when unrelated jobs in the same CI run fail.


        Summary: Skip master post-merge documentation builds covered by Pages  
(was: Reuse post-merge documentation artifacts for GitHub Pages)

> Skip master post-merge documentation builds covered by 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
>
> Sampled post-merge CI on master builds documentation that the daily GitHub 
> Pages workflow also builds.
> Skip the documentation job for pushes to apache/spark master and add a 
> comment in build_main.yml explaining that Pages provides the documentation 
> build coverage. Other upstream branches continue to request documentation, 
> and forks retain their change-based job selection.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to