You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@spark.apache.org by gi...@apache.org on 2026/10/13 11:10:10 UTC
(spark-website) branch asf-site updated: [html] Automatically generate and commit site HTML (#699)
This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/spark-website.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 1497754dde [html] Automatically generate and commit site HTML (#699)
1497754dde is described below
commit 1497754dde382ae5c128349878552fa90cd84094
Author: github-actions[bot] <gi...@users.noreply.github.com>
AuthorDate: Tue Oct 13 11:10:04 2026 +0000
[html] Automatically generate and commit site HTML (#699)
---
site/release-process.html | 47 +++++++++++++++++++-----------------------
site/sitemap.xml | 39 ++++++++++++++++-------------------
site/third-party-projects.html | 2 +-
3 files changed, 40 insertions(+), 48 deletions(-)
diff --git a/site/release-process.html b/site/release-process.html
index aeb8b2e7a3..9934d1bbde 100644
--- a/site/release-process.html
+++ b/site/release-process.html
@@ -400,6 +400,8 @@ that looks something like <code class="language-plaintext highlighter-rouge">[VO
<li><a href="#create-an-announcement">Create an announcement</a></li>
</ul>
+<p>The <code class="language-plaintext highlighter-rouge">finalize</code> step pushes to the <code class="language-plaintext highlighter-rouge">asf-site</code> branch of spark-website. After that push, you may see a follow-up <code class="language-plaintext highlighter-rouge">[html]</code> commit from GitHub Actions. This is normal.</p>
+
<p>Please manually verify the result after each step.</p>
<p align="right"><a href="#top">Return to top</a></p>
@@ -504,26 +506,28 @@ $ git push apache v1.1.1
<p>It’s recommended to not remove the generated docs of the latest RC, so that we can copy it to
spark-website directly, otherwise you need to re-build the docs.</p>
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code># Build the latest docs
-$ git checkout v1.1.1
-$ cd docs
-$ PRODUCTION=1 bundle exec jekyll build
+<div class="language-sh highlighter-rouge"><div class="highlight"><pre class="highlight"><code><span class="c"># Build the latest docs</span>
+<span class="nv">$ </span>git checkout v1.1.1
+<span class="nv">$ </span><span class="nb">cd </span>docs
+<span class="nv">$ PRODUCTION</span><span class="o">=</span>1 bundle <span class="nb">exec </span>jekyll build
-# Copy the new documentation to Apache
-$ git clone https://github.com/apache/spark-website
+<span class="c"># Copy the new documentation to Apache</span>
+<span class="nv">$ </span>git clone https://github.com/apache/spark-website
...
-$ cp -R _site spark-website/site/docs/1.1.1
-
-# Update the "latest" link
-$ cd spark-website/site/docs
-$ rm latest
-$ ln -s 1.1.1 latest
+<span class="nv">$ </span><span class="nb">cp</span> <span class="nt">-R</span> _site spark-website/site/docs/1.1.1
+
+<span class="c"># Update the "latest" link</span>
+<span class="nv">$ </span><span class="nb">cd </span>spark-website/site/docs
+<span class="nv">$ </span><span class="nb">rm </span>latest
+<span class="nv">$ </span><span class="nb">ln</span> <span class="nt">-s</span> 1.1.1 latest
+<span class="nv">$ </span><span class="nb">cd</span> ../..
+<span class="nv">$ </span>git add site/docs/1.1.1 site/docs/latest
+<span class="nv">$ </span>git commit <span class="nt">-m</span> <span class="s2">"Add docs for Spark 1.1.1"</span>
</code></pre></div></div>
<h4 id="update-the-rest-of-the-spark-website">Update the rest of the Spark website</h4>
-<p>Next, update the rest of the Spark website. See how the previous releases are documented
-(all the HTML file changes are generated by <code class="language-plaintext highlighter-rouge">jekyll</code>). In particular:</p>
+<p>Next, update the rest of the Spark website. See how the previous releases are documented. In particular:</p>
<ul>
<li>update <code class="language-plaintext highlighter-rouge">documentation.md</code> to add link to the docs for the new release</li>
@@ -533,9 +537,7 @@ $ ln -s 1.1.1 latest
<li>check <code class="language-plaintext highlighter-rouge">security.md</code> for anything to update</li>
</ul>
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>$ git add 1.1.1
-$ git commit -m "Add docs for Spark 1.1.1"
-</code></pre></div></div>
+<p>Commit these source files normally. You do not need to run <code class="language-plaintext highlighter-rouge">jekyll build</code> or commit anything else under <code class="language-plaintext highlighter-rouge">site/</code>. After the change is merged to <code class="language-plaintext highlighter-rouge">asf-site</code>, GitHub Actions generates the HTML under <code class="language-plaintext highlighter-rouge">site/</code> and pushes it for you.</p>
<p>Then, create the release notes. Go to the
<a href="https://issues.apache.org/jira/projects/SPARK?selectedItem=com.atlassian.jira.jira-projects-plugin:release-page">release page in JIRA</a>,
@@ -544,13 +546,7 @@ pick the release version from the list, then click on “Release Notes”
<code class="language-plaintext highlighter-rouge">spark-2.1.2</code>. Create a new release post under <code class="language-plaintext highlighter-rouge">releases/_posts</code> to include this short URL. The date of the post should
be the date you create it.</p>
-<p>Then run <code class="language-plaintext highlighter-rouge">bundle exec jekyll build</code> to update the <code class="language-plaintext highlighter-rouge">site</code> directory.</p>
-
-<p>Considering the Pull Request will be large, please separate the commits of code changes and generated <code class="language-plaintext highlighter-rouge">site</code> directory for an easier review.</p>
-
-<p>After merging the change into the <code class="language-plaintext highlighter-rouge">asf-site</code> branch, you may need to create a follow-up empty
-commit to force synchronization between ASF’s git and the web site, and also the GitHub mirror.
-For some reason synchronization seems to not be reliable for this repository.</p>
+<p>After merging the change into the <code class="language-plaintext highlighter-rouge">asf-site</code> branch, confirm the GitHub Actions run finished and the generated HTML is on the site. You may need to create a follow-up empty commit to force synchronization between ASF’s git and the website, and also the GitHub mirror. For some reason synchronization seems to not be reliable for this repository.</p>
<p>On a related note, make sure the version is marked as released on JIRA. Go find the release page as above, eg.,
<a href="https://issues.apache.org/jira/projects/SPARK/versions/12340295"><code class="language-plaintext highlighter-rouge">https://issues.apache.org/jira/projects/SPARK/versions/12340295</code></a>,
@@ -611,8 +607,7 @@ $ git log v1.1.1 --grep "$expr" --shortstat --oneline | grep -B 1 -e "[3-9][0-9]
<h3 id="create-an-announcement">Create an announcement</h3>
<p>Once everything is working (website docs, website changes) create an announcement on the website
-and then send an e-mail to the mailing list with a subject that looks something like <code class="language-plaintext highlighter-rouge">[ANNOUNCE] ...</code>. To create an announcement, create a post under
-<code class="language-plaintext highlighter-rouge">news/_posts</code> and then run <code class="language-plaintext highlighter-rouge">bundle exec jekyll build</code>.</p>
+and then send an e-mail to the mailing list with a subject that looks something like <code class="language-plaintext highlighter-rouge">[ANNOUNCE] ...</code>. To create an announcement, create a post under <code class="language-plaintext highlighter-rouge">news/_posts</code>. GitHub Actions will automatically generate the corresponding HTML when you push to <code class="language-plaintext highlighter-rouge">asf-site</code>.</p>
<p>Enjoy an adult beverage of your choice, and congratulations on making a Spark release.</p>
diff --git a/site/sitemap.xml b/site/sitemap.xml
index 50b553975f..fe1b2bb590 100644
--- a/site/sitemap.xml
+++ b/site/sitemap.xml
@@ -1195,7 +1195,10 @@
<loc>https://spark.apache.org/releases/spark-release-0-3.html</loc>
<changefreq>weekly</changefreq>
</url>
-
+<url>
+ <loc>https://spark.apache.org/</loc>
+ <changefreq>weekly</changefreq>
+</url>
<url>
<loc>https://spark.apache.org/404.html</loc>
<changefreq>weekly</changefreq>
@@ -1236,6 +1239,10 @@
<loc>https://spark.apache.org/faq.html</loc>
<changefreq>weekly</changefreq>
</url>
+<url>
+ <loc>https://spark.apache.org/graphx/</loc>
+ <changefreq>weekly</changefreq>
+</url>
<url>
<loc>https://spark.apache.org/history.html</loc>
<changefreq>weekly</changefreq>
@@ -1245,15 +1252,15 @@
<changefreq>weekly</changefreq>
</url>
<url>
- <loc>https://spark.apache.org/sql/</loc>
+ <loc>https://spark.apache.org/mailing-lists.html</loc>
<changefreq>weekly</changefreq>
</url>
<url>
- <loc>https://spark.apache.org/news/</loc>
+ <loc>https://spark.apache.org/mllib/</loc>
<changefreq>weekly</changefreq>
</url>
<url>
- <loc>https://spark.apache.org/streaming/</loc>
+ <loc>https://spark.apache.org/news/</loc>
<changefreq>weekly</changefreq>
</url>
<url>
@@ -1261,15 +1268,15 @@
<changefreq>weekly</changefreq>
</url>
<url>
- <loc>https://spark.apache.org/graphx/</loc>
+ <loc>https://spark.apache.org/powered-by.html</loc>
<changefreq>weekly</changefreq>
</url>
<url>
- <loc>https://spark.apache.org/mllib/</loc>
+ <loc>https://spark.apache.org/release-process.html</loc>
<changefreq>weekly</changefreq>
</url>
<url>
- <loc>https://spark.apache.org/spark-connect/</loc>
+ <loc>https://spark.apache.org/research.html</loc>
<changefreq>weekly</changefreq>
</url>
<url>
@@ -1277,30 +1284,21 @@
<changefreq>weekly</changefreq>
</url>
<url>
- <loc>https://spark.apache.org/</loc>
- <changefreq>weekly</changefreq>
-</url>
-<url>
- <loc>https://spark.apache.org/mailing-lists.html</loc>
- <changefreq>weekly</changefreq>
-</url>
-<url>
- <loc>https://spark.apache.org/powered-by.html</loc>
+ <loc>https://spark.apache.org/security.html</loc>
<changefreq>weekly</changefreq>
</url>
<url>
- <loc>https://spark.apache.org/release-process.html</loc>
+ <loc>https://spark.apache.org/spark-connect/</loc>
<changefreq>weekly</changefreq>
</url>
<url>
- <loc>https://spark.apache.org/research.html</loc>
+ <loc>https://spark.apache.org/sql/</loc>
<changefreq>weekly</changefreq>
</url>
<url>
- <loc>https://spark.apache.org/security.html</loc>
+ <loc>https://spark.apache.org/streaming/</loc>
<changefreq>weekly</changefreq>
</url>
-
<url>
<loc>https://spark.apache.org/third-party-projects.html</loc>
<changefreq>weekly</changefreq>
@@ -1313,5 +1311,4 @@
<loc>https://spark.apache.org/versioning-policy.html</loc>
<changefreq>weekly</changefreq>
</url>
-
</urlset>
diff --git a/site/third-party-projects.html b/site/third-party-projects.html
index 321dca5e74..04beba6ade 100644
--- a/site/third-party-projects.html
+++ b/site/third-party-projects.html
@@ -268,7 +268,7 @@ transforming, and analyzing genomic data using Apache Spark</li>
<h2 id="adding-new-projects">Adding new projects</h2>
-<p>To add a project, open a pull request against the <a href="https://github.com/apache/spark-website">spark-website</a> repository. Add an entry to <a href="https://github.com/apache/spark-website/blob/asf-site/third-party-projects.md">this markdown file</a>, then run <code class="language-plaintext highlighter-rouge">jekyll build</code> to generate the HTML too. Include both in your pull request. See the README in this repo for more information.</p>
+<p>To add a project, open a pull request against the <a href="https://github.com/apache/spark-website">spark-website</a> repository. Add an entry to <a href="https://github.com/apache/spark-website/blob/asf-site/third-party-projects.md">this markdown file</a> and follow the <a href="https://github.com/apache/spark-website#readme">README instructions</a> to submit a pull request with your changes.</p>
<p>Note that all project and product names should follow <a href="/trademarks.html">trademark guidelines</a>.</p>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@spark.apache.org
For additional commands, e-mail: commits-help@spark.apache.org