automate building of tripal 2 and 3

[bradfordcondon]

tripal/tripal#357

• When something is pushed to tripal 2-x, let's rebuild the docker container.

• When a new tripal 3 release candidate is created (? or a new PR merged? Not sure which) let's rebuild the tripal 3 container.

[almasaeed2010]

Since these containers are made specifically for testing purposes, we can trigger a rebuild of the most recent tripal2/3 "master" branch. This won't affect others since we won't push to Docker hub until they are tested or when the tests we've setup pass.

[bradfordcondon]

Hmm ok. And in theory if the previous PR didn't break (specifically running drush updatedb) then the chain going back to the release didn't either?

Since these containers are made specifically for testing purposes

I think they are also great for development purposes...

If we want builds for specific releases, we can think about creating them.

[almasaeed2010]

Yeah if the update and rebuild tests pass, we are good to go.

As to being dev containers, people will have to specify a version that contains a similar env to their live sites such as the tripal and drupal versions.

[bradfordcondon]

additional request: #9 automate pulling dev seed repo's "latest dump" file and loading it in, saving the release as tripal3 with data or something similar.