https://github.com/apache/otava/blob/master/docs/CSV.md https://github.com/apache/otava/blob/master/docs/GRAPHITE.md ...
All of them afaics henrik On Wed, Apr 22, 2026 at 5:24 AM Alexander Sorokoumov < [email protected]> wrote: > Can you point me to the examples that still use docker build? I thought I > replaced them with the latest published image a few months ago when we > started to, well, publish the images. > > On Tue, Apr 21, 2026 at 4:22 PM Henrik Ingo <[email protected]> wrote: > > > On Mon, Apr 20, 2026 at 8:40 AM Alexander Sorokoumov < > > [email protected]> wrote: > > > > > This is a good catch and serious bug. The problem is not the docs, but > in > > > the way we build and publish Docker images. Moreover, as examples use > the > > > latest published Docker image, the issue is likely present in the > current > > > release as well. > > > > > > Here is the PR with a fix - https://github.com/apache/otava/pull/149. > > > > > > Since we should publish to PyPI/Docker using the released source code, > > I'd > > > rather restart the release after merging that PR. An alternative is > > > continue with the release and immediately do a follow up minor release > > just > > > to fix this issue. Given that we caught this bug at the earliest > release > > > stage, it seems practical to just roll a new RC. > > > > > > > > Agree. I tried reading the old docker build instructions but just by > > reading alone it wasn't clear to me what was wrong. > > > > My one question remains though: Which examples in the docs actually fail? > > Most of them seemed to use docker-build. > > > > Either way, I will close this vote now and start again later, maybe on > the > > weekend. > > > > henrik > > > > -- > > *nyrkio.com <http://nyrkio.com/>* ~ *Continuous Benchmarking as a > Service* > > > > Henrik Ingo, CEO > > [email protected] LinkedIn: > > www.linkedin.com/in/heingo > > +358 40 569 7354 Twitter: > > twitter.com/h_ingo > > > -- *nyrkio.com <http://nyrkio.com/>* ~ *Continuous Benchmarking as a Service* Henrik Ingo, CEO [email protected] LinkedIn: www.linkedin.com/in/heingo +358 40 569 7354 Twitter: twitter.com/h_ingo
