Skip to content

Conversation

@kpp
Copy link

@kpp kpp commented Jun 22, 2017

  • To enable TravisCI builds you have to login in https://travis-ci.org/, and add your repo.
  • To enable artifacts you have to create a bucket in Amazon S3 located in US East (N. Virginia), add the following env variables into Travis config via web interface:
  • ARTIFACTS_PERMISSIONS="public-read"
  • ARTIFACTS_SECRET="YOUR S3 secret key" [hidden]
  • ARTIFACTS_KEY
  • ARTIFACTS_BUCKET

Enable S3 ACL: https://docs.travis-ci.com/user/uploading-artifacts/

@kpp kpp force-pushed the travis branch 17 times, most recently from 799db58 to 3091652 Compare June 22, 2017 19:32
@kpp kpp changed the title Added .travis.yml Added .travis.yml [Work In Progress] Jul 11, 2017
@kpp kpp force-pushed the travis branch 6 times, most recently from a210783 to fff16fe Compare July 12, 2017 13:31
@kpp kpp changed the title Added .travis.yml [Work In Progress] Added .travis.yml Jul 12, 2017
@kpp
Copy link
Author

kpp commented Jul 24, 2017

@tscmoo hello?

@tscmoo
Copy link
Collaborator

tscmoo commented Jul 31, 2017

Sorry, hi.

I'm not sure that I want ci/automated builds for this project right now. Is there some precedent for this (irc talks)?

@kpp
Copy link
Author

kpp commented Jul 31, 2017

CI builds take 0 minutes of your time, protecting master from merging broken commits (as you did it right now). So I don't understand why you don't want this feature.

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants