Jib Gradle plugin disables Google HTTP Client logging

[chanseokoh]

There have been many reports that Gradle users have difficulty generating Google HTTP Client logging following our instructions.

• Unable to push to harbor image with http #1917 (comment)
• com.google.cloud.tools.jib.plugins.common.BuildStepsExecutionException: Connection reset #2335 (comment)
• Building docker image of spring boot #2207 (comment)

From my cursory experiment, this symptom has gotten worse with more recent Gradle. This is in line with the first report that downgrading to 4.10.3 worked.

The cause was our calling TaskCommon.disableHttpLogging().

Some interesting observations:

• Looks like disableHttpLogging() has a lasting effect on a running Gradle daemon. Once it is called, Gradle doesn't generate logs even if I remove disableHttpLogging(). Stopping daemons with ./gradlew --stop and trying again works. This explains the observation in the first report that using --no-daemon helps.
• If we don't call disableHttpLogging(), just passing --info to Gradle makes Google HTTP Client to log network traffic. Therefore, it is still desirable to disable logging in usual cases.

---

Additional info: #2357 (comment)