chore: add kokoro 3.9 configs

[leahecole]

This will be blocked until

• this synthtool PR is merged
  and
• we run synth here (I rechecked the box to regen the PR on Friday 1/15 at 5:30pm pacific)

Internal CL352076910 adds 3.6, 3.8, and 3.9 internal configs (3.7 is already set up)

[parthea]

Hey @leahecole, Could we add the configurations to the synthtool templates here?

[parthea]

See synthtool feature request here.

[leahecole]

On it - thanks for the reference @parthea

[leahecole]

This will probably need a rework to instead specify the build specific project in a noxfile_config

[leahecole]

@parthea I was trying to follow through on my earlier comment and of course forgot what I meant. I added a noxfile_config to the model builder samples directory that calls the BUILD_SPECIFIC_GCLOUD_PROJECT - we define that value with the ucaip project in the kokoro configs. Given that kokoro configs are being sync'd with Owlbot, and we normally do a build specific project as one from our project pool, should I actually be doing this in the noxfile config?

What I think we need

'gcloud_project_env': 'string-of-project-name'

What we currently have (which references a project string defined in common.cfg

'gcloud_project_env': 'BUILD_SPECIFIC_GCLOUD_PROJECT'

[parthea]

Hey @leahecole ,

I'm not sure how to solve it with noxfile_config. In case it helps, this synthtool replacement in owlbot.py worked for me locally.

s.replace(".kokoro/samples/python3.*/common.cfg",
    """env_vars: \{
    key: "BUILD_SPECIFIC_GCLOUD_PROJECT"
    value: "python-docs-samples-tests-py3.*?"
\}""",
    """env_vars: {
    key: "BUILD_SPECIFIC_GCLOUD_PROJECT"
    value: "ucaip-sample-tests"
}""",
    flags=re.MULTILINE | re.DOTALL,
)

[parthea]

Hey @leahecole,
Please let me know if I can go ahead with adding the replacement in owlbot.py from #175 (comment)

[leahecole]

That will work and I'm happy to hand it off to you!

[google-cla]

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

[parthea]

@googlebot I consent.

[parthea]

@leahecole Done, please can you take a look?

[leahecole]

@parthea other than these little fixes (which very well could have been a copy paste error from me) it looks good!

[leahecole]

LGTM!

[leahecole]

Because I'm the original author I can't approve so perhaps another @googleapis/python-samples-owners can approve :)

[leahecole]

Thanks @busunkim96 :)