Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Linkage Monitor fails to run google-auth-library-java repository #1941

Closed
suztomo opened this issue Feb 12, 2021 · 1 comment
Closed

Linkage Monitor fails to run google-auth-library-java repository #1941

suztomo opened this issue Feb 12, 2021 · 1 comment

Comments

@suztomo
Copy link
Contributor

suztomo commented Feb 12, 2021 •
edited
Loading

https://github.com/googleapis/google-auth-library-java/pull/554/checks?check_run_id=1818423838 fails:

Error:  Failed to execute goal on project google-auth-library-appengine: Could not resolve dependencies for project 
com.google.auth:google-auth-library-appengine:jar:0.23.1-SNAPSHOT: Could not find artifact com.google.auth:google-auth-
library-oauth2-http:jar:tests:0.23.1-SNAPSHOT -> [Help 1]

CC: @Neenu1995

Investigation

The job failed at "Install artifacts to local Maven repository" phase. It means the Linkage Monitor has not run yet. Does the repository require special command to install? Any difference in build.sh?

In my MacBook Pro

suztomo-macbookpro44% mvn install -B -V \
          -Dmaven.test.skip -DskipTests=true \
          -Dclirr.skip=true \
          -Denforcer.skip=true \
          -Dmaven.javadoc.skip=true \
          -Dgcloud.download.skip=true
...
[INFO] -----------< com.google.auth:google-auth-library-appengine >------------
[INFO] Building Google Auth Library for Java - Google App Engine 0.23.1-SNAPSHOT [4/5]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for Google Auth Library for Java 0.23.1-SNAPSHOT:
[INFO] 
[INFO] Google Auth Library for Java ....................... SUCCESS [  3.459 s]
[INFO] Google Auth Library for Java - Credentials ......... SUCCESS [  3.656 s]
[INFO] Google Auth Library for Java - OAuth2 HTTP ......... SUCCESS [  3.608 s]
[INFO] Google Auth Library for Java - Google App Engine ... FAILURE [  0.020 s]
[INFO] Google Auth Library for Java BOM ................... SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  12.053 s
[INFO] Finished at: 2021-02-12T15:55:14-05:00
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal on project google-auth-library-appengine: Could not resolve dependencies for project com.google.auth:google-auth-library-appengine:jar:0.23.1-SNAPSHOT: Could not find artifact com.google.auth:google-auth-library-oauth2-http:jar:tests:0.23.1-SNAPSHOT -> [Help 1]
[ERROR]

This works:

mvn clean install -B -V \
    -DskipTests=true \
    -Dclirr.skip=true \
    -Denforcer.skip=true \
    -Dmaven.javadoc.skip=true \
    -Dgcloud.download.skip=true \
    -T 1C

The maven.test.skip interfering the test artifact generation. I thought the parameter would just speedup the build without compiling test Java sources.

But in java-spanner repository, passing -DskipTests=true still executes tests. The repository uses a special property "skipUTs" to control unit tests.

suztomo@suztomo:~/java-spanner$ mvn install -B -V  -DskipUTs=true -DskipTests=true \
     -Dclirr.skip=true     -Denforcer.skip=true     -Dmaven.javadoc.skip=true \
     -Dgcloud.download.skip=true     -T 1C
@suztomo suztomo mentioned this issue Feb 12, 2021
Merged
gcf-merge-on-green bot pushed a commit to googleapis/synthtool that referenced this issue Feb 16, 2021
@suztomo
ci: linkage monitor CI job to use build.sh (#947)
f327d3b 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
05ffa3a 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
67d4e8a 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
1d48d00 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
4c1772d 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
469d454 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
dfeed07 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
fb3acc9 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
3e52fa0 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
af6cb4a 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
a91209a 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
1da5267 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
4d5a892 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
ed39de7 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
4411005 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
d6d0fab 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
00a72b5 
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-spanner that referenced this issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
17afae5 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
866d886 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
73bb43a 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
273d838 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
5b9be4c 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
c678508 
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 issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
8e182bc 
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-core that referenced this issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
15d6f50 
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-automl that referenced this issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
9d5dcea 
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-bigquery that referenced this issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
ff03705 
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-speech that referenced this issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
3b0a386 
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-notification that referenced this issue Feb 16, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
62ad6eb 
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 issue Feb 17, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
98b232b 
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 issue Feb 17, 2021
@yoshi-automation
chore: Re-generated to pick up changes from synthtool (#317)
c7857c9 
* 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 issue Feb 17, 2021
@yoshi-automation
chore: Re-generated to pick up changes from synthtool (#428)
f8e00fd 
* 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 issue Feb 17, 2021
@yoshi-automation
chore: Re-generated to pick up changes from synthtool (#142)
5411cd0 
* 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 issue Feb 17, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
9f10596 
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 issue Feb 17, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
33c92a6 
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 issue Feb 17, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
7afd68b 
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 issue Feb 17, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
dffc4f9 
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 issue Feb 17, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
5e1e79f 
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 issue Feb 17, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
3251fe9 
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 issue Feb 17, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
4b3322e 
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 issue Feb 17, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
eaf3e7d 
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 issue Feb 17, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
adee288 
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 issue Feb 17, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
db14233 
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 issue Feb 18, 2021
@yoshi-automation
chore: regenerate common templates (#629)
d67824e 
* 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 issue Feb 18, 2021
@yoshi-automation
chore: Re-generated to pick up changes from synthtool (#146)
8d8ef02 
* 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 issue Feb 18, 2021
@yoshi-automation
chore: Re-generated to pick up changes from synthtool (#163)
8dcace2 
* 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 issue Feb 19, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh (#276)
55cf226 
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 issue Feb 19, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
11ce924 
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 issue Feb 19, 2021
@yoshi-automation
chore: regenerate common templates (#123)
24bade5 
* 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 issue Feb 22, 2021
@yoshi-automation
chore: regenerate common templates (#229)
3be9dcb 
* 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 issue Feb 22, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
d947b50 
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 issue Feb 23, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
97acec8 
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 issue Feb 25, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh (#107)
99ce526 
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 issue Mar 4, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
4f73b0c 
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 issue Mar 10, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
919743c 
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 issue Mar 10, 2021
@yoshi-automation
ci: linkage monitor CI job to use build.sh
1d52827 
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
@elharo
Copy link
Contributor

elharo commented Jul 22, 2021

This seems to be fixed.

@elharo elharo closed this as completed Jul 22, 2021
suztomo pushed a commit to googleapis/sdk-platform-java that referenced this issue Mar 21, 2023
@yoshi-automation
ci: linkage monitor CI job to use build.sh (#276)
bd353ed 
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
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@suztomo @elharo