ci: simplify local install command (no need to review) #868
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Warning: This pull request is touching the following templated files:
|
google-cla
bot
added
the
cla: yes
product-auto-label
bot
added
the
api: spanner
Codecov Report
@@ Coverage Diff @@
## master #868 +/- ##
============================================
- Coverage 85.12% 83.11% -2.01%
+ Complexity 2588 2495 -93
============================================
Files 143 143
Lines 14154 11407 -2747
Branches 1366 1116 -250
============================================
- Hits 12048 9481 -2567
+ Misses 1537 1406 -131
+ Partials 569 520 -49 Continue to review full report at Codecov.
|
gcf-merge-on-green bot
pushed a commit
to googleapis/synthtool
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded.
yoshi-automation
added a commit
to googleapis/java-accesscontextmanager
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-aiplatform
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-analytics-admin
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-analytics-data
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-billing
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-asset
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-recommendations-ai
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-servicedirectory
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-shared-dependencies
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-billingbudgets
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-texttospeech
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-assured-workloads
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-recommender
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-channel
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-cloud-bom
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-document-ai
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: #868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-spanner-jdbc
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-errorreporting
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-redis
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-cloudbuild
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-resourcemanager
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-containeranalysis
that referenced
this pull request
Feb 16, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-dlp
that referenced
this pull request
Feb 17, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-dns
that referenced
this pull request
Feb 17, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
eaball35
pushed a commit
to googleapis/java-dns
that referenced
this pull request
Feb 17, 2021
* ci: linkage monitor CI job to use build.sh This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b * chore: update cloud-rad buckets doclava v2 => staging docFX v3 => prod Source-Author: Emily Ball <emilyball@google.com> Source-Date: Tue Feb 16 17:02:08 2021 -0800 Source-Repo: googleapis/synthtool Source-Sha: b416a7befcdbc42de41cf387dcf428f894fb812b Source-Link: googleapis/synthtool@b416a7b
eaball35
pushed a commit
to googleapis/java-dlp
that referenced
this pull request
Feb 17, 2021
* ci: linkage monitor CI job to use build.sh This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b * chore: update cloud-rad buckets doclava v2 => staging docFX v3 => prod Source-Author: Emily Ball <emilyball@google.com> Source-Date: Tue Feb 16 17:02:08 2021 -0800 Source-Repo: googleapis/synthtool Source-Sha: b416a7befcdbc42de41cf387dcf428f894fb812b Source-Link: googleapis/synthtool@b416a7b
eaball35
pushed a commit
to googleapis/java-dialogflow-cx
that referenced
this pull request
Feb 17, 2021
* ci: linkage monitor CI job to use build.sh This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b * chore: update cloud-rad buckets doclava v2 => staging docFX v3 => prod Source-Author: Emily Ball <emilyball@google.com> Source-Date: Tue Feb 16 17:02:08 2021 -0800 Source-Repo: googleapis/synthtool Source-Sha: b416a7befcdbc42de41cf387dcf428f894fb812b Source-Link: googleapis/synthtool@b416a7b
yoshi-automation
added a commit
to googleapis/google-auth-library-java
that referenced
this pull request
Feb 17, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/google-http-java-client
that referenced
this pull request
Feb 17, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/google-oauth-java-client
that referenced
this pull request
Feb 17, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-translate
that referenced
this pull request
Feb 17, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-analytics-admin
that referenced
this pull request
Feb 17, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-analytics-admin
that referenced
this pull request
Feb 17, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-analytics-data
that referenced
this pull request
Feb 17, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-analytics-data
that referenced
this pull request
Feb 17, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-notebooks
that referenced
this pull request
Feb 17, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-game-servers
that referenced
this pull request
Feb 17, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
chingor13
pushed a commit
to googleapis/google-oauth-java-client
that referenced
this pull request
Feb 18, 2021
* changes without context
autosynth cannot find the source of changes triggered by earlier changes in this
repository, or by version upgrades to tools such as linters.
* build: migrate to flakybot
Source-Author: Justin Beckwith <justin.beckwith@gmail.com>
Source-Date: Thu Jan 28 22:22:38 2021 -0800
Source-Repo: googleapis/synthtool
Source-Sha: d1bb9173100f62c0cfc8f3138b62241e7f47ca6a
Source-Link: googleapis/synthtool@d1bb917
* build(java): generate docfx yml on release
* feat: generate docfx yml on release
* fix: updates name variable
* fix: remove non needed resource
* fix: update date
Source-Author: Emily Ball <emilyball@google.com>
Source-Date: Mon Feb 1 15:24:59 2021 -0800
Source-Repo: googleapis/synthtool
Source-Sha: 5de29e9434b63ea6d7e46dc348521c62969af1a1
Source-Link: googleapis/synthtool@5de29e9
* build(java): run linkage monitor as GitHub action
Source-Author: Tomo Suzuki <suztomo@google.com>
Source-Date: Tue Feb 2 16:20:26 2021 -0500
Source-Repo: googleapis/synthtool
Source-Sha: e935c9ecb47da0f2e054f5f1845f7cf7c95fa625
Source-Link: googleapis/synthtool@e935c9e
* build(java): update autorelease branch name check
In response to the new multi release branch changes.
Source-Author: Stephanie Wang <stephaniewang526@users.noreply.github.com>
Source-Date: Wed Feb 3 15:06:07 2021 -0500
Source-Repo: googleapis/synthtool
Source-Sha: 140ba24a136c63e7f10a998a63e7898aed63ea7d
Source-Link: googleapis/synthtool@140ba24
* chore: remove leading newline from LICENSE
Co-authored-by: Christopher Wilcox <crwilcox@google.com>
Source-Author: Justin Beckwith <justin.beckwith@gmail.com>
Source-Date: Wed Feb 3 15:37:31 2021 -0800
Source-Repo: googleapis/synthtool
Source-Sha: 27b2d4f4674840628d0b75c5941e89c12af4764f
Source-Link: googleapis/synthtool@27b2d4f
* fix: update repo name
java-memcache set for all accidentally
Source-Author: Emily Ball <emilyball@google.com>
Source-Date: Thu Feb 4 10:39:41 2021 -0800
Source-Repo: googleapis/synthtool
Source-Sha: 692715c0f23a7bb3bfbbaa300f7620ddfa8c47e5
Source-Link: googleapis/synthtool@692715c
* build(java): update autorelease script
Noticed the workflow was getting skipped on all the release PRs. Updating due to recent update in release-please branch name.
Source-Author: Stephanie Wang <stephaniewang526@users.noreply.github.com>
Source-Date: Tue Feb 9 19:10:03 2021 -0500
Source-Repo: googleapis/synthtool
Source-Sha: 2414b817065726eae0bc525346c7e874f969369d
Source-Link: googleapis/synthtool@2414b81
* ci: linkage monitor CI job to use build.sh
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!)
Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository.
# How did I test?
I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868
<img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png">
It succeeded.
Source-Author: Tomo Suzuki <suztomo@google.com>
Source-Date: Tue Feb 16 15:56:09 2021 -0500
Source-Repo: googleapis/synthtool
Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c
Source-Link: googleapis/synthtool@f327d3b
* chore: update cloud-rad buckets
doclava v2 => staging
docFX v3 => prod
Source-Author: Emily Ball <emilyball@google.com>
Source-Date: Tue Feb 16 17:02:08 2021 -0800
Source-Repo: googleapis/synthtool
Source-Sha: b416a7befcdbc42de41cf387dcf428f894fb812b
Source-Link: googleapis/synthtool@b416a7b
eaball35
pushed a commit
to googleapis/java-analytics-data
that referenced
this pull request
Feb 18, 2021
* changes without context
autosynth cannot find the source of changes triggered by earlier changes in this
repository, or by version upgrades to tools such as linters.
* chore: migrate maps/routes onto the {Java,Python} microgenerators
Committer: @miraleung
PiperOrigin-RevId: 357773363
Source-Link: googleapis/googleapis@a3b60b0
Source-Author: Bazel Bot <bazel-bot-development[bot]@users.noreply.github.com>
Source-Date: Tue Feb 16 20:29:44 2021 +0000
Source-Repo: googleapis/googleapis-gen
Source-Sha: c2f406125475d4df75373708747e1d87ba50f345
Source-Link: googleapis/googleapis-gen@c2f4061
* ci: linkage monitor CI job to use build.sh
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!)
Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository.
# How did I test?
I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868
<img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png">
It succeeded.
Source-Author: Tomo Suzuki <suztomo@google.com>
Source-Date: Tue Feb 16 15:56:09 2021 -0500
Source-Repo: googleapis/synthtool
Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c
Source-Link: googleapis/synthtool@f327d3b
* chore: update cloud-rad buckets
doclava v2 => staging
docFX v3 => prod
Source-Author: Emily Ball <emilyball@google.com>
Source-Date: Tue Feb 16 17:02:08 2021 -0800
Source-Repo: googleapis/synthtool
Source-Sha: b416a7befcdbc42de41cf387dcf428f894fb812b
Source-Link: googleapis/synthtool@b416a7b
* chore(deps): update dependency google-api-core to v1.26.0
Co-authored-by: Jeffrey Rennie <rennie@google.com>
Co-authored-by: Elliotte Rusty Harold <elharo@users.noreply.github.com>
Source-Author: WhiteSource Renovate <bot@renovateapp.com>
Source-Date: Wed Feb 17 17:10:46 2021 +0100
Source-Repo: googleapis/synthtool
Source-Sha: 0973d57c09011609a283e82470a44110efb4ccf4
Source-Link: googleapis/synthtool@0973d57
* build(python): enable flakybot on library unit and system tests
Source-Author: Bu Sun Kim <8822365+busunkim96@users.noreply.github.com>
Source-Date: Wed Feb 17 14:10:46 2021 -0700
Source-Repo: googleapis/synthtool
Source-Sha: d17674372e27fb8f23013935e794aa37502071aa
Source-Link: googleapis/synthtool@d176743
eaball35
pushed a commit
to googleapis/java-analytics-admin
that referenced
this pull request
Feb 18, 2021
* changes without context
autosynth cannot find the source of changes triggered by earlier changes in this
repository, or by version upgrades to tools such as linters.
* chore: migrate maps/routes onto the {Java,Python} microgenerators
Committer: @miraleung
PiperOrigin-RevId: 357773363
Source-Link: googleapis/googleapis@a3b60b0
Source-Author: Bazel Bot <bazel-bot-development[bot]@users.noreply.github.com>
Source-Date: Tue Feb 16 20:29:44 2021 +0000
Source-Repo: googleapis/googleapis-gen
Source-Sha: c2f406125475d4df75373708747e1d87ba50f345
Source-Link: googleapis/googleapis-gen@c2f4061
* ci: linkage monitor CI job to use build.sh
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!)
Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository.
# How did I test?
I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868
<img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png">
It succeeded.
Source-Author: Tomo Suzuki <suztomo@google.com>
Source-Date: Tue Feb 16 15:56:09 2021 -0500
Source-Repo: googleapis/synthtool
Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c
Source-Link: googleapis/synthtool@f327d3b
* chore: update cloud-rad buckets
doclava v2 => staging
docFX v3 => prod
Source-Author: Emily Ball <emilyball@google.com>
Source-Date: Tue Feb 16 17:02:08 2021 -0800
Source-Repo: googleapis/synthtool
Source-Sha: b416a7befcdbc42de41cf387dcf428f894fb812b
Source-Link: googleapis/synthtool@b416a7b
* chore(deps): update dependency google-api-core to v1.26.0
Co-authored-by: Jeffrey Rennie <rennie@google.com>
Co-authored-by: Elliotte Rusty Harold <elharo@users.noreply.github.com>
Source-Author: WhiteSource Renovate <bot@renovateapp.com>
Source-Date: Wed Feb 17 17:10:46 2021 +0100
Source-Repo: googleapis/synthtool
Source-Sha: 0973d57c09011609a283e82470a44110efb4ccf4
Source-Link: googleapis/synthtool@0973d57
* build(python): enable flakybot on library unit and system tests
Source-Author: Bu Sun Kim <8822365+busunkim96@users.noreply.github.com>
Source-Date: Wed Feb 17 14:10:46 2021 -0700
Source-Repo: googleapis/synthtool
Source-Sha: d17674372e27fb8f23013935e794aa37502071aa
Source-Link: googleapis/synthtool@d176743
chingor13
pushed a commit
to googleapis/java-shared-dependencies
that referenced
this pull request
Feb 19, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-shared-config
that referenced
this pull request
Feb 19, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
chingor13
pushed a commit
to googleapis/java-notebooks
that referenced
this pull request
Feb 19, 2021
* chore: adding docfx doclet resource * chore: updating publish_javadoc to support docfx yml generation * fix: reducing commit Source-Author: Emily Ball <emilyball@google.com> Source-Date: Mon Jan 25 13:29:09 2021 -0800 Source-Repo: googleapis/synthtool Source-Sha: 3816b080296d4d52975079fd26c110dd26ba25af Source-Link: googleapis/synthtool@3816b08 * build: migrate to flakybot Source-Author: Justin Beckwith <justin.beckwith@gmail.com> Source-Date: Thu Jan 28 22:22:38 2021 -0800 Source-Repo: googleapis/synthtool Source-Sha: d1bb9173100f62c0cfc8f3138b62241e7f47ca6a Source-Link: googleapis/synthtool@d1bb917 * build(java): generate docfx yml on release * feat: generate docfx yml on release * fix: updates name variable * fix: remove non needed resource * fix: update date Source-Author: Emily Ball <emilyball@google.com> Source-Date: Mon Feb 1 15:24:59 2021 -0800 Source-Repo: googleapis/synthtool Source-Sha: 5de29e9434b63ea6d7e46dc348521c62969af1a1 Source-Link: googleapis/synthtool@5de29e9 * build(java): run linkage monitor as GitHub action Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 2 16:20:26 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: e935c9ecb47da0f2e054f5f1845f7cf7c95fa625 Source-Link: googleapis/synthtool@e935c9e * build(java): update autorelease branch name check In response to the new multi release branch changes. Source-Author: Stephanie Wang <stephaniewang526@users.noreply.github.com> Source-Date: Wed Feb 3 15:06:07 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: 140ba24a136c63e7f10a998a63e7898aed63ea7d Source-Link: googleapis/synthtool@140ba24 * chore: remove leading newline from LICENSE Co-authored-by: Christopher Wilcox <crwilcox@google.com> Source-Author: Justin Beckwith <justin.beckwith@gmail.com> Source-Date: Wed Feb 3 15:37:31 2021 -0800 Source-Repo: googleapis/synthtool Source-Sha: 27b2d4f4674840628d0b75c5941e89c12af4764f Source-Link: googleapis/synthtool@27b2d4f * fix: update repo name java-memcache set for all accidentally Source-Author: Emily Ball <emilyball@google.com> Source-Date: Thu Feb 4 10:39:41 2021 -0800 Source-Repo: googleapis/synthtool Source-Sha: 692715c0f23a7bb3bfbbaa300f7620ddfa8c47e5 Source-Link: googleapis/synthtool@692715c * build(java): update autorelease script Noticed the workflow was getting skipped on all the release PRs. Updating due to recent update in release-please branch name. Source-Author: Stephanie Wang <stephaniewang526@users.noreply.github.com> Source-Date: Tue Feb 9 19:10:03 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: 2414b817065726eae0bc525346c7e874f969369d Source-Link: googleapis/synthtool@2414b81 * ci: linkage monitor CI job to use build.sh This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b * chore: update cloud-rad buckets doclava v2 => staging docFX v3 => prod Source-Author: Emily Ball <emilyball@google.com> Source-Date: Tue Feb 16 17:02:08 2021 -0800 Source-Repo: googleapis/synthtool Source-Sha: b416a7befcdbc42de41cf387dcf428f894fb812b Source-Link: googleapis/synthtool@b416a7b
chingor13
pushed a commit
to googleapis/java-shared-config
that referenced
this pull request
Feb 22, 2021
* ci: linkage monitor CI job to use build.sh This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b * chore: update cloud-rad buckets doclava v2 => staging docFX v3 => prod Source-Author: Emily Ball <emilyball@google.com> Source-Date: Tue Feb 16 17:02:08 2021 -0800 Source-Repo: googleapis/synthtool Source-Sha: b416a7befcdbc42de41cf387dcf428f894fb812b Source-Link: googleapis/synthtool@b416a7b * fix: don't log downloads @chingor13 This change keeps Maven 3.6.1 and later from spamming our CI logs with page after page of lists of artifacts it's downloading that makes it much harder to find the actual test output. Source-Author: Elliotte Rusty Harold <elharo@users.noreply.github.com> Source-Date: Thu Feb 18 19:58:59 2021 +0000 Source-Repo: googleapis/synthtool Source-Sha: 1aeca92e4a38f47134cb955f52ea76f84f09ff88 Source-Link: googleapis/synthtool@1aeca92 * build: reduce download junk in log files * fix: less download junk log files * Update build.sh Source-Author: Elliotte Rusty Harold <elharo@users.noreply.github.com> Source-Date: Fri Feb 19 01:42:29 2021 +0000 Source-Repo: googleapis/synthtool Source-Sha: 6946fd71ae9215b0e7ae188f5057df765ee6d7d2 Source-Link: googleapis/synthtool@6946fd7
yoshi-automation
added a commit
to googleapis/java-orgpolicy
that referenced
this pull request
Feb 22, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/google-http-java-client
that referenced
this pull request
Feb 23, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
chingor13
pushed a commit
to googleapis/java-gcloud-maven-plugin
that referenced
this pull request
Feb 25, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-artifact-registry
that referenced
this pull request
Mar 4, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-artifact-registry
that referenced
this pull request
Mar 10, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
yoshi-automation
added a commit
to googleapis/java-domains
that referenced
this pull request
Mar 10, 2021
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
suztomo
pushed a commit
to googleapis/sdk-platform-java
that referenced
this pull request
Mar 21, 2023
This PR updates the GitHub Actions configuration for Linkage Monitor. Before this change, the CI configuration has "mvn install" command with 6 options. It turned out that a slight difference in the command line option from "build.sh" fails the build in google-auth-library-java repository (GoogleCloudPlatform/cloud-opensource-java#1941). (@Neenu1995 found the build failure. Thanks!) Therefore, this change updates the configuration so that Linkage Monitor job just uses "build.sh" to install the artifacts into local Maven repository. # How did I test? I tested this change in java-spanner repository with this draft PR: googleapis/java-spanner#868 <img width="889" alt="Screen Shot 2021-02-12 at 16 54 18" src="https://user-images.githubusercontent.com/28604/107826467-f3cd5c80-6d52-11eb-86f1-1a8053326978.png"> It succeeded. Source-Author: Tomo Suzuki <suztomo@google.com> Source-Date: Tue Feb 16 15:56:09 2021 -0500 Source-Repo: googleapis/synthtool Source-Sha: f327d3b657a63ae4a8efd7f011a15eacae36b59c Source-Link: googleapis/synthtool@f327d3b
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
Fixes #<issue_number_goes_here> ☕️