We was to make sure that we always are using bioconductor 3.6 and R 3.4.2. Since these have been accidentially upgraded in an effort to fix the deploy process I think it might make sense to "document" it in the form of a test that reads the files and checks to make sure that the correct versions are being installed.
Problem or idea
We should parse the lock files / docker files / anything else that installs packages and write a test if the version is set to latest or anything that isn't the version that we want.
Solution or next step
Write the test that verifies the version and make sure that the error messages are descriptive enough to explain that changing these versions needs to be confirmed by the science team.
Context
We was to make sure that we always are using bioconductor 3.6 and R 3.4.2. Since these have been accidentially upgraded in an effort to fix the deploy process I think it might make sense to "document" it in the form of a test that reads the files and checks to make sure that the correct versions are being installed.
Problem or idea
We should parse the lock files / docker files / anything else that installs packages and write a test if the version is set to latest or anything that isn't the version that we want.
Solution or next step
Write the test that verifies the version and make sure that the error messages are descriptive enough to explain that changing these versions needs to be confirmed by the science team.