-
Notifications
You must be signed in to change notification settings - Fork 450
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
Use GitHub Actions to manage Pushy releases #617
Labels
Comments
jchambers
changed the title
Use Travis CI deployments to manage Pushy releases
Use Travis CI deployments (or GitHub Actions?) to manage Pushy releases
Dec 21, 2018
Now that GitHub Actions are A Thing, we might consider using those, too. |
jchambers
changed the title
Use Travis CI deployments (or GitHub Actions?) to manage Pushy releases
Use GitHub Actions to manage Pushy releases
Feb 12, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now, the deployment process for Pushy is that I type a bunch of stuff into a terminal to manually trigger deployment to Maven Central using the Maven deploy plugin. This is more error-prone than is ideal, and also perhaps excessively dependent on my specific credentials.
As an alternative, we should consider using the Travis CI deployment system to build, sign, and publish artifacts at release time.
The text was updated successfully, but these errors were encountered: