memory limit error due to outdated tripal version

[slmcevoy]

trying to import Sequence Ontology via the OBO Vocaulary Loader
php mem limit set to 200M

2019-01-11 16:53:41
Tripal Job Launcher
Running as user 'admin'

2019-01-11 16:53:41: There are 5 jobs queued.
2019-01-11 16:53:41: Job ID 72.
2019-01-11 16:53:41: Calling: tripal_tripal_cron_notification()
2019-01-11 16:53:44: Job ID 73.
2019-01-11 16:53:44: Calling: tripal_expire_collections()
2019-01-11 16:53:44: Job ID 74.
2019-01-11 16:53:44: Calling: tripal_expire_files()
2019-01-11 16:53:44: Job ID 75.
2019-01-11 16:53:44: Calling: tripal_run_importer(40)

Running 'OBO Vocabulary Loader' importer
NOTE: Loading of file is performed using a database transaction.
If it fails or is terminated prematurely then all insertions and
updates are rolled back and will not be found in the database

Downloading URL http://purl.obolibrary.org/obo/go.obo, saving to /tmp/obo_J37FZy
Step 1: Preloading File /tmp/obo_J37FZy...
PHP Fatal error: Allowed memory size of 209715200 bytes exhausted (tried to allocate 20480 bytes) in /var/www/html/sites/all/modules/custom/tripal/tripal_chado/includes/TripalImporter/OBOImporter.inc on line 2046
PHP Fatal error: Allowed memory size of 209715200 bytes exhausted (tried to allocate 20480 bytes) in /root/.composer/vendor/drush/drush/includes/preflight.inc on line 770

[bradfordcondon]

follow up to this: we resolved the issue by updating to the 7.x-3.x release.

The docker container needs to launch with 7.x-3.x instead of rc3.

[almasaeed2010]

Unfortunately I don't docker allows us to rebuild when a repo updates? If that's possible we can rebuild every time Tripal releases a new version. I thought of using Travis, but we'd have to log-in to docker hub to be able to upload a new release.

[bradfordcondon]

https://docs.docker.com/docker-hub/builds/

this documents how to automate the builds. I'll set it up for tripal3 and see how it works.

https://cloud.docker.com/u/statonlab/repository/docker/statonlab/tripal3/builds

ideally dockerhub will build for each merged PR on the given branch.... not sure how releases will work but would be awesome if we configured it to create a tag for each release as well.

edit: concusion: automated builds are only convenient if hte Dockerfile is in the same repository as the code you are watching. It's a much more difficult prospect to have our repo here auto-build based on changes in core.