Skip to content

chore: add Kokoro release config and script for OSS Exit Gate - #563

Open
zarturod wants to merge 1 commit into
googleads:mainfrom
zarturod:chore/oss-exit-gate-kokoro-release
Open

zarturod wants to merge 1 commit into
googleads:mainfrom
zarturod:chore/oss-exit-gate-kokoro-release

Conversation

@zarturod

Copy link
Copy Markdown

Summary

Adds .kokoro/release.cfg, .kokoro/release.sh, .kokoro/requirements.in, and .kokoro/requirements.txt to migrate googleads-python-lib PyPI releases (googleads) to the OSS Exit Gate pipeline via Kokoro.

  • Build & Validate: Builds sdist and wheel distributions (python3 -m build) in an isolated Python 3.12 virtualenv and validates them with twine check.
  • Stage to OSS Exit Gate Artifact Registry: Uploads distributions to https://us-python.pkg.dev/oss-exit-gate-prod/googleads-python-lib--pypi using ambient Kokoro BYOSA credentials (keyrings.google-artifactregistry-auth).
  • Safe Dry-Run Default: Defaults to DRY_RUN=true in .kokoro/release.cfg and .kokoro/release.sh so staging can be verified before triggering external publication.
  • Trigger Publication via Manifest: When DRY_RUN=false, uploads a targeted manifest.json ("name": "googleads") to gs://oss-exit-gate-prod-projects-bucket/googleads-python-lib/pypi/manifests/.
  • Follows the BAM DevRel Kokoro + OSS Exit Gate pattern from googleads/data-manager-python/.kokoro/.

@google-cla

google-cla Bot commented Oct 28, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant