I haven't touched the nightlies in a couple days, so it may have just been them trickling through the build. Glad its working again though.
I'll ask about https again. Planet Federal ought to have a cert for build.geoserver.org, I just don't have access to it. I'm currently looking into PostGIS; something is wrong with the config, but I'm having trouble determining exactly what (seems like something is missing on the worker node) I found run.sh for the cite tests, and have added a PR to the geoserver-cite-tools repo containing it, so that it is in version control. If you want to take a look at that, and try and get the cite tests working, that would be great. I also included my notes from last time I looked at the cite tests in a comment at the top of the file - that should help get this working. The PR is here: https://github.com/geoserver/geoserver-cite-tools/pull/8 The other option would be to look at the release jobs, and see what changes need to be made there to get them working again, although I think Jody mentioned he might be doing that soon. A windows build box is on the way, someone else at Planet Federal is looking into it. One other thing on my radar (but lower priority that everything else) is the geowebcache nightlies, which aren't configured to use git, and need to be updated before they'll work again. Torben On Fri, May 31, 2019 at 1:09 AM Andrea Aime <andrea.a...@geo-solutions.it> wrote: > Hi Torben, > I had a script pointing at those communty-latest, ext-latest directory > links, it was failing because they were not there. > However, I see they are available now, suspect you did something to change > it. Thank you! > > Now, I heard Jody is looking at the GWC nightly job, anything else that I > can help with? > The major pain points right now are, in order of priority (priority of > mine of course, others might disagree): > > - https support > - postgresql and other databases for online builds > - cite > - release jobs > - windows build server for releases > > Cheers > Andrea > > > On Thu, May 30, 2019 at 12:03 AM Torben Barsballe < > tbarsba...@federal.planet.com> wrote: > >> Hmm, those should still be getting constructed. The builds are currently >> using "Archive Artifacts" to transfer the artifacts from the worker node to >> the master - Its possible the wildcard expression doesn't catch the >> "latest" artifacts or something similar is wrong. If you want to take a >> look at the build configuration for the nightly builds and see if you can >> determine what's going on, that would be great. >> Note that "Archive artifacts" only copies the artifacts into the job >> workspace on master, I've got a cron job running on master to copy those >> artifacts to the hosted folders, so if the *-latest artifacts are getting >> archived but not showing up then it could be an error in that cron job (I'm >> hoping to eventually just have the workers scp the artifacts to the hosted >> folder on master, but my ability to modify the worker nodes is somewhat >> limited, and this was a quicker way to get the nightlies actually working) >> >> If there isn't anything obvious wrong in the nightly config, then I can >> take a look on the server and see if something else is going wrong. >> >> Torben >> >> On Wed, May 29, 2019 at 3:56 AM Andrea Aime <andrea.a...@geo-solutions.it> >> wrote: >> >>> On Tue, May 28, 2019 at 7:52 PM Torben Barsballe via GeoTools-Devel < >>> geotools-devel@lists.sourceforge.net> wrote: >>> >>>> Build Server >>>> >>> >>> One more thing that is missing from the nightly builds is the "latest" >>> directories, e.g., ext-latest, community-latest, >>> which were always pointing to the latest build. Directory names with >>> dates are great, but not useful for using >>> scripted custom GeoServer war assemblies >>> >>> As usual, if there is anything I can do to help, just let me know. >>> >>> Cheers >>> Andrea >>> >>> == >>> >>> GeoServer Professional Services from the experts! Visit >>> http://goo.gl/it488V for more information. == Ing. Andrea Aime @geowolf >>> Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa >>> (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 >>> http://www.geo-solutions.it http://twitter.com/geosolutions_it >>> ------------------------------------------------------- *Con >>> riferimento alla normativa sul trattamento dei dati personali (Reg. UE >>> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si >>> precisa che ogni circostanza inerente alla presente email (il suo >>> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è >>> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il >>> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra >>> operazione è illecita. Le sarei comunque grato se potesse darmene notizia. >>> This email is intended only for the person or entity to which it is >>> addressed and may contain information that is privileged, confidential or >>> otherwise protected from disclosure. We remind that - as provided by >>> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this >>> e-mail or the information herein by anyone other than the intended >>> recipient is prohibited. If you have received this email by mistake, please >>> notify us immediately by telephone or e-mail.* >>> >> > > -- > > Regards, Andrea Aime == GeoServer Professional Services from the experts! > Visit http://goo.gl/it488V for more information. == Ing. Andrea Aime > @geowolf Technical Lead GeoSolutions S.A.S. Via di Montramito 3/A 55054 > Massarosa (LU) phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 > 8844549 http://www.geo-solutions.it http://twitter.com/geosolutions_it > ------------------------------------------------------- *Con riferimento > alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - > Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni > circostanza inerente alla presente email (il suo contenuto, gli eventuali > allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i > destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per > errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le > sarei comunque grato se potesse darmene notizia. This email is intended > only for the person or entity to which it is addressed and may contain > information that is privileged, confidential or otherwise protected from > disclosure. We remind that - as provided by European Regulation 2016/679 > “GDPR” - copying, dissemination or use of this e-mail or the information > herein by anyone other than the intended recipient is prohibited. If you > have received this email by mistake, please notify us immediately by > telephone or e-mail.* >
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
