[util] Continuous Deployment Support

[gaocegege]

Type

• util/workflow

Related

• [post] Google SRE 阅读笔记(1)-监控 #9

Description

Now We have to run pre-deploy every time we update the source code. the work should be done by our lovely travis.

[gaocegege]

netlify could do it.

[gaocegege]

No, netlify could not do it.

[at15]

we can add after_success to let travis build and push to master or another branch

git checkout -b travis/post-xxxx
git commit -m Build commit-id
git push origin travis/post-xxx

btw: I didn't see any config file for nelify like .travis.yml, and does nelify handle non-master branches?

[gaocegege]

I set netlify to publish docs/ directory, and it will make a preview for PR.

[gaocegege]

Netlify does not need a config, but you could add it if you like.

[at15]

@gaocegege I think netlfiy is broken now, no update after #59 merged

btw: netlify has deploy preview on PR and we can get rid of travis, travis-ci.org is broken already anyway ... I see nothing after # to travis-ci.com w/ github, I guess they do not share data.

[at15]

We are using gh-pages and requires running scripts/pre-deploy to commit and push the rendered html.
The netlify config is not working.