Hi Pulsar developers,

Recently on Docker Hub the `latest` image has been changed from 2.8.2 to
2.9.1. As a result, the Golang client CI is failing. I have been debugging
the issue, but to help timely detection of similar issues in the future and
to ease debugging, I propose we should create a nightly Docker image for
Pulsar builds.

I filed https://github.com/apache/pulsar/issues/14755, and the arguments
are as follows:

*Is your enhancement request related to a problem? Please describe.*

Currently Docker Hub only contains release images for Pulsar. This makes
doing CI for dependent repos harder, since they wouldn't be able to test
again the bleeding edge easily, and has led to issues such as
https://github.com/apache/pulsar-client-go/issues/748 where it's unclear
which Pulsar change caused the issue.

(The linked issue was made worse because the latest image has been outdated
by ~6 months, but 1) even if that's not the case we'd still only be able to
catch issues between releases, and 2) the fact that the Golang client is
using latest points to a need of having a nightly.)

*Describe the solution you'd **like*

Create a nightly build so external repos can always point against it and
catch issues as early as possible.

*Describe alternatives you've considered*

The external repos can also try to pull in the latest Pulsar code, but that
seems harder and needs more per repo configuration.

@eolivelli suggested I post this here so it can be discussed. Opinions and
ideas are welcome, thanks!


Best,

Ziyao

Reply via email to