[CI] Push circt python wheel to pypi nightly

[rsetaluri]

No description provided.

[rsetaluri]

@mikeurbach @teqdruid how do we version this to be made into a dev release on pypi?

[teqdruid]

If the versioning works like the pycde versioning scheme, breaking it out isn't necessary. The versioning lib automatically detects the most recent tag in the commit's history. If the commit is the tag, it uses that. If not, it appends .dev<numberOfCommitsSinceTag>.

[teqdruid]

So you really just need the schedule addition above. Am I correct @mikeurbach ?

[mikeurbach]

We do use setuptools_scm, so the versioning should work as expected. But I think it makes sense to have three steps:

• one for when there is a tag (which is run on the release event trigger) and uploads the tag version to PyPI
• one for when the event is the cron, which uploads the dev version to PyPI
• one for anything else (useful for testing the workflow), which uploads artifacts to the job for inspection

I think it would make sense to use:

- name: Upload wheels (Tag)
   if: github.ref_type == 'tag'

- name: Upload wheels (Nightly)
   if: github.event_name == 'cron'

- name: Upload wheels (Workflow Dispatch)
   if: github.ref_type != 'tag' && github.event_name != 'cron'

What do you think @teqdruid @rsetaluri ?

[teqdruid]

What would be the actions? My point is, how would they differ?

[mikeurbach]

Oh I see, yes we can combine the steps that push to pypi, something like:

- name: Upload wheels (Tag or Nightly)
   if: github.ref_type == 'tag' || github.event_name == 'cron'

[teqdruid]

Yeah. I was assuming that you'd also want to push to pypi on a workflow_dispatch, but perhaps not...

[mikeurbach]

Yeah, I think we should only push to pypi on automated builds. If someone is testing the workflow itself or something, I don't think we need to push new versions.

[rsetaluri]

agree with the two modes. In the case of !(tag || cron), we can just download artifacts from github actions