feat(build): added support for publishing api docs and showcase using Travis

[dsebastien]

Issues closed: #282

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/NationalBankBelgium/stark/blob/master/CONTRIBUTING.md#-commit-message-guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x] Build related changes
[x] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

We generate our docs but don't publish them

Issue Number: #282

What is the new behavior?

We publish the api docs and the showcase on GitHub pages.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

The solution is not complete yet, because other issues need to be tackled for this to be effective; for example #415

[dsebastien]

To actually test this, we'll need to create a release.
I also noticed that the current npm packages we publish still refer to ...alpha.2 as the "next", which doesn't make much sense if the next will actually be at least alpha.3 ^^

[SuperITMan]

Should not we create a specific email address (NBB) for Stark on GitHub ?

[dsebastien]

Yes but no :)

[SuperITMan]

Actually, when we do a release, I think we should update the version to the next patch/minor one automatically 😊
Except for now, of course, because we are still in alpha version.

[coveralls]

Coverage remained the same at 94.247% when pulling 5d53f7a on dsebastien:feature/ghdeploy into 69ee8f4 on NationalBankBelgium:master.

[dsebastien]

@christophercr, @RobbyDeLaet I leave this up to you guys :)
I think you could test the push operation from Robby's laptop.
If the script doesn't work now, it probably means that the SSH key ain't used.

Here's the alternative I had found: https://gist.github.com/douglasduteil/5525750

[christophercr]

This could be another alternative: https://gist.github.com/willprice/e07efd73fb7f13f917ea

[christophercr]

@dsebastien I tested again this and indeed the SSH key wasn't used when doing the git clone/push.

So I used the other alternative you mentioned, and that works, this is the log of the successful build of my fork: https://travis-ci.org/christophercr/stark/jobs/393357177

I've adapted my fork so you can see the changes I did compared to what you have (but you need to rebase yours with the latest changes from the master): dsebastien/stark@feature/ghdeploy...christophercr:feature/ghdeploy

[dsebastien]

Great!

Don’t hesitate to just adapt your fork and PR/merge that in upstream :)

[christophercr]

Closed in favor of this PR #445 which contains the final working solution.