Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Kokoro Job for google-http-java-client
See original GitHub issueThis is my note about how Kokoro job for Linkage Monitor is setup.
One of existing jobs: “cloud-devrel/client-libraries/java/google-http-java-client/presubmit/java8”.
Proposal: create the following files in Piper and google-http-java-client GitHub repository:
Kokoro job config linkage-monitor.cfg
A new Kokoro job config file as a sibling of the java8.cfg in Piper.
Kokoro build config .kokoro/presubmit/linkage-monitor.cfg
A new Kokoro build config file as a sibling of .kokoro/java8.cfg
Similar to .kokoro/presubmit/java8.cfg but having “linkage-monitor.sh” for TRAMPOLINE_BUILD_FILE
.kokoro/linkage-monitor.sh
A new shell script to install snapshot google-http-java-client locally and run linkage monitor.
Similar to .kokoro/build.sh but not running test but running LinkageMonitor.
mvn install -DskipTests
curl http://... linkage-monitor-all-deps.jar # A GCS URL which suztomo will create
java -jar linkage-monitor-all-deps.jar "com.google.cloud:libraries-bom"
Todo: talk this to Elliotte, and then Jeff.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Sounds good to me. Long term, we could possibly package this in a docker image which could have the linkage-monitor and the shell script already included for maximum portability.
It works!