[tahoe-lafs-trac-stream] [Tahoe-LAFS] #3601: CI builds new images for test jobs even when Tahoe's dependencies haven't changed

[Tahoe-LAFS]

#3601: CI builds new images for test jobs even when Tahoe's dependencies haven't
changed
------------------------------------+--------------------------------------
     Reporter:  exarkun             |      Owner:
         Type:  enhancement         |     Status:  new
     Priority:  normal              |  Milestone:  undecided
    Component:  dev-infrastructure  |    Version:  n/a
   Resolution:                      |   Keywords:  self-contained ci docker
Launchpad Bug:                      |
------------------------------------+--------------------------------------
Changes (by btlogy):

 * keywords:  self-contained ci => self-contained ci docker
 * type:  defect => enhancement
 * component:  unknown => dev-infrastructure


Comment:

 Having lately looked into those images, I was thinking of two steps to
 improve the current situation in regards of this ticket:

 1. limit the Docker context of those images to the strict minimum (e.g.:
 not the all `src/`, neither the `doc/` folders): this could be achieved w/
 `.dockerignore` and/or restructuring files/directories.
 2. trigger the build-images workflow on any PR that would change this
 limited context, but publish only when building on the master: this idea
 was partly discussed in ticket:3484.

--
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3601#comment:3>
Tahoe-LAFS <https://Tahoe-LAFS.org>
secure decentralized storage