keplersj
commented
10 years ago I've been playing around with a couple different CI options because of this. Travis was never really built for projects like BoatCraft in the first place, it was built for Ruby and Node projects.
The options.
Travis-CI (My least favorite)
- Starts with a clean workspace every build. :green_heart:
- Downloads dependencies every build :red_circle:
- Works out of the box with Coveralls :green_heart:
- Does not allow for artifact publishing. :red_circle:
- Builds for every pull request, pull request push, and regular push. :green_heart:
- 99.99% Uptime :green_heart:
- Unlimited Space :green_heart:
- Free :green_heart:
Drone.io (My middle-ground favorite)
- Consistent workspace :green_heart:
- Caching Dependencies :green_heart:
- Allows for Scala building-as-needed. :green_heart:
- Allows for Artifact publishing :green_heart:
- But the publishing is through there website, not over Maven. :red_circle:
- Limited space :red_circle:
- Free :green_heart:
- Builds every push. :green_heart:
- Doesn't really work with Coveralls right now. :red_circle: I'm sure we could ask @kt3k about this though.
- 99.99% Uptime :green_heart:
- Can build nightlies. :green_heart:
Home-made Server (My Favorite, Experimental Option)
- Consisten Workspace :green_heart:
- Caching Dependencies :green_heart:
- Allows for Scala Building as needed. :green_heart:
- Allows for Artifact Publishing :green_heart:
- Publishes Artifacts using Maven (Artifactory) :green_heart:
- "Unlimited" Storage :green_heart:
- Can build actual nightlies. :green_heart:
- Can build every push and pull request. :green_heart:
- Unknown uptime. :red_circle:
- Might have to switch to a VPS eventually. :red_circle:
- Code Coverage happens on server. (Replaces Coveralls) :green_heart:
viliml
Is that really necessary? Could we store the dependencies in a zip somewhere and just get them to somewhere prior to the travis call? If not, just close this.