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 5a049ad Publishing website 2020/09/25 18:04:03 at commit 806e67d
5a049ad is described below
commit 5a049adfcb5379c68a2936dbd4fc229a42ce22c8
Author: jenkins <bui...@apache.org>
AuthorDate: Fri Sep 25 18:04:03 2020 +0000
Publishing website 2020/09/25 18:04:03 at commit 806e67d
---
website/generated-content/contribute/index.xml | 7 ++++---
website/generated-content/contribute/release-guide/index.html | 8 +++++---
website/generated-content/sitemap.xml | 2 +-
3 files changed, 10 insertions(+), 7 deletions(-)
diff --git a/website/generated-content/contribute/index.xml
b/website/generated-content/contribute/index.xml
index 1b61e6d..092cee4 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -696,13 +696,15 @@ There are 2 ways to perform this verification, either
running automation script(
<ol>
<li>Create a personal access token from your Github account. See
instruction <a
href="https://help.github.com/en/articles/creating-a-personal-access-token-for-the-command-line";>here</a>.
It&rsquo;ll be used by the script for accessing Github API.
-You don&rsquo;t have to add any permissions to this token.</li>
+You only need to enable &ldquo;repo&rdquo; 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 &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).
-To do so, only add one trigger phrase per comment. See
<code>JOB_TRIGGER_PHRASES</code> in <a
href="https://github.com/apache/beam/blob/master/release/src/main/scripts/verify_release_build.sh#L43";>verify_release_build.sh</a>
+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>
@@ -716,7 +718,6 @@ for full list of phrases.</li>
</ul>
<p>Jenkins job <code>beam_Release_Gradle_Build</code> basically run
<code>./gradlew build -PisRelease</code>.
This only verifies that everything builds with unit tests passing.</p>
-<p>You can use <a
href="https://github.com/apache/beam/blob/master/release/src/main/scripts/mass_comment.py";>mass_comment.py</a>
to mass-comment on PR.</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>:
diff --git a/website/generated-content/contribute/release-guide/index.html
b/website/generated-content/contribute/release-guide/index.html
index e60148a..7546e0f 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -103,11 +103,13 @@ so builds will be broken until a new snapshot is
available.</p><p>There are 2 wa
</code></pre></li><li><p>The script will:</p><ol><li>Install <a
href=https://github.com/github/hub>hub</a> with your agreement.</li><li>Touch
an empty txt file and commit changes into <code>${your remote beam
repo}/snapshot_build</code></li><li>Use hub to create a PR against
apache:master, which triggers a Jenkins job to build
snapshot.</li></ol></li><li><p>Tasks you need to do manually to <strong>verify
the SNAPSHOT build</strong></p><ol><li>Check whether the Jenkins job gets
triggered. [...]
There are 2 ways to perform this verification, either running automation
script(recommended), or running all commands manually.</p><p>! Dataflow tests
will fail if Dataflow worker container is not created and published by this
time. (Should be done by Google)</p><h4
id=run-automation-script-verify_release_buildsh>Run automation script
(verify_release_build.sh)</h4><ul><li><p>Script: <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/verify_release_build.sh>verify
[...]
It’ll be used by the script for accessing Github API.
-You don’t have to add any 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
+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).
-To do so, only add one trigger phrase per comment. See
<code>JOB_TRIGGER_PHRASES</code> in <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/verify_release_build.sh#L43>verify_release_build.sh</a>
+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>Tasks included in the
script</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>Jenkins job
<code>beam_Release_Gradle_Build</code> basically run <code>./gradlew build
-PisRelease</code>.
-This only verifies that everything builds with unit tests passing.</p><p>You
can use <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/mass_comment.py>mass_comment.py</a>
to mass-comment on PR.</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 t [...]
+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 [...]
ignore failures there.</p><p>To triage the failures and narrow things down you
may want to look at <code>settings.gradle</code> and run the build only for the
projects you’re interested at the moment, e.g. <code>./gradlew
:runners:java-fn-execution</code>.</p><h4
id=alternative-run-release-build-manually-locally>(Alternative) Run release
build manually (locally)</h4><ul><li><p>Pre-installation for python
build</p><ol><li><p>Install pip</p><pre><code>curl
https://bootstrap.pypa.io/get-pip.py -o get-pip.py
python get-pip.py
diff --git a/website/generated-content/sitemap.xml
b/website/generated-content/sitemap.xml
index 8bcdabc..f65f622 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.24.0/</loc><lastmod>2020-09-18T12:38:38-07:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2020-09-18T12:38:38-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2020-09-18T12:38:38-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2020-09-18T12:38:38-07:00</lastmod></url><url><loc>/blog/p
[...]
\ 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.24.0/</loc><lastmod>2020-09-18T12:38:38-07:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2020-09-18T12:38:38-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2020-09-18T12:38:38-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2020-09-18T12:38:38-07:00</lastmod></url><url><loc>/blog/p
[...]
\ No newline at end of file
