on the first day of christmas i noticed that this url https://docs.geoserver.org/stable/en/developer/installer/index.html contains the following content
<snip> At the time the GeoServer project does not have financial resources and man power to stand up a Windows build server (if you can help with this, please contact the developer list) </snip> if this is no longer true please disregard if build server still required * i happen to know that as an open source project the geoserver project can run unlimited builds in azure devops. so can anyone else who clones the repo in a public azure devops project * after investigating the geoserver github actions i saw nothing incompatible with triggering builds in azure devops in collaboration with specific github actions * the primary showstopper risk seems to revolve around headless installation of nsis itself and its dependencies on azure build servers as per * extract the .DLL files (AccessControl.dll) and copy it to the NSIS plugins directory usually C:\Program Files\NSIS\Plugins\x86-ansi if build server still required and mitigations exist for installing nsis and dependencies on cloud build agents, i offer to * evaluate the full build process for the windows geoserver * deliver a proof of concept of a suitable pipeline that runs in azure devops please advice
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel