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

Automate releases #575

Open
7 of 8 tasks
loosebazooka opened this issue Nov 16, 2023 · 6 comments
Open
7 of 8 tasks

Automate releases #575

loosebazooka opened this issue Nov 16, 2023 · 6 comments
Labels
enhancement New feature or request

Comments

@loosebazooka
Copy link
Member

loosebazooka commented Nov 16, 2023

Gradle:

  • Move ownership from vlsi to sigstore-java-releasers on gradle plugin portal
  • Add gradle release secrets to repo

Maven-Central:

  • Add pgp key to repo
  • publish public key to keyserver
  • Add sigstore-java-releasers as authorized releaser on dev.sigstore
  • Add maven release secrets to repo
  • Ensure Gradle plugin is released on Central as well
@loosebazooka loosebazooka added the enhancement New feature or request label Nov 16, 2023
@loosebazooka
Copy link
Member Author

So the current iteration isn't fully automatic

  • tagging does not trigger a release
    • sigstore-java release action is a "workflow_dispatch"
    • gradle plugins releases action is also a "workflow_dispatch"
  • maven central releases still need a user to log in and close+release the artifact
  • gradle plugins aren't released to maven central

@szpak
Copy link
Contributor

szpak commented Jan 31, 2024

maven central releases still need a user to log in and close+release the artifact

That could be automatized with https://github.com/gradle-nexus/publish-plugin/

@loosebazooka
Copy link
Member Author

Oh right, thanks, I was hoping for a little human intervention on purpose at first. I think @vlsi release plugin does automation as well?

@szpak
Copy link
Contributor

szpak commented Jan 31, 2024

Most likely yes. As Visi is closer to this project, probably his plugin will be "better supported" here.

@szpak
Copy link
Contributor

szpak commented Jan 31, 2024

Oh right, thanks, I was hoping for a little human intervention on purpose at first.

Sure, that's a good idea to verify the things.

Btw, in some projects (e.g. the Apache projects), people close the staging repository, giving the others chance to test it manually, verify content, etc. And once it is done, the staging repository can be released (manually or from a manual step in the pipeline).

Of course, sigstore-java might not need that - e.g. having a good test harness and some other verifications in place. I know many project which release automatically from tag (or from [#DO_RELEASE] in the commit message).

@loosebazooka
Copy link
Member Author

Yeah I agree. We're a little immature in release right now. Will work on a better mechanism. I don't have a preference on release plugin. So either is fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants