Closed bkuhl closed 8 years ago
With this PR, the only steps left are:
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.
With other PRs coming in for changing functionality, this repo could benefit from travis-ci configuration.
@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 :)
👍 I'm in the same boat as zfarrell
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.