Skip to content
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

Added travis configuration for auto builds #18

Merged
merged 4 commits into from
Jul 12, 2016
Merged

Added travis configuration for auto builds #18

merged 4 commits into from
Jul 12, 2016

Conversation

bkuhl
Copy link
Collaborator

@bkuhl bkuhl commented Jul 11, 2016

  • Added travis configuration

Travis-CI is free for public repos. To setup travis, go to https://travis-ci.org and add this repository. Go to the settings within that repository and set the following environment variables:

  • DOCKER_EMAIL
  • DOCKER_USERNAME
  • DOCKER_PASSWORD

These environment variables enable Travis-CI to login to docker... the user should have write permissions to the repo. The below segment is executed if all other steps pass successfully. This process will not run in the event of any kind of terminating failure (such as failure to docker build). The travis-ci process gets run at every pull request and/or push (depending on how you configure the repo) this section is only executed when a new github release is made. This means creating a new Release will trigger the CI build process and will eventually get pushed to DockerHub.

deploy:
  provider: script
  script: docker push "${DOCKER_REPO}:${TRAVIS_TAG}"
  skip_cleanup: false
  on:
    tags: true

@bkuhl
Copy link
Collaborator Author

bkuhl commented Jul 11, 2016

With this PR, the only steps left are:

  • Updating the Dockerfile to accept a version number instead of always using the latest
  • Automatically publishing a GitHub release when a new version of the game is detected (see https://github.com/bkuhl/game-watcher)

@zopanix zopanix merged commit beff8cd into zopanix:master Jul 12, 2016
@bkuhl
Copy link
Collaborator Author

bkuhl commented Jul 12, 2016

It can be a really good idea to add a status badge to the project readme. This makes it really clear if the latest build is passing or not and allows you and others to quickly review the build process for builds.

@bkuhl
Copy link
Collaborator Author

bkuhl commented Jul 17, 2016

With other PRs coming in for changing functionality, this repo could benefit from travis-ci configuration.

This was referenced Jul 19, 2016
@zfarrell
Copy link
Contributor

@zopanix - do you have an ETA of when you'll be able to get to this?

I'm grateful for the hard work you've put into this repo thus far. However the updates are noticeably delayed. Implementing this issue seems like it would resolve the delay issue.

Would you be open to adding additional maintainers to help distribute the workload? I'd like to avoid creating a duplicate project, but i keep finding myself starting the process of it just so that i can get an up-to-date server :)

@bkuhl
Copy link
Collaborator Author

bkuhl commented Jul 28, 2016

👍 I'm in the same boat as zfarrell

dhuette13 pushed a commit to dhuette13/docker_factorio_server that referenced this pull request Aug 7, 2016
Added travis configuration for auto builds
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.

3 participants