-
Re-work the tox deployment so that we mount the application directory as a read-only volume rather than copying the file in when building the image. This has the following advantages: 1. We do not build a new image each time we run tests. (This is nicer to those of us with finite disk space.) 2. Running tests is slightly faster since a new image is not being built. 3. The application directory is mounted read-only so we catch code which accidentally writes to the current directory. 4. We can use the upstream tox image rather than rolling our own derived image. In order to make to happy to run in a read-only environment, we specify that a) it does not run sdist to write an .egg-info directory and b) that coverage data is stored in /tmp rather than the application directory.
Re-work the tox deployment so that we mount the application directory as a read-only volume rather than copying the file in when building the image. This has the following advantages: 1. We do not build a new image each time we run tests. (This is nicer to those of us with finite disk space.) 2. Running tests is slightly faster since a new image is not being built. 3. The application directory is mounted read-only so we catch code which accidentally writes to the current directory. 4. We can use the upstream tox image rather than rolling our own derived image. In order to make to happy to run in a read-only environment, we specify that a) it does not run sdist to write an .egg-info directory and b) that coverage data is stored in /tmp rather than the application directory.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.