Tickle builds via POST request?

[eddelbuettel]

The build trigger page(s) look like they would offer finer control than the unconditional 'build when commit made'.

An open question is how to learn about success/failure of dependencies.

[cboettig]

Nice. Looks like you could configure a webhook to know when the build was successful. I don't see anything about failure though, one might just need to time-out instead.

Meanwhile, it looks like if I use the start-build button on the homepage for the repo, it just triggers a build of that image. (vs on the automated builds page, where it basically simulates a push event and triggers everything to build)

[eddelbuettel]

Nice -- I saw those per-repo hooks but didn't put two and two together.

[cboettig]

Seems like we have this working now with a combination of repository links to trigger builds when the previous base image is updated and then unlinking the automated build-on-commit option from rocker/r-devel and rocker/rstudio, such that they only build once base is updated.

In this way, a commit to any of the three repos will result in them being updated, but in the natural sequence. Also, updates to debian:testing (e.g. security patches) will trigger automatic builds of r-base, and thus down the line (including hadleyverse and ropensci). debian:testing is updated regularly with security patches, as described in tianon/docker-brew-debian#10

Since this is now in place, I think we can close this? (even though we aren't using the build trigger & webhook options)

[cboettig]

Okay, we tickle drd daily.
All other images build as when they or their dependency FROM image is updated.