Added dockerhub trigger

[Luzifer]

As discussed in #1685 this trigger will fire after the ipfs cmd has been built and trigger a DockerHub build for the jbenet/go-ipfs repo on DockerHub.

Encrypted target was created by using this command:

# echo -n 'https://registry.hub.docker.com/[...]/' | gobuilder-cli --repo=github.com/ipfs/go-ipfs encrypt
Go ahead and type your secret ...
U2FsdGVkX18fMPhIZ3k1QDCwnB49ln6DdyvIH2tDDHxTZi3Q3DQ7AKWllo9KngxwteX2dBFQ2P+jLEBh12PEEqOkN2SePNbMhMtmk/c4siHVAqo5wnf8Utgqob0jB40sobmqNN9X3Y/W2yb72LuGJg==

closes #1685

[GitCop]

There were the following issues with your Pull Request

• Commit: 662a614
  • Invalid signoff. Commit message must end with
    License: MIT
    Signed-off-by: .* <.*>

Guidelines and a script are available to help. Your feedback on GitCop is welcome on this issue.

---

This message was auto-generated by https://gitcop.com

[Luzifer]

@jbenet PTAL

[jbenet]

thanks @Luzifer

[jbenet]

Did this work?

• gobuilder built: https://gobuilder.me/github.com/ipfs/go-ipfs/cmd/ipfs
• docker hub doesn't seem to have: https://hub.docker.com/r/jbenet/go-ipfs/builds/

[Luzifer]

Yeah the .gobuilder.yml has some issues:

ERRO[789001] Unable to send notification                   error=invalid padding host=eagle repo=github.com/ipfs/go-ipfs/cmd/ipfs

Might result from OpenSSL encryption…

Possible solutions:

• Use the dockerhub trigger URL in plain text (just replace encoded blob)
• Find out why it's complaining

[ghost]

Could you document the github -> gobuilder -> dockerhub build chain somewhere in the infrastructure.git readme? Nothing fancy, just to have it written down that it exists.

[Luzifer]

Used the wrong repo as the encryptor… m( I'm sorry…

[jbenet]

no worries! :)