For example, php must be built before php-mediawiki and phan. etc
I imagine the dirs that hole the docker files could container some sort of number mapping to the build order so:
- 0-php
- 0 zuul-cloner
- 1-php-mediawiki
- 1-composer
- 2-mediawiki-phan
Description
Description
Details
Details
| Subject | Repo | Branch | Lines +/- | |
|---|---|---|---|---|
| docker: Recursively build images in order | integration/config | master | +117 -5 |
Related Objects
Related Objects
Event Timeline
Comment Actions
Change 381761 had a related patch set uploaded (by Legoktm; owner: Hashar):
[integration/config@master] docker: Recursively build images in order
Comment Actions
Change 381761 merged by jenkins-bot:
[integration/config@master] docker: Recursively build images in order
Comment Actions
This is mostly working. Child images can be rebuild by passing --recurse.
Ideally we would want to ensure that parent images are up to date (docker pull / rebuild as needed). For the use case I had in mind that is easier to just rebuild from scratch without any cache.