How to configure Travis CI better for auto push to git branch?

Asked Jan 01 '16 at 22:12

Active Jan 01 '16 at 23:02

Viewed 170 times

I'm developing a project at GitHub and using TravisCI. On GitHub, there's an option, which allows one to use one branch gh-pages to publish static web content online on http://<user>.github.io/<repo>.

As my project is a frontend one (WebGL/JavaScript) and doesn't require any backend, I decided to try the following deployment process:

Push to master, which will fire the CI service to build an application and run unit-tests.
If building and testing the app on Travis succeeds, then push the results to the gh-pages branch, where later the static content will be available in the following sub-directory:

/<commit#>.<build#>/<payload> (e.g. /925dc3e.4/index.html)

The scheme itself is simple, but I'm afraid because of security reasons. I understand, that showing the password in some sort of a config file is a very bad idea. However, I've found the encryption keys in Travis CI service feature, but am not sure, whether it's secure enough, or insecure at all?

edited Jun 20 '20 at 09:12

Community

asked Jan 01 '16 at 22:12

1

"Is it enough secure or insecure at all?" It's secure enough to use (the encryption is per-slug). I autodeploy to `gh-pages` myself on my project, you can see the `.travis.yml` [here](https://github.com/nabijaczleweli/BearLibTerminal.rs/blob/master/.travis.yml#L39-L49). – набиячлэвэли Jan 01 '16 at 22:28
@набиячлэвэлиь thanks! it's great :) – Jan 01 '16 at 22:42
How about using the `after_success` section instead? – localheinz Jan 02 '16 at 01:19
@localheinz I pointed it out to him, in [the chat](http://chat.stackoverflow.com/rooms/84081/loungegaem), later on – набиячлэвэли Jan 03 '16 at 00:01

How to configure Travis CI better for auto push to git branch?

0 Answers0