This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/beam.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 99e8b3b Publishing website 2022/04/01 06:39:57 at commit ca47cd8
99e8b3b is described below
commit 99e8b3b7871d4ab2b426f2296995c54840701d60
Author: jenkins <[email protected]>
AuthorDate: Fri Apr 1 06:39:58 2022 +0000
Publishing website 2022/04/01 06:39:57 at commit ca47cd8
---
website/generated-content/contribute/index.xml | 8 ++++++--
website/generated-content/contribute/release-guide/index.html | 10 +++++++---
website/generated-content/sitemap.xml | 2 +-
3 files changed, 14 insertions(+), 6 deletions(-)
diff --git a/website/generated-content/contribute/index.xml
b/website/generated-content/contribute/index.xml
index 99a855a..c97a60a 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -689,11 +689,15 @@ You only need to enable &ldquo;repo&rdquo;
permissions to this token.<
<li>Then run
<pre><code>cd beam/release/src/main/scripts &amp;&amp;
./verify_release_build.sh
</code></pre></li>
-<li>Trigger <code>beam_Release_Gradle_Build</code> and all PostCommit
Jenkins jobs from PR (which is created by previous step).
+<li>Trigger <code>beam_Release_Gradle_Build</code> and all Jenkins
PostCommit jobs from the PR created by the previous step.
You can run <a
href="https://github.com/apache/beam/blob/master/release/src/main/scripts/mass_comment.py";>mass_comment.py</a>
to do that.
Or manually add one trigger phrase per PR comment.
See <code>COMMENTS_TO_ADD</code> in <a
href="https://github.com/apache/beam/blob/master/release/src/main/scripts/mass_comment.py";>mass_comment.py</a>
-for full list of phrases.</li>
+for full list of phrases. Please note that this list of phrases can get
+out of date, it&rsquo;s your responsibility to run <em>all</em>
PostCommits, not just
+the ones listed there.
+<a
href="https://issues.apache.org/jira/browse/BEAM-13951";>BEAM-13951</a> has
+directions for updating this list using the Jenkins API.</li>
</ol>
</li>
<li>
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index c5ccd7f..845b3c3 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -97,11 +97,15 @@ There are 2 ways to perform this verification, either
running automation script(
See instruction <a
href=https://help.github.com/en/articles/creating-a-personal-access-token-for-the-command-line>here</a>.
It’ll be used by the script for accessing Github API.
You only need to enable “repo” permissions to this
token.</li><li>Update required configurations listed in
<code>RELEASE_BUILD_CONFIGS</code> in <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/script.config>script.config</a></li><li>Then
run<pre><code>cd beam/release/src/main/scripts &&
./verify_release_build.sh
-</code></pre></li><li>Trigger <code>beam_Release_Gradle_Build</code> and all
PostCommit Jenkins jobs from PR (which is created by previous step).
+</code></pre></li><li>Trigger <code>beam_Release_Gradle_Build</code> and all
Jenkins PostCommit jobs from the PR created by the previous step.
You can run <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/mass_comment.py>mass_comment.py</a>
to do that.
Or manually add one trigger phrase per PR comment.
See <code>COMMENTS_TO_ADD</code> in <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/mass_comment.py>mass_comment.py</a>
-for full list of phrases.</li></ol></li><li><p><strong>Tasks included in the
script</strong></p><ol><li>Installs <code>hub</code> with your agreement and
setup local git repo;</li><li>Create a test PR against release
branch;</li></ol></li></ul><p>The <a
href=https://ci-beam.apache.org/job/beam_Release_Gradle_Build/><code>beam_Release_Gradle_Build</code></a>
Jenkins job runs <code>./gradlew build -PisRelease</code>.
+for full list of phrases. Please note that this list of phrases can get
+out of date, it’s your responsibility to run <em>all</em> PostCommits,
not just
+the ones listed there.
+<a href=https://issues.apache.org/jira/browse/BEAM-13951>BEAM-13951</a> has
+directions for updating this list using the Jenkins
API.</li></ol></li><li><p><strong>Tasks included in the
script</strong></p><ol><li>Installs <code>hub</code> with your agreement and
setup local git repo;</li><li>Create a test PR against release
branch;</li></ol></li></ul><p>The <a
href=https://ci-beam.apache.org/job/beam_Release_Gradle_Build/><code>beam_Release_Gradle_Build</code></a>
Jenkins job runs <code>./gradlew build -PisRelease</code>.
This only verifies that everything builds with unit tests passing.</p><h4
id=verify-the-build-succeeds>Verify the build succeeds</h4><ul><li>Tasks you
need to do manually to <strong>verify the build succeed</strong>:<ol><li>Check
the build result.</li><li>If build failed, scan log will contain all
failures.</li><li>You should stabilize the release branch until release build
succeeded.</li></ol></li></ul><p>There are some projects that don’t
produce the artifacts, e.g. <code>beam-te [...]
versions to run Python tests. See Python installation tips in <a
href=https://cwiki.apache.org/confluence/display/BEAM/Python+Tips#PythonTips-InstallingPythoninterpreters>Developer
Wiki</a>.</p><ul><li><p><strong>Run gradle release
build</strong></p><ol><li><p>Clean current workspace</p><pre><code>git clean
-fdx
./gradlew clean
@@ -409,7 +413,7 @@ If you end up getting permissions errors ask on the mailing
list for assistance.
Ask other contributors to do the same.</p><p>Also, update <a
href=https://en.wikipedia.org/wiki/Apache_Beam>the Wikipedia article on Apache
Beam</a>.</p><h3 id=checklist-to-declare-the-process-completed>Checklist to
declare the process completed</h3><ol><li>Release announced on the user@
mailing list.</li><li>Blog post published, if applicable.</li><li>Release
recorded in reporter.apache.org.</li><li>Release announced on social
media.</li><li>Completion declared on the dev@ mailing list. [...]
Once you’ve finished the release, please take a step back and look what areas
of this process and be improved. Perhaps some part of the process can be
simplified.
Perhaps parts of this guide can be clarified.</p><p>If we have specific ideas,
please start a discussion on the dev@ mailing list and/or propose a pull
request to update this guide.
-Thanks!</p><div class=feedback><p class=update>Last updated on
2022/02/11</p><h3>Have you found everything you were looking for?</h3><p
class=description>Was it all useful and clear? Is there anything that you would
like to change? Let us know!</p><button class=load-button><a
href="mailto:[email protected]?subject=Beam Website Feedback">SEND
FEEDBACK</a></button></div></div></div><footer class=footer><div
class=footer__contained><div class=footer__cols><div class="footer__cols__col
foo [...]
+Thanks!</p><div class=feedback><p class=update>Last updated on
2022/03/31</p><h3>Have you found everything you were looking for?</h3><p
class=description>Was it all useful and clear? Is there anything that you would
like to change? Let us know!</p><button class=load-button><a
href="mailto:[email protected]?subject=Beam Website Feedback">SEND
FEEDBACK</a></button></div></div></div><footer class=footer><div
class=footer__contained><div class=footer__cols><div class="footer__cols__col
foo [...]
<a href=http://www.apache.org>The Apache Software Foundation</a>
| <a href=/privacy_policy>Privacy Policy</a>
| <a href=/feed.xml>RSS Feed</a><br><br>Apache Beam, Apache, Beam, the Beam
logo, and the Apache feather logo are either registered trademarks or
trademarks of The Apache Software Foundation. All other products or name brands
are trademarks of their respective holders, including The Apache Software
Foundation.</div></div></div></div></footer></body></html>
\ No newline at end of file
diff --git a/website/generated-content/sitemap.xml
b/website/generated-content/sitemap.xml
index 5eb00de..4bc9a1e 100644
--- a/website/generated-content/sitemap.xml
+++ b/website/generated-content/sitemap.xml
@@ -1 +1 @@
-<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";
xmlns:xhtml="http://www.w3.org/1999/xhtml";><url><loc>/blog/beam-2.37.0/</loc><lastmod>2022-03-04T10:14:02-08:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2022-03-28T08:41:34-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2022-03-28T08:41:34-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2022-03-28T08:41:34-07:00</lastmod></url><url><loc>/blog/u
[...]
\ No newline at end of file
+<?xml version="1.0" encoding="utf-8" standalone="yes"?><urlset
xmlns="http://www.sitemaps.org/schemas/sitemap/0.9";
xmlns:xhtml="http://www.w3.org/1999/xhtml";><url><loc>/blog/beam-2.37.0/</loc><lastmod>2022-03-04T10:14:02-08:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2022-03-28T08:41:34-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2022-03-28T08:41:34-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2022-03-28T08:41:34-07:00</lastmod></url><url><loc>/blog/u
[...]
\ No newline at end of file
