-
Notifications
You must be signed in to change notification settings - Fork 160
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
Continuous Integration Support #1
Comments
I think we can have both... TeamCity(https://www.jetbrains.com/teamcity/) is free for a small project.
which should be sufficient for the development of bigflow. TeamCity also works nicely with IDEs came from JetBrains. The only downside is that we have to run teamcity somewhere and requires operating. |
I've already set travis-ci up, and it works just fine. With the help of the travis-ci, now we can run our ci job at every commit on master & every pull request. If any code committed to the master, github pages will be generated to this page, and a release file will be uploaded to here. But at this moment, there are 3 more things to do:
|
I was so naive... On travis-ci.com, the ci tests ran perfect in about one hour, but now on travis-ci.org it just ... not work. So speeding up the build becomes more important than before. |
Well you could use https://en.m.wikipedia.org/wiki/Ccache for massively speeding up the builds, or the mozilla fork (which support rust too) https://github.com/mozilla/sscache. Also, HS : it's a nice to have (for security and stability reason) feature : https://github.com/Microsoft/checkedc |
Continuous integration is required for bigflow, and we should have a system to support continuos integration.
Maybe we can use travis-ci.org, or teamcity, or we can set up a jenkins at BCC (Baidu Cloud Compute)?
The text was updated successfully, but these errors were encountered: