Split automated command into two make calls

[ericvn]

An update in istio/common-files#382 was propagated to the various repos via the automation script. The automated PR included changes in go.sum where the common-files update should have changed the makefile target, mod-download-go, to prevent that. Some experimentation running make update-common gen in a build container showed that indeed the go.sum file was changed. This did not happen when running the command from the command line. Splitting the command into two makes in the build container did not update the go.sum.

A subsequent common-files update (remove the target and make the mod-download-go rule do nothing will hopefully get the automated PRs corrected and merged.

[istio-testing]

@ericvn: Updated the job-config configmap in namespace default at cluster default using the following files:

• key istio.common-files.master.gen.yaml using file prow/cluster/jobs/istio/common-files/istio.common-files.master.gen.yaml

In response to this:

An update in istio/common-files#382 was propagated to the various repos via the automation script. The automated PR included changes in go.sum where the common-files update should have changed the makefile target, mod-download-go, to prevent that. Some experimentation running make update-common gen in a build container showed that indeed the go.sum file was changed. This did not happen when running the command from the command line. Splitting the command into two makes in the build container did not update the go.sum.

A subsequent common-files update (remove the target and make the mod-download-go rule do nothing will hopefully get the automated PRs corrected and merged.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.