Keep a Python test phase's lockfile install in check builds #135
@@ -391,12 +391,12 @@ style conventions are in separate documents:
|
|||||||
the lockfile is out of date with `Pipfile`.
|
the lockfile is out of date with `Pipfile`.
|
||||||
- A kept layer holds the same pipenv, the same dependencies of pipenv and
|
- A kept layer holds the same pipenv, the same dependencies of pipenv and
|
||||||
the same lockfile packages that a new install would, because each was
|
the same lockfile packages that a new install would, because each was
|
||||||
checked against its hash. The pip and setuptools inside the virtualenv
|
checked against its hash. The packages `virtualenv` puts into the
|
||||||
that pipenv creates are the same too: the `virtualenv` package, one of
|
virtualenv that pipenv creates are the same too: the `virtualenv` package,
|
||||||
pipenv's dependencies, copies them from wheels it ships, and its hash
|
one of pipenv's dependencies, copies them from wheels it ships, and its
|
||||||
covers those wheels. Any system packages the step installed are not pinned
|
hash covers those wheels. Any system packages the step installed are not
|
||||||
by hash: the layer keeps the versions the package manager gave when the
|
pinned by hash: the layer keeps the versions the package manager gave when
|
||||||
layer was built, and a new install may get newer ones.
|
the layer was built, and a new install may get newer ones.
|
||||||
- The packages are kept in a layer rather than a cache mount for the reason
|
- The packages are kept in a layer rather than a cache mount for the reason
|
||||||
Go's modules are: a cache mount is shared by every build on the host, and
|
Go's modules are: a cache mount is shared by every build on the host, and
|
||||||
nothing checks its files again.
|
nothing checks its files again.
|
||||||
|
|||||||
Reference in new issue
Block a user