strategy for travis-ci builds of dynamo journal

[sclasen]

Two ways to go.

• Disabled for travis
• create an amazon account, and a set of locked-down-as-possible IAM credentials and then do this kind of thing
  http://about.travis-ci.org/docs/user/travis-pro/#How-can-I-encrypt-files-that-include-sensitive-data%3F

[krasserm]

I think disabling for Travis in a first step together with a Wiki page how people can manually enable and run it is good enough. Sooner or later, the dynamodb journal test should of course run automatically.

At the moment I'm not sure whether to continue with Travis CI or setup Jenkins on a (public) Linux image. I currently have Jenkins running at home. Depending how we'll get issue #59 resolved, we should choose only one of them. The proposed encryption strategy sounds good enough for me, should we decide for Travis ... I trust all committers :)