Open monperrus opened 7 months ago
no worries for Reproducible Central: I have automation that makes it easy to update without the help of projects see https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/doc/add.md for details, if you are interested
at spoon level, what I really need is either no beta to Maven Central, or if you want to publich to Maven Central, publish a git tag as you do with releases: see https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/fr/inria/gforge/spoon/spoon-core/README.md
on rebuilding when something is published, I manage, no worry
publish a git tag as you do with releases
I have tried it here https://github.com/INRIA/spoon/pull/5530. Just need a reviewer to look at it.
or if you want to publich to Maven Central, publish a git tag as you do with releases
@hboutemy Spoon also publishes the git tag for beta releases https://github.com/INRIA/spoon/releases/tag/v11.0.1-beta-17 onwards. :tada:
@monperrus both of the tasks in the issue description is taken care by reproducible-central. we can close this issue.
@algomaster99 really nice: 11.0.1-beta-17 now confirmed reproducible https://github.com/jvm-repo-rebuild/reproducible-central/blob/master/content/fr/inria/gforge/spoon/spoon-core/README.md (buildspec published, README will be updated tonight) 🎉
that's great progress.
what do you think of pushing the buildinfo file to Maven Central directly, with each staging?
what do you think of pushing the buildinfo file to Maven Central directly, with each staging?
We can do it for the sake of good practice. @hboutemy will this help you in any way?
this won't really help in addition, rebuilding is valuable when done by a third party
don't worry, rebuilding is not really complex, I have all necessary helpers
as part of the release pipeline, we should: