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 aba38e078ec Publishing website 2023/05/11 22:16:48 at commit 2209da6 aba38e078ec is described below commit aba38e078ec783e842907c9a5474d7b109cd2db7 Author: jenkins <bui...@apache.org> AuthorDate: Thu May 11 22:16:49 2023 +0000 Publishing website 2023/05/11 22:16:48 at commit 2209da6 --- website/generated-content/contribute/index.xml | 16 +++++++++++++--- .../contribute/release-guide/index.html | 13 ++++++++++--- .../documentation/sdks/go-cross-compilation/index.html | 7 ++++++- website/generated-content/sitemap.xml | 2 +- 4 files changed, 30 insertions(+), 8 deletions(-) diff --git a/website/generated-content/contribute/index.xml b/website/generated-content/contribute/index.xml index a7aec354bc3..70ca49e76f3 100644 --- a/website/generated-content/contribute/index.xml +++ b/website/generated-content/contribute/index.xml @@ -1404,7 +1404,9 @@ Please review and vote on the release candidate #3 for the version 1.2.3, as fol [ ] +1, Approve the release [ ] -1, Do not approve the release (please provide specific comments) Reviewers are encouraged to test their own use cases with the release candidate, and vote +1 if -no issues are found. +no issues are found. Only PMC member votes will count towards the final vote, but votes from all +community members is encouraged and helpful for finding regressions; you can either test your own +use cases or use cases from the validation sheet [10]. The complete staging area is available for your review, which includes: * GitHub Release notes [1], * the official Apache source release to be deployed to dist.apache.org [2], which is signed with the key with fingerprint FFFFFFFF [3], @@ -1440,8 +1442,11 @@ Proceed to the <code>Fix Issues</code> step below and address the problem. However, some issues don’t require cancellation. For example, if an issue is found in the website pull request, just correct it on the spot and the vote can continue as-is.</p> <h3 id="run-validation-tests">Run validation tests</h3> -<p>All tests listed in this <a href="https://s.apache.org/beam-release-validation">spreadsheet</a></p> -<p>Since there are a bunch of tests, we recommend you running validations using automation script. +<p>The community is responsible for performing validation, but as release manager you are expected to contribute as well. +Before accepting an RC, as a community we try to exercise most (if not all) of the tests listed in this +<a href="https://s.apache.org/beam-release-validation">spreadsheet</a>, and those are good validations for you to try out as release manager. +The goal of these tests is to validate that we&rsquo;re able to run basic pipelines from a variety of environments (not just our CI environment).</p> +<p>Since there are a bunch of tests, we recommend you running some validations using an automation script. In case of script failure, you can still run all of them manually.</p> <p>You may need to have Python interpreters for all supported Python minor versions to run all of the tests. See Python installation tips in <a href="https://cwiki.apache.org/confluence/display/BEAM/Python+Tips#PythonTips-InstallingPythoninterpreters">Developer Wiki</a>.</p> @@ -1460,6 +1465,10 @@ versions to run all of the tests. See Python installation tips in <a href="ht </code></pre></li> </ol> </li> +</ul> +<p><strong>Note:</strong> running the validations requires the ability to do the following in your GCP account: start pipelines, +write to BigQuery, and create a cluster of machines for running containers (for x-lang validation).</p> +<ul> <li> <p><strong>Tasks included</strong></p> <ol> @@ -1494,6 +1503,7 @@ versions to run all of the tests. See Python installation tips in <a href="ht <li>Check whether validations succeed by following console output instructions.</li> <li>Terminate streaming jobs and java injector.</li> <li>Run Java quickstart (wordcount) and mobile game examples with the staged artifacts. The easiest way to do this is by running the tests on Jenkins. +Other manual validation will follow, but this will at least validate that the staged artifacts can be used. <ul> <li>Log in to Jenkins.</li> <li>Go to <a href="https://ci-beam.apache.org/job/beam_PostRelease_NightlySnapshot/">https://ci-beam.apache.org/job/beam_PostRelease_NightlySnapshot/</a>.</li> diff --git a/website/generated-content/contribute/release-guide/index.html b/website/generated-content/contribute/release-guide/index.html index 71a49f5c233..633aac6961e 100644 --- a/website/generated-content/contribute/release-guide/index.html +++ b/website/generated-content/contribute/release-guide/index.html @@ -249,7 +249,9 @@ Please review and vote on the release candidate #3 for the version 1.2.3, as fol Reviewers are encouraged to test their own use cases with the release candidate, and vote +1 if -no issues are found. +no issues are found. Only PMC member votes will count towards the final vote, but votes from all +community members is encouraged and helpful for finding regressions; you can either test your own +use cases or use cases from the validation sheet [10]. The complete staging area is available for your review, which includes: * GitHub Release notes [1], @@ -287,11 +289,16 @@ Release Manager There’s no need to wait 72 hours. Proceed to the <code>Fix Issues</code> step below and address the problem. However, some issues don’t require cancellation. -For example, if an issue is found in the website pull request, just correct it on the spot and the vote can continue as-is.</p><h3 id=run-validation-tests>Run validation tests</h3><p>All tests listed in this <a href=https://s.apache.org/beam-release-validation>spreadsheet</a></p><p>Since there are a bunch of tests, we recommend you running validations using automation script. +For example, if an issue is found in the website pull request, just correct it on the spot and the vote can continue as-is.</p><h3 id=run-validation-tests>Run validation tests</h3><p>The community is responsible for performing validation, but as release manager you are expected to contribute as well. +Before accepting an RC, as a community we try to exercise most (if not all) of the tests listed in this +<a href=https://s.apache.org/beam-release-validation>spreadsheet</a>, and those are good validations for you to try out as release manager. +The goal of these tests is to validate that we’re able to run basic pipelines from a variety of environments (not just our CI environment).</p><p>Since there are a bunch of tests, we recommend you running some validations using an automation script. In case of script failure, you can still run all of them manually.</p><p>You may need to have Python interpreters for all supported Python minor versions to run all of the tests. See Python installation tips in <a href=https://cwiki.apache.org/confluence/display/BEAM/Python+Tips#PythonTips-InstallingPythoninterpreters>Developer Wiki</a>.</p><h4 id=run-validations-using-run_rc_validationsh>Run validations using run_rc_validation.sh</h4><ul><li><p><strong>Script:</strong> <a href=https://github.com/apache/beam/blob/master/release/src/main/scripts/run_rc_validation.sh>run_rc_validation.sh</a></p></li><li><p><strong>Usage</strong></p [...] <a href=https://github.com/apache/beam/blob/master/release/src/main/scripts/script.config>script.config</a></li><li>Then run<pre><code>./beam/release/src/main/scripts/run_rc_validation.sh -</code></pre></li></ol></li><li><p><strong>Tasks included</strong></p><ol><li>Create a PR to trigger Python validation job, including<ul><li>Python quickstart in batch and streaming mode with direct runner and Dataflow runner.</li><li>Python Mobile Games(UserScore, HourlyTeamScore) with direct runner and Dataflow runner.</li></ul></li><li>Run Python Streaming MobileGames, includes<ul><li>Start a new terminal to run Java Pubsub injector.</li><li>Start a new terminal to run Python LeaderBo [...] +</code></pre></li></ol></li></ul><p><strong>Note:</strong> running the validations requires the ability to do the following in your GCP account: start pipelines, +write to BigQuery, and create a cluster of machines for running containers (for x-lang validation).</p><ul><li><p><strong>Tasks included</strong></p><ol><li>Create a PR to trigger Python validation job, including<ul><li>Python quickstart in batch and streaming mode with direct runner and Dataflow runner.</li><li>Python Mobile Games(UserScore, HourlyTeamScore) with direct runner and Dataflow runner.</li></ul></li><li>Run Python Streaming MobileGames, includes<ul><li>Start a new terminal t [...] +Other manual validation will follow, but this will at least validate that the staged artifacts can be used.<ul><li>Log in to Jenkins.</li><li>Go to <a href=https://ci-beam.apache.org/job/beam_PostRelease_NightlySnapshot/>https://ci-beam.apache.org/job/beam_PostRelease_NightlySnapshot/</a>.</li><li>Click “Build with Parameters”.</li><li>Set <code>snapshot_version</code> to <code>2.xx.0</code>, and set <code>snapshot_url</code> to point to the staged artifacts in Maven central [...] -Prepourl=https://repository.apache.org/content/repositories/orgapachebeam-${KEY} \ -Pver=${RELEASE_VERSION} </code></pre><p><strong>Flink Local Runner</strong></p><pre><code>./gradlew :runners:flink:1.13:runQuickstartJavaFlinkLocal \ diff --git a/website/generated-content/documentation/sdks/go-cross-compilation/index.html b/website/generated-content/documentation/sdks/go-cross-compilation/index.html index 53f95a01ac0..74db352f552 100644 --- a/website/generated-content/documentation/sdks/go-cross-compilation/index.html +++ b/website/generated-content/documentation/sdks/go-cross-compilation/index.html @@ -40,8 +40,13 @@ $ ./output/launcher --worker_binary=output/worker --runner=flink --endpoint=... </code></pre><h1 id=sdk-containers>SDK Containers</h1><p>Apache Beam releases <a href=documentation/runtime/environments/>SDK specific containers</a> for runners to use to launch workers. These containers provision and initialize the worker binary as appropriate for the SDK.</p><p>At present, Go SDK worker containers are only built for the <code>linux-amd64</code> platform. See <a href=https://github.com/apache/beam/issues/20807>Issue 20807</a> for the current state of ARM64 container support.</p><p>Because Go is statically compiled, there are no runtime dependencies on a specific Go version for a container. +However, depending on how your binary is built, the The Go release used to compile your binary will be what your workers execute. -Be sure to update to a recent <a href=https://go.dev/doc/devel/release>Go release</a> for best performance.</p></div></div><footer class=footer><div class=footer__contained><div class=footer__cols><div class="footer__cols__col footer__cols__col__logos"><div class=footer__cols__col__logo><img src=/images/beam_logo_circle.svg class=footer__logo alt="Beam logo"></div><div class=footer__cols__col__logo><img src=/images/apache_logo_circle.svg class=footer__logo alt="Apache logo"></div></div>< [...] +Be sure to update to a recent <a href=https://go.dev/doc/devel/release>Go release</a> for best performance.</p><h1 id=cg0_enabled0-and-glibc>CG0_ENABLED=0 and glibc</h1><p>From Beam 2.48.0, the default cross compile sets CGO_ENABLED=0 to reduce issues with the boot container and glibc versions. +If your pipeline requires CGO to run, see the above Overriding the Worker Binary for more information on using your own built binary.</p><p>Beam uses minimal debian containers as a base. +If your binary has specific execution requirements, <a href=documentation/runtime/environments/>Custom Containers</a> can be derieved from the released +containers to satisfy them. +Use custom containers to resolve glibc mismatches, or requiring additional binaries to be available at execution time.</p></div></div><footer class=footer><div class=footer__contained><div class=footer__cols><div class="footer__cols__col footer__cols__col__logos"><div class=footer__cols__col__logo><img src=/images/beam_logo_circle.svg class=footer__logo alt="Beam logo"></div><div class=footer__cols__col__logo><img src=/images/apache_logo_circle.svg class=footer__logo alt="Apache logo"></ [...] <a href=https://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 class="footer__cols__col footer__cols__col__logos"><div class=footer__cols__col--group><div class=footer__cols__col__logo><a href=https://github.com/apache/beam><im [...] \ No newline at end of file diff --git a/website/generated-content/sitemap.xml b/website/generated-content/sitemap.xml index 178a75a461a..fb08973ce9f 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.47.0/</loc><lastmod>2023-05-11T11:24:28-04:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-05-11T11:24:28-04:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-05-11T11:24:28-04:00</lastmod></url><url><loc>/categories/</loc><lastmod>2023-05-11T11:24:28-04:00</lastmod></url><url><loc>/catego [...] \ 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.47.0/</loc><lastmod>2023-05-11T11:16:13-07:00</lastmod></url><url><loc>/categories/blog/</loc><lastmod>2023-05-11T11:16:13-07:00</lastmod></url><url><loc>/blog/</loc><lastmod>2023-05-11T11:16:13-07:00</lastmod></url><url><loc>/categories/</loc><lastmod>2023-05-11T11:16:13-07:00</lastmod></url><url><loc>/catego [...] \ No newline at end of file