Skip to content

[Bioc-devel] bioconductor/metabolomics Docker image available

3 messages · Neumann, Steffen, Dan Tenenbaum, Obenchain, Valerie

Neumann, Steffen
# 
Hi Dan and BioC community!

I now cleaned up my?Bioconductor/bioc_docker?
and opened a pull request to add a Metabolomics?
Bioconductor [1].

This works on our Jenkins installation, where I regularly?
build the devel_metabolomics [2] and release [3] images.

The image for the previous devel version (BioC-3.3) does build,?
but the image for the old release version (BioC-3.2) does not,?
due to the mzR issue on new gcc we talked about a few months ago.

If you want, I can send a second pull request?
and modify?bioc_docker/config.yml to use the current?
versions 3.3 for release, and 3.4 for devel.

A more general question, what is the current docker strategy?
for Bioconductor. Are they build/tested on a regular basis ?
Are failure reported to package maintainers, or should they ??
Should the docker images be part of the regular checkResults report ?

Yours,?
Steffen

[1]?https://github.com/Bioconductor/bioc_docker/pull/4
[2] http://phenomenal-h2020.eu/jenkins/job/bioc_docker_devel_metabolomics/
[3]?http://phenomenal-h2020.eu/jenkins/job/bioc_docker_release_metabolomics
Dan Tenenbaum
# 
----- Original Message -----
Yes, please do this.
Built daily, but not tested.
Failure is not reported to anyone, it probably should be.
I think they should be in a separate report, but perhaps one that lives under /checkResults.

Dan
Obenchain, Valerie
# 
Hi Steffen,
On 07/27/2016 09:11 AM, Dan Tenenbaum wrote:
As you're probably aware, many of the containers were failing to build
due (in part) to outdated versions. Dan updated config.yml yesterday and
we are monitoring the builds of the other containers.

Can you please merge your branch with master and update your pull
request (i.e., no changes needed to config.yml )?

Thanks.
Valerie
This email message may contain legally privileged and/or confidential information.  If you are not the intended recipient(s), or the employee or agent responsible for the delivery of this message to the intended recipient(s), you are hereby notified that any disclosure, copying, distribution, or use of this email message is prohibited.  If you have received this message in error, please notify the sender immediately by e-mail and delete this email message from your computer. Thank you.