The build process is on Jenkins for the platform over here https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-release. There is script to prepare source in the Jenkins build.
As maven + apidoc were requiring to create a new buildjob for a release I did a reworks to prepare release + maven artefacts and also apidoc https://github.com/apache/netbeans-jenkins-lib/blob/master/vars/asfMainNetBeansBuild.groovy that do the same pattern as main release build (start line 101) + source zips + download the nb-repository-plugin + prepare the maven arteafcts based on release cluster. Regards Eric -----Message d'origine----- De : Neil C Smith <[email protected]> Envoyé : mardi 23 juillet 2019 16:46 À : dev <[email protected]> Objet : Re: Convenience binary policy? On Tue, 23 Jul 2019, 15:16 Eric Barboni, <[email protected]> wrote: > Maven artefacts are pom,jar,nbm and also jar with source. > How does it works for these? Source are from the same git hash but > split to all the jar? > Vote required or not in this case ? > Well, the platform source zip isn't voted on either - it's a build artefact of the full source. But, one thing I'm less sure on - where is the build code for this process? In the main sources or external? I would say we can take Geertjan Lazy consensus for that sanity checking > While that's ok by me, I'd prefer requiring a minimum number of checks and sign offs. The problem with lazy consensus in this scenario is there's no guarantee anyone has checked! But, happy with whatever the consensus seems to be. Key thing is to be on the same page the next time we have to deal with it. And we get the rest of 11.1 up soon! :-) Best wishes, Neil > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
