Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build and publish figures on pypi #372

Merged
merged 2 commits into from
Jun 14, 2021
Merged

build and publish figures on pypi #372

merged 2 commits into from
Jun 14, 2021

Conversation

OmarIthawi
Copy link
Contributor

@OmarIthawi OmarIthawi commented Jun 12, 2021

This is an initial attempt to publish figures on pypi.

It'll probably not work so I've committed the publish step just to make sure the build can be done.

@johnbaldwin I hope this will be a pleasant surprise for you when you're back 🙂

This has been made from the Figures build and release steps in our confluence docs.

Publish only 1.2.3.dev1 releases

This is still in testing and it's good not to mess up the Figures PyPI so this action will only publish .dev releases as described in the setuptools of Python: https://help.github.com/en/actions/language-and-framework-guides/using-python-with-github-actions#publishing-to-package-registries

One this is tested and working, we'll publish for all releases.

Proposed workflow

This will enable a GitHub-based workflow which is completely different from the previous command line based one:

  • Update the version in the setup.py and make a PR
  • Merge the release bump PR
  • Publish a release on GitHub (done via the GUI)
  • The release is published automatically on PyPI

The workflow above is different from our PyPI release Runbook.

@@ -72,7 +72,6 @@ class ProgressOverview extends Component {
label: `${course.name} | ${course.number} | ${course.id}`,
name: course.name,
number: course.number,
id: course.id,
Copy link
Contributor

Choose a reason for hiding this comment

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

@OmarIthawi Why do we remove this?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

the pipleline breaks due to having duplicate id: course.id in two lines:

image

@OmarIthawi OmarIthawi requested a review from johnbaldwin June 14, 2021 09:16
Copy link
Contributor

@johnbaldwin johnbaldwin left a comment

Choose a reason for hiding this comment

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

Yay @OmarIthawi ! Really looking forward to getting this tested with PyPI. Since we've not been deploying to PyPI for our releases and PyPI just has an 0.4.0 release from Dec 2020, I'd say it would be find to iterate to push a series of 0.4.0.devX versions. This is exciting!

those lint warnings turns into errors when running the lint in on the
GitHub Actions due to the CI=true environment variable being set to true
This has been made from the Figures build and release steps in our confluence docs.

This is still in testing and it's good not to mess up the Figures PyPI so this action will only publish `.dev` releases as described in the setuptools of Python: https://help.github.com/en/actions/language-and-framework-guides/using-python-with-github-actions#publishing-to-package-registries

One this is tested and working, we'll publish for all releases.

This will enable a GitHub-based workflow which is completely different from the previous command line based one:

 - Update the version in the `setup.py` and make a PR
 - Merge the release bump PR
 - Publish a release on GitHub (done via the GUI)
 - The release is published automatically on PyPI

The workflow above is different from our [PyPI release Runbook](https://appsembler.atlassian.net/wiki/spaces/ED/pages/41550165/New+PyPI+release).
@OmarIthawi OmarIthawi merged commit e20539d into master Jun 14, 2021
@OmarIthawi OmarIthawi deleted the pypi branch June 14, 2021 09:30
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.

3 participants