For those interested we now have pipelines working to test the local docker build as well as the building of the official dockerfile.
https://ci-builds.apache.org/job/Solr/job/Solr-Docker-Test-main/ https://ci-builds.apache.org/job/Solr/job/Solr-Docker-Official-Test-main/ I'm not sure how to actually capture the error and log outputs that live at solr/docker/build/test-results, so if someone wants to do that please go ahead! If not it should still work and people can check the jenkins workspace to look for the logs (not ideal, but not an awful solution for now). I will look into getting the *apache/solr-nightly* docker tag setup with INFRA next week and modify the jenkins pipeline to start pushing the nightly image when the tests pass, unless anyone objects. - Houston On Thu, Sep 2, 2021 at 12:27 PM Eric Pugh <[email protected]> wrote: > I frequently want to test latest Solr as part of something larger, so > making it easier to access would be good for me. It’s a bit of pain > adding non-dockerhub locations, so this would be nice! > > > On Sep 2, 2021, at 11:34 AM, Houston Putman <[email protected]> > wrote: > > Hello all, > > I'm creating a Jenkins pipeline to do a daily build and test of the new > Apache Solr docker image. (Probably both the local and the official image) > > Is there any interest in having a place on docker hub where these nightly > docker images get published? Kind of like we have nightly maven and TGZ > artifacts published? > > I was imagining something like apache/solr-nightly:9.0.0-SNAPSHOT, which > is very clear in both the tag and version that it is not a released version > of Solr. > > Any thoughts or opinions appreciated. > > - Houston > > > _______________________ > *Eric Pugh **| *Founder & CEO | OpenSource Connections, LLC | 434.466.1467 > | http://www.opensourceconnections.com | My Free/Busy > <http://tinyurl.com/eric-cal> > Co-Author: Apache Solr Enterprise Search Server, 3rd Ed > <https://www.packtpub.com/big-data-and-business-intelligence/apache-solr-enterprise-search-server-third-edition-raw> > This e-mail and all contents, including attachments, is considered to be > Company Confidential unless explicitly stated otherwise, regardless > of whether attachments are marked as such. > >
