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.

Sign up for GitHub

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

Jump to bottom

Use GitHub Actions to manage Pushy releases #617

Open
jchambers opened this issue Jun 19, 2018 · 1 comment · May be fixed by #1076
Open

Use GitHub Actions to manage Pushy releases #617

jchambers opened this issue Jun 19, 2018 · 1 comment · May be fixed by #1076
Labels
enhancement

Comments

@jchambers
Copy link
Owner

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.
@jchambers 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
@jchambers
Copy link
Owner Author

Now that GitHub Actions are A Thing, we might consider using those, too.

@jchambers 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
This was referenced Jul 6, 2024
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Deploy on release jchambers/pushy
1 participant
@jchambers