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

CI: Port publish and release functionality to Rust #3003

Open
tjtelan opened this issue Feb 22, 2023 · 0 comments
Open

CI: Port publish and release functionality to Rust #3003

tjtelan opened this issue Feb 22, 2023 · 0 comments
Labels
build-release CI DX/GENERAL Developer Experience General enhancement New feature or request technical debt

Comments

@tjtelan
Copy link
Contributor

tjtelan commented Feb 22, 2023

Related to: #2998

Having the publish/release functions of CI collected into a CLI would lower the barriers for maintenance, and help diagnose "works on my machine" issues, and document troubleshooting steps in one context vs shell scripts, Makefiles, and GH Action configs.

This CLI can begin by duplicating the commands we run in GH Actions, preferably before we make any optimizations.

We would have to build this CLI before any other tests. But the outcome would result in more effective local testing and reduce the frequency we have to push commits to troubleshoot GH Actions-related issues. Someone who isn't as confident with the shell or make, but knows Rust can contribute or review PR with higher confidence.

I imagine this as a configurable cli tool that supports :

  • Running shell commands for building artifacts for publish
  • Creating GH releases to publish artifacts
  • Downloading artifacts from GH Releases
  • Update VERSION and create PR (prerelease candidates [alpha-n,beta-n], patch, minor, major, or custom)
  • Generation of the CHANGELOG with respect to release
    • Based on PRs in the commit message history
    • Configuration for curating of the output (to handle transition to enforcing conventional commit)

This CLI should begin by duplicating the commands we run in GH Actions, preferably before we make significant optimizations. I will add caution, and suggest baby steps with integration into CI, because this is a critical area.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build-release CI DX/GENERAL Developer Experience General enhancement New feature or request technical debt
Projects
None yet
Development

No branches or pull requests

1 participant