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

Implement continuous deployment using GitHub actions #84

Open
nathandloria opened this issue Apr 11, 2021 · 3 comments
Open

Implement continuous deployment using GitHub actions #84

nathandloria opened this issue Apr 11, 2021 · 3 comments
Assignees
Labels
enhancement New feature or request Team 3 This tag serves as a `claim` for team 3 to work on the issue initially

Comments

@nathandloria
Copy link
Collaborator

nathandloria commented Apr 11, 2021

Context and feature:
Currently, a team is working on shifting the project from pipenv to poetry. In their things to bear in mind section, they mention how to automate the continuous deployment of GatorMiner. By raising this issue, we propose to develop a solution to this problem.

Proposed solution:
We would like to configure used the configured poetry environment in order to ship the GatorMiner tool each time a push is made to a PR/Main branch which will allow for the tool to be viewed without users needing to install software and run commands.

Useful resources:
https://python-poetry.org/docs/cli/

Additional context:
Branch link.

@nathandloria nathandloria added enhancement New feature or request Team 3 This tag serves as a `claim` for team 3 to work on the issue initially labels Apr 11, 2021
@nathandloria
Copy link
Collaborator Author

The branch associated with this issue can be found here.

@enpuyou
Copy link
Contributor

enpuyou commented Apr 11, 2021

Thanks for bringing up this issue @nathandloria. Just a quick note on perhaps a typo: we are migrating from pipenv, not pyenv, to poetry. As the original issue #31 mentioned, pipenv-poetry-migrate might be a useful resource to look at.

Additionally, we would like to see if your team could set up an automated deployment (whether it is Github Release, or PyPI release(once the other team has published the first version)) process with Github Action. And let's talk about whether to further support pipenv once these are set up.

Thanks again!

@nathandloria nathandloria changed the title Convert Project to Poetry from Pyenv Convert Project to Poetry from Pipenv Apr 12, 2021
@nathandloria nathandloria changed the title Convert Project to Poetry from Pipenv Implement continuous deployment using GitHub actions Apr 12, 2021
@nathandloria
Copy link
Collaborator Author

Thanks for bringing up this issue @nathandloria. Just a quick note on perhaps a typo: we are migrating from pipenv, not pyenv, to poetry. As the original issue #31 mentioned, pipenv-poetry-migrate might be a useful resource to look at.

Additionally, we would like to see if your team could set up an automated deployment (whether it is Github Release, or PyPI release(once the other team has published the first version)) process with Github Action. And let's talk about whether to further support pipenv once these are set up.

Thanks again!

Thanks for the tips. It appears our issue was too close to #31 so I rewrote the issue description and changed the title. Let me know if this works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Team 3 This tag serves as a `claim` for team 3 to work on the issue initially
Projects
None yet
Development

No branches or pull requests

6 participants