Scatter gun question: Has anyone done a build service which uses TestContainers to fire up a container and then have the build service interact with it?

we moved all docker managing logic out of gradle into our testsuites as managing docker container within a build has been a pita

One such case could be running Kroki in a container and then point asciidoctor to that URL instead of the one in the cloud.

We moved our asciidoctor outside Gradle as well, but yes start Kroki before you run Gradle:

# start Kroki
docker compose up -d
# wait for Kroki to be up
timeout 30s sh -c 'until curl -s <http://localhost:8000> 2>&1 >/dev/null; sleep 1; done'
# Run Gradle
./gradlew build -PkrokiUrl=<http://localhost:8000>

@Thomas Broyer I am interested why asciidoctor-gradle is not working for you. (Unless you've moved to Antora).

It's not that it's "not working", more that we don't need to have it as part of our Gradle build (output won't be used by other Gradle tasks), and we have a company theme as part of a customized docker-asciidoctor image, so it's just easier in most cases to just run asciidoctor through docker separately from Gradle (and we can use the same build steps in every project, whether they use Gradle, Maven, Node, Python, etc.)