Hi Neil, I would prefer elaborate with others on a chat or slack because I'm not sure to have all the element. This is Work in Progress.
Disclamer :D I'm not computer so I cannot be in stored in a data center with an air temp at 22°C. Despite I melt, I hope to be understandable. Main goal is to have everything prepared for a Release Manager (including maven artefacts) + apidoc generation And also use a json file that give a list of every tools version used to compile and allow a release branch to still populate apidoc ( because we may still reorganize some webpage (avoid 404)). It seems installer cannot be part of that. With Antonio we start a json file to handle the release information (not complete I guess). That should allow to generate a main download page of Apache NetBeans That should allow to generate a cron script that adapt over the list of release to populate apidoc pages Current version: https://github.com/apache/netbeans-jenkins-lib/blob/master/meta/netbeansrelease.json About the groovy script and build The build is a special Apache Hosted Git Folder job https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-TLP/configure It scan git on branch releaseXXX commit and branch master It's similar to what is done on release build but in groovy style. It basically do the following on release branches. Take information from json file to have version Creation of folder copy of sources on each folder Ant build for cluster release and platform. (archived for later sign) Ant build for sources and additional elements for maven artefacts. (archived for later sign) Ant build for apidoc (a cron job on nbvm take the zip to populate website) It does the following on master Take information from json file to have tools version and date Api doc generation Ant build of netbeans Publish maven artefact snapshot direct on apache snapshot repo (no archive, autopublish checked with infra) Ant build for apidoc (a cron job on nbvm take the zip to populate website) Best Regards Eric -----Message d'origine----- De : Neil C Smith <[email protected]> Envoyé : mardi 23 juillet 2019 18:39 À : dev <[email protected]> Objet : Re: Convenience binary policy? On Tue, 23 Jul 2019 at 16:09, Eric Barboni <[email protected]> wrote: > I did a reworks to prepare release + maven artefacts and also apidoc > https://github.com/apache/netbeans-jenkins-lib/blob/master/vars/asfMai > nNetBeansBuild.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. OK, I guess it's similar to the platform sources then, if slightly more complicated. Are the salient bits of that script documented somewhere such that someone can take the main source zip and replicate that process easily without it? 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 --------------------------------------------------------------------- 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
