Open PhilippHeuer opened 3 days ago
great job, I like what you did, we need to work together further buildspec is natively at project build level = why current output (buildinfo, buildcompare, badge) is also at project build level but yes, providing output data at gav level has been identified as an enabler to many new ways to use data: I just did not have time to do it yet I'm happy you did it and I can review and discuss: I'll dive into it and give more precise feedback later, as it deserves serious look I definitively want to integrate such gav-level output and let wider community use that data in as many new ways as they can
Hi,
I'm a big fan of the work that is done in
reproducible-central
and the idea of reproducible builds in general. I created a small project for an initial integration ofreproducible-central
into Renovate PRs.Link: https://github.com/PhilippHeuer/jvm-repo-rebuild-index (written in Go) Example PR: https://github.com/PhilippHeuer/renovate-test/pull/8
Configuration:
The objective of this project was to:
group/artifact/version
(by maven coordinates)project missing
,verification pending
,reproducible
,not reproducible
)reproducible-central
This first version generates static json files for all projects in
reproducible-central
and serves them via GitHub pages. Additionally, it contains a few api endpoints for the dynamic PR badge. (selfhosted, requires logic so static json doesn't work)I think it would be awesome to have an official API to integrate
jvm-repo-rebuild
results into Renovate, Dependabot, ... (this could enable a native integrations in the future)Maybe this project can serve as a starting point for that (either as reference or to mature into something official), I would love to hear your thoughts on this project / idea.