New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Travis deploy integration #333

Merged
merged 2 commits into from Nov 16, 2017

Conversation

Projects
None yet
2 participants
@badboy
Contributor

badboy commented Nov 16, 2017

After experiencing problems with the old documented way of manually doing the import and push I simply switched over to Travis' native method and it works without a hassle.

github_token: $GH_TOKEN
local_dir: build
on:
branch: master

This comment has been minimized.

@epage

epage Nov 16, 2017

Member

So this will automatically push the results of cobalt build into the appropriate branch?

Have a link where I can learn more?

@epage

epage Nov 16, 2017

Member

So this will automatically push the results of cobalt build into the appropriate branch?

Have a link where I can learn more?

This comment has been minimized.

@badboy

badboy Nov 16, 2017

Contributor

Oh sorry. I put a link to the documentation into the commit message but forgot to include it in the PR text, here it is: https://docs.travis-ci.com/user/deployment/pages/

It pushed into gh-pages by default but this can be configured.

@badboy

badboy Nov 16, 2017

Contributor

Oh sorry. I put a link to the documentation into the commit message but forgot to include it in the PR text, here it is: https://docs.travis-ci.com/user/deployment/pages/

It pushed into gh-pages by default but this can be configured.

@epage epage merged commit 0e40793 into cobalt-org:master Nov 16, 2017

0 of 2 checks passed

continuous-integration/appveyor/pr AppVeyor build failed
Details
continuous-integration/travis-ci/pr The Travis CI build failed
Details
@epage

This comment has been minimized.

Show comment
Hide comment
@epage

epage Nov 16, 2017

Member

Thanks! This is much better for our users.

In general, I need to revamp the documentation. That is planned for 0.10.

btw in 0.10 I'm looking to break compatibility in major ways but provide a upgrade utility. My current plan is to test against the example sites. Feel free to let me know of your site if you'd want me testing it too.

Member

epage commented Nov 16, 2017

Thanks! This is much better for our users.

In general, I need to revamp the documentation. That is planned for 0.10.

btw in 0.10 I'm looking to break compatibility in major ways but provide a upgrade utility. My current plan is to test against the example sites. Feel free to let me know of your site if you'd want me testing it too.

@epage

This comment has been minimized.

Show comment
Hide comment
@epage

epage Nov 16, 2017

Member

I've now created #334 to track my test cases.

Member

epage commented Nov 16, 2017

I've now created #334 to track my test cases.

@epage epage referenced this pull request Dec 21, 2017

Closed

Travis is disabled. #4

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment