search

dyweb / blog

Dongyue Tech Blog
https://blog.dongyueweb.com
14 stars 7 forks source link

[util] Continuous Deployment Support #14

Open gaocegege opened 7 years ago

gaocegege commented 7 years ago

Type

Related

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 commented 7 years ago

netlify could do it.

gaocegege commented 7 years ago

No, netlify could not do it.

at15 commented 7 years ago

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 commented 7 years ago

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

gaocegege commented 7 years ago

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

at15 commented 1 year ago

@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 sign in to travis-ci.com w/ github, I guess they do not share data.

at15 commented 1 year ago

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