Skip to content

Conversation

hiranya911
Copy link
Contributor

@hiranya911 hiranya911 commented Feb 7, 2020

Currently staging and publishing happen in a single job. We simply regulate when publishing steps are invoked by examining the PR metadata. This change makes this distinction more explicit by refactoring the publish steps into a separate job.

The publish job is invoked only when:

  1. the staging job completes successfully (needs: stage_release), and
  2. when the trigger PR meets the necessary conditions (if: ....).

The stage_release job tests, builds and uploads the release artifacts. The publish_release job downloads the same artifacts, and posts them to Pypi (not implemented yet).

I'm also disabling the egg file binary distribution and instead configuring wheel and source distributions. This is consistent with how other GCP Python packages are published (e.g. https://pypi.org/project/google-auth/#files).

Sample run: https://github.com/firebase/firebase-admin-python/actions/runs/36064065

Copy link
Member

@lahirumaramba lahirumaramba left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@hiranya911 hiranya911 merged commit a4f2bda into master Feb 10, 2020
@hiranya911 hiranya911 deleted the hkj-workflow-split branch February 10, 2020 19:02
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.

2 participants