This is an automated email from the ASF dual-hosted git repository.
tvalentyn pushed a change to branch tvalentyn-patch-1
in repository https://gitbox.apache.org/repos/asf/beam.git
omit d1a61707776 Add pytest logging in VC tests.
add be3428f976d Update JavaCC Gradle plugin to latest version (3.0.0)
(#27869)
add 8837c93d642 Re-word line in Octo case study
add 83f09e70682 Merge pull request #27992 from jrmccluskey/caseStudyCleanup
add bbaa7ebd3ee Github Workflow Replacement for Jenkins Job,
beam_PreCommit_SQL_Java17 (Cron, Commit, Phrase) (#27965)
add 822f2e32158 Add pytest logging in VC tests.
add 72a46778396 Remove show-capture
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (d1a61707776)
\
N -- N -- N refs/heads/tvalentyn-patch-1 (72a46778396)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.github/workflows/README.md | 1 +
...QL_Java11.yml => beam_PreCommit_SQL_Java17.yml} | 72 +++++++++++-----------
buildSrc/build.gradle.kts | 1 -
sdks/java/extensions/sql/build.gradle | 2 +-
sdks/java/io/clickhouse/build.gradle | 3 +-
sdks/python/container/run_validatescontainer.sh | 1 -
settings.gradle.kts | 6 ++
website/www/site/content/en/case-studies/octo.md | 2 +-
8 files changed, 46 insertions(+), 42 deletions(-)
copy .github/workflows/{beam_PreCommit_SQL_Java11.yml =>
beam_PreCommit_SQL_Java17.yml} (74%)
