> > I think a similar setup would be best - if you have a single place > where people can configure their alternate repository for binaries > before building
At work, we're doing builds of binaries and builds of Java and then merging the two. This is done in one product with Ant+Jenkins+Artifactory and another product with Maven+Jenkins+Artifactory I could share some Jenkins pipelines and other examples. It works pretty good when we a) Build binaries somewhat infrequently because the code doesn't change. Set a version number on the zip of binaries. Change the version number when making experimental or permanent changes. b) Use the version number of the zip of binaries when including the zip in the Java build. Select a known good version number and bake it into the build files of the Java code. Manually update the version number when new binaries have gone through a testing process. The impact is that most developers don't configure their laptops to build the binaries. Kind Regards, Johnny
