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 038c864f1b3 Publishing website 2023/05/03 22:17:14 at commit 03ecb15
038c864f1b3 is described below
commit 038c864f1b3544d50f55c89c013fba8899b696c9
Author: jenkins <bui...@apache.org>
AuthorDate: Wed May 3 22:17:14 2023 +0000
Publishing website 2023/05/03 22:17:14 at commit 03ecb15
---
website/generated-content/contribute/index.xml | 23 +++++++++++-----------
.../contribute/release-guide/index.html | 15 +++++++-------
website/generated-content/sitemap.xml | 2 +-
3 files changed, 19 insertions(+), 21 deletions(-)
diff --git a/website/generated-content/contribute/index.xml
b/website/generated-content/contribute/index.xml
index 18a1f86ba0b..60f7c0e38e5 100644
--- a/website/generated-content/contribute/index.xml
+++ b/website/generated-content/contribute/index.xml
@@ -946,7 +946,8 @@ The final state of the repository should match this
diagram:</p>
<li>The Dataflow container image should be modified to the version to be
released.</li>
</ul>
<p>This will all be accomplished by the <a
href="https://github.com/apache/beam/actions/workflows/cut_release_branch.yml";>cut_release_branch</a>
-workflow.</p>
+workflow. This workflow will also update <a
href="https://github.com/apache/beam/blob/master/release/src/main/scripts/mass_comment.py";>mass_comment.py</a>
+to contain all of the active Jenkins jobs.</p>
<p>After updating the master branch, the workflow will also start a build of
<a href="https://ci-beam.apache.org/job/beam_Release_NightlySnapshot/";>the
nightly snapshot</a> against master branch.
Some processes, including our archetype tests, rely on having a live SNAPSHOT
of the current version from the <code>master</code> branch.
@@ -954,11 +955,13 @@ Once the release branch is cut, these SNAPSHOT versions
are no longer found, so
The workflow starts the nightly snapshot by creating an empty PR against
apache:master (which will be linked to in the logs).</p>
<h4 id="use-cut_release_branchsh-to-cut-a-release-branch">Use
cut_release_branch.sh to cut a release branch</h4>
<ul>
-<li>
-<p><strong>Action:</strong> <a
href="https://github.com/apache/beam/actions/workflows/cut_release_branch.yml";>cut_release_branch</a>
(click <code>run workflow</code>)</p>
-</li>
-<li>
-<p>Tasks you need to do manually to <strong>verify the SNAPSHOT
build</strong></p>
+<li><strong>Action:</strong> <a
href="https://github.com/apache/beam/actions/workflows/cut_release_branch.yml";>cut_release_branch</a>
(click <code>run workflow</code>)</li>
+</ul>
+<p>In order to run this workflow, you will need to provide a Jenkins
username and API token. Your Jenkins username should be your Apache ID.
+Your Jenkins API token can be generated by visiting <a
href="https://ci-beam.apache.org/user/";>https://ci-beam.apache.org/user/</a><your
Jenkins username>/configure and clicking
+<code>Add new token</code> in the API token section.</p>
+<ul>
+<li>Tasks you need to do manually to <strong>verify the SNAPSHOT
build</strong>
<ol>
<li>Check whether the Jenkins job gets triggered. If not, please comment
<code>Run Gradle Publish</code> into the generated PR.</li>
<li>After verifying build succeeded, you need to close PR manually.</li>
@@ -990,12 +993,8 @@ You only need to enable &ldquo;repo&rdquo;
permissions to this token.<
<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. 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>
+See <a
href="https://github.com/apache/beam/blob/master/release/src/main/scripts/jenkins_jobs.txt";>jenkins_jobs.txt</a>
+for a full list of phrases.</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 6b7a99fea31..aa099397932 100644
--- a/website/generated-content/contribute/release-guide/index.html
+++ b/website/generated-content/contribute/release-guide/index.html
@@ -86,11 +86,14 @@ The role of the release manager is to file GitHub issues
for each regression wit
The release manager oversees these just like any other issue marked with the
milestone of the release.</p><p>The mailing list should be informed to allow
fixing the regressions in the course of the release.</p><h2
id=5-create-a-release-branch-in-apachebeam-repository>5. Create a release
branch in apache/beam repository</h2><p>Attention: Only committer has
permission to create release branch in apache/beam.</p><p>Release candidates
are built from a release branch.
As a final step in preparation for the release, you should create the release
branch, push it to the Apache code repository, and update version information
on the original branch.
The final state of the repository should match this diagram:</p><img
src=/images/cut-release-branch.png alt="Increment minor version on master
branch and set Dataflow container version on release branch" width=100%><p>The
key points to know:</p><ul><li>The <code>master</code> branch has the
SNAPSHOT/dev version incremented.</li><li>The release branch has the
SNAPSHOT/dev version to be released.</li><li>The Dataflow container image
should be modified to the version to be released.</li></u [...]
-workflow.</p><p>After updating the master branch, the workflow will also start
a build of
+workflow. This workflow will also update <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/mass_comment.py>mass_comment.py</a>
+to contain all of the active Jenkins jobs.</p><p>After updating the master
branch, the workflow will also start a build of
<a href=https://ci-beam.apache.org/job/beam_Release_NightlySnapshot/>the
nightly snapshot</a> against master branch.
Some processes, including our archetype tests, rely on having a live SNAPSHOT
of the current version from the <code>master</code> branch.
Once the release branch is cut, these SNAPSHOT versions are no longer found,
so builds will be broken until a new snapshot is available.
-The workflow starts the nightly snapshot by creating an empty PR against
apache:master (which will be linked to in the logs).</p><h4
id=use-cut_release_branchsh-to-cut-a-release-branch>Use cut_release_branch.sh
to cut a release branch</h4><ul><li><p><strong>Action:</strong> <a
href=https://github.com/apache/beam/actions/workflows/cut_release_branch.yml>cut_release_branch</a>
(click <code>run workflow</code>)</p></li><li><p>Tasks you need to do manually
to <strong>verify the SNAPSHOT buil [...]
+The workflow starts the nightly snapshot by creating an empty PR against
apache:master (which will be linked to in the logs).</p><h4
id=use-cut_release_branchsh-to-cut-a-release-branch>Use cut_release_branch.sh
to cut a release branch</h4><ul><li><strong>Action:</strong> <a
href=https://github.com/apache/beam/actions/workflows/cut_release_branch.yml>cut_release_branch</a>
(click <code>run workflow</code>)</li></ul><p>In order to run this workflow,
you will need to provide a Jenkins usern [...]
+Your Jenkins API token can be generated by visiting <a
href=https://ci-beam.apache.org/user/>https://ci-beam.apache.org/user/</a><your
jenkins username>/configure and clicking
+<code>Add new token</code> in the API token section.</p><ul><li>Tasks you need
to do manually to <strong>verify the SNAPSHOT build</strong><ol><li>Check
whether the Jenkins job gets triggered. If not, please comment <code>Run Gradle
Publish</code> into the generated PR.</li><li>After verifying build succeeded,
you need to close PR manually.</li><li>Manually update <code>CHANGES.md</code>
on <code>master</code> by adding a new section for the next release (<a
href=https://github.com/apach [...]
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><strong>Script:</strong> <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/verify_releas
[...]
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.
@@ -98,12 +101,8 @@ You only need to enable “repo” permissions to
this token.</li><li>Up
</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. 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>.
+See <a
href=https://github.com/apache/beam/blob/master/release/src/main/scripts/jenkins_jobs.txt>jenkins_jobs.txt</a>
+for a 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>.
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
diff --git a/website/generated-content/sitemap.xml
b/website/generated-content/sitemap.xml
index 88199f7a89c..2d8c14c6a24 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>/case-studies/booking/</loc><lastmod>2023-05-03T10:38:11-04:00</lastmod></url><url><loc>/blog/beam-2.46.0/</loc><lastmod>2023-05-03T10:38:11-04:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-05-03T10:38:11-04:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-05-03T10:38:11-04:00</lastmod></url><url><l
[...]
\ 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>/case-studies/booking/</loc><lastmod>2023-05-03T16:51:10-04:00</lastmod></url><url><loc>/blog/beam-2.46.0/</loc><lastmod>2023-05-03T16:51:10-04:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-05-03T16:51:10-04:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-05-03T16:51:10-04:00</lastmod></url><url><l
[...]
\ No newline at end of file
