On Mon, 22 Mar 2021, 21:37 Lars Bruun-Hansen, <[email protected]> wrote:
> By "cowboy method", I meant: A non-producible build. Developer > builds the native binary on his own workstation from > who-knows-what-source and hands it over to someone who uploads it to > bin-repo. Worst case he builds from some code which isn't committed, > perhaps never will be. I'm afraid this is the current state of affairs > with these native binaries in the NetBeans universe. (all devs knows > this is not the right way, but we all cut corners) > > By "doing it right", I meant: Native binaries can always be traced > back to an exact commit ref in the official Git repo. Binaries are not > build by a human, but by a CI pipeline. Code is checked out from a > commit ref and the binary is build from that and then turned into a > consumable artifact which is immutable (same version id can never be > overwritten, a new version id must be used). The binary is re-build > whenever the source code changes. > +1 and IMO, released via standard ASF processes, vote and infrastructure. Unless we expect every end-user source consumer to build these manually, we should treat them as released artefacts like any other binary. Best wishes, Neil >
