Alessandro: We now have repo.osgeo.org operational, the builds should hopefully switch over in the next couple of days.
I have created https://repo.osgeo.org/repository/geoserver-docker/ for you to try out. -- Jody Garnett On Tue, 3 Mar 2020 at 09:48, Jody Garnett <jody.garn...@gmail.com> wrote: > For repo, would having an osgeo nexus repo help as a place to store the > docker images? > -- > Jody Garnett > > > On Tue, 3 Mar 2020 at 01:41, Alessandro Parma < > alessandro.pa...@geo-solutions.it> wrote: > >> Thanks for your feedback >> >> My answers inline below >> >> > I think managing the docker builds in the "build" directory is >> appropriate. Is it worth co-locating these with their cite data directory >> configuration (to make each folder more self contained)? >> >> I agree. I would move the datadirs everything in the build/cite >> <https://github.com/randomorder/geoserver/tree/gsip-176/build/cite> dir >> along with the docker related file, ok? >> >> > aside: In the past when faced with builds grabbing status codes we >> would grep through the output for failure, not sure how stable that is. >> >> Ok, thank you. I'll dig a little deeper into to try to avoid grepping the >> logs, if possible. >> >> > There is not an official repository on docker hub for this, we should >> set this up (I am not sure what is needed). >> >> I think we should create an Organization >> <https://docs.docker.com/docker-hub/orgs/> and a team with members >> allowed to push the docker image to the hub. >> >> On Fri, Feb 28, 2020 at 7:26 PM Jody Garnett <jody.garn...@gmail.com> >> wrote: >> >>> Thank you for the update! >>> >>> I think managing the docker builds in the "build" directory is >>> appropriate. Is it worth co-locating these with their cite data directory >>> configuration (to make each folder more self contained)? >>> >>> aside: In the past when faced with builds grabbing status codes we would >>> grep through the output for failure, not sure how stable that is. >>> >>> There is not an official repository on docker hub for this, we should >>> set this up (I am not sure what is needed). >>> -- >>> Jody Garnett >>> >>> >>> On Fri, 28 Feb 2020 at 09:50, Alessandro Parma < >>> alessandro.pa...@geo-solutions.it> wrote: >>> >>>> HI Jody, All, >>>> >>>> Status update with a couple of questions about the source code >>>> management and deployment of this work: >>>> >>>> I added more builds <https://build.geoserver.org/view/testing-cite/> >>>> for the ets suites, updated list: >>>> - wms11 >>>> - wms13 >>>> - wfs10 >>>> - wfs11 >>>> - wcs10 >>>> - wcs11 >>>> - wcs20 >>>> - wfs20 >>>> >>>> Then created a build for the teamengine-docker fork >>>> <https://github.com/geosolutions-it/teamengine-docker.git/> to build >>>> the docker image for teamengine with the suites and tools that we need. >>>> The docker image includes all of the sutes that we use and a single >>>> docker images can be used by all cite test runs (there is >>>> nothing test-specific in it). This build is currently hosted on this >>>> <https://build.geo-solutions.it/jenkins/view/GSIP%20176%20-%20CITE%20Automation/job/teamengine-docker/> >>>> build server because I had some issues >>>> <https://build.geoserver.org/view/testing-cite/job/teamengine-docker/18/console> >>>> with the build on geoserver >>>> build server that I still need to address... The docker image is >>>> currently pushed here >>>> <https://github.com/geosolutions-it/teamengine-docker> on the docker >>>> hub (more on this later) >>>> >>>> I then created a parameterized build >>>> <https://build.geoserver.org/view/testing-cite/job/cite-runner/build?delay=0sec> >>>> to >>>> run the tests. It is currently building from my >>>> <https://github.com/randomorder/geoserver.git/> GeoServer fork where I >>>> pushed >>>> the docker-compose files >>>> <https://github.com/randomorder/geoserver/tree/gsip-176/build/cite> >>>> and the other auxiliary files required to run the tests. My idea, and >>>> I'd like to have feedback from you as well as from the GeoServer >>>> ML, is to add all the files required into the 'build' subdirectory >>>> <https://github.com/randomorder/geoserver/tree/gsip-176/build/cite> of >>>> the repository. Would this be ok? >>>> The file structure mimics that in our proposal where we have a global >>>> docker-compose.yml file with a 'geoserver' and ''teamengine' service >>>> definition and subdirectory for every test suite with test specific >>>> files like "forms" for command line execution of a given test suite and a >>>> docker-compose override file to spin up postgresql if required by the >>>> specific test. For data directories I'd use the ones that are >>>> already available >>>> <https://github.com/randomorder/geoserver/tree/gsip-176/data> in the >>>> repository. >>>> >>>> An example execution of this parametrized build is available here >>>> <https://build.geoserver.org/view/testing-cite/job/cite-runner/4/console> >>>> where >>>> I ran the WMS 1.1.1 suite against the latest geoserver master nightly. >>>> The log files from the test run are stored as artifacts >>>> <https://build.geoserver.org/view/testing-cite/job/cite-runner/4/artifact/logs.zip> >>>> from the job run. There is still some work to do, notably, the job does >>>> not fail when a given >>>> test fails (apparently due to the test.sh script in the teamengine >>>> suite swallowing the status of the tests. I still need to figure this out) >>>> and to add >>>> more builds for the other suites. I'll keep you informed on my progress >>>> on this. >>>> >>>> Concerning the docker image(s) for teamengine-docker is there an >>>> official repository for GeoServer on the docker hub where I can push the >>>> image? >>>> >>>> Thank you in advance for your feedback, >>>> Alessandro >>>> >>>> >>>> On Fri, Feb 21, 2020 at 6:00 PM Alessandro Parma < >>>> alessandro.pa...@geo-solutions.it> wrote: >>>> >>>>> Dear Jody, All >>>>> >>>>> Just a quick update on this: >>>>> I set up a test build >>>>> <https://build.geoserver.org/view/testing-cite/job/ets-wms11/> on the >>>>> build server for one of the CITE tests >>>>> <https://github.com/opengeospatial/ets-wms11.git> to build and deploy >>>>> the artifacts on the maven repository >>>>> <http://download.osgeo.org/upload/geotools/org/opengis/cite/ets-wms11/1.19/> >>>>> and >>>>> I am currently working on the the docker images and writing the >>>>> docker-compose file to run the geoserver, postgres and teamengine >>>>> containers to execute the tests. >>>>> The build job is taking the Github branch and tags as parameters (with >>>>> defaults) and is not tightly bound to the build environment so It >>>>> would be pretty straightforward to migrate it to another build server. >>>>> For the docker images and I don't have something ready to show yet, >>>>> I'll let you know as soon as I do. >>>>> >>>>> On Fri, Feb 14, 2020 at 6:42 PM Simone Giannecchini < >>>>> simone.giannecch...@geo-solutions.it> wrote: >>>>> >>>>>> Hi Jody, >>>>>> We are a little beyond schedule with this, the work has started but >>>>>> there is little to show. >>>>>> >>>>>> We will send periodic updates to the psc and devel list starting next >>>>>> week. >>>>>> >>>>>> Regards, >>>>>> Simone Giannecchini >>>>>> == >>>>>> GeoServer Professional Services from the experts! >>>>>> Visit http://bit.ly/gs-services for more information. >>>>>> == >>>>>> Ing. Simone Giannecchini >>>>>> @simogeo >>>>>> Founder/Director >>>>>> >>>>>> GeoSolutions S.A.S. >>>>>> Via di Montramito 3/A >>>>>> 55054 Massarosa (LU) >>>>>> Italy >>>>>> phone: +39 0584 962313 >>>>>> fax: +39 0584 1660272 >>>>>> mob: +39 333 8128928 >>>>>> >>>>>> 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. >>>>>> >>>>>> >>>>>> On Thu, Feb 13, 2020 at 6:08 PM Jody Garnett <jody.garn...@gmail.com> >>>>>> wrote: >>>>>> >>>>>>> Simone: >>>>>>> >>>>>>> Next week's Feb 18th meeting is our final meeting in February, is >>>>>>> there any update from the Cite Automation work? >>>>>>> >>>>>>> With the recent news from Planet Federal I am concerned about >>>>>>> ability to deliver into build.geoserver.org environment. >>>>>>> -- >>>>>>> Jody Garnett >>>>>>> >>>>>> -- >>>>>> Regards, >>>>>> Simone Giannecchini. >>>>>> GeoSolutions Director >>>>>> >>>>>> - sent from my mobile, apologies for brevity and typos- >>>>>> >>>>> >>>>> >>>>> -- >>>>> >>>>> Regards, >>>>> >>>>> Alessandro Parma >>>>> >>>>> == >>>>> GeoServer Professional Services from the experts! Visit >>>>> http://goo.gl/it488V for more information. >>>>> == >>>>> >>>>> Alessandro Parma >>>>> DevOps Engineer >>>>> >>>>> GeoSolutions S.A.S. >>>>> Via di Montramito 3/A >>>>> 55054 Massarosa (LU) >>>>> Italy >>>>> phone: +39 0584 962313 >>>>> fax: +39 0584 1660272 >>>>> >>>>> 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, >>>> >>>> Alessandro Parma >>>> >>>> == >>>> GeoServer Professional Services from the experts! Visit >>>> http://goo.gl/it488V for more information. >>>> == >>>> >>>> Alessandro Parma >>>> DevOps Engineer >>>> >>>> GeoSolutions S.A.S. >>>> Via di Montramito 3/A >>>> 55054 Massarosa (LU) >>>> Italy >>>> phone: +39 0584 962313 >>>> fax: +39 0584 1660272 >>>> >>>> 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, >> >> Alessandro Parma >> >> == >> GeoServer Professional Services from the experts! Visit >> http://goo.gl/it488V for more information. >> == >> >> Alessandro Parma >> DevOps Engineer >> >> GeoSolutions S.A.S. >> Via di Montramito 3/A >> 55054 Massarosa (LU) >> Italy >> phone: +39 0584 962313 >> fax: +39 0584 1660272 >> >> 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. >> >
_______________________________________________ Geoserver-devel mailing list Geoserver-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-devel
