-
Notifications
You must be signed in to change notification settings - Fork 98
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
Setup automated build on GitHub #200
Comments
If using CodeShip:
A branch protection for
|
This is great idea and I'll definitely look into getting this set up. I might need to get a hold of the repository owner to put this together, though. I did have another thought, however: What do you think about dogfooding this project with Bitbucket and Jenkins? I wouldn't mind reaching out to Atlassian for a freebie server license. |
Having a Bitbucket + Jenkins setup would be great for integration tests. Nevertheless, I don't think we should use that setup for continuous integration, as our build would be dependent on the code we are actually maintaining (circular loop). The latest major BitBucket release is a good example, as the plugin was not working with that version but we would have needed the plugin to approve any pull request to fix the issue. |
Strangely enough, no automated build has been set up for this project. This would allow to perform a first check of all pull requests before a manual review is done.
CodeShip could be a good option, as it allows 100 free builds per months, which should be more than enough for this project.
This depends on PR #199, as it contains the dependency version fix required for automated builds.
The text was updated successfully, but these errors were encountered: