search

BD2KGenomics / ga4gh-integration-deprecated

Tracking for ga4gh-integration projects
1 stars 2 forks source link

Switch to jenkins from travis #65

Open david4096 opened 7 years ago

david4096 commented 7 years ago

We should be able to host and maintain our own CI process. Some of the features of travis might have to be migrated to other services.

dcolligan commented 7 years ago

What's wrong with travis? Setting up our own build processes is a huge headache, and travis has been easy enough to maintain, not to mention incredibly convenient.

david4096 commented 7 years ago

It was down the other day affected by S3 outage. We're trying to build a decentralized network of services and relying on a centralized service that we can't repeat for deploy is flawed.

It is incredibly convenient and offers features Jenkins doesn't have out of the box. This issue is low urgency, but I hope that we can aspire to having our entire process replicable without needing cloud services. When one S3 region went down, dockstore, and quay did as well.

These kinds of outages give temporary attention to the huge assumptions we make in using freemium services. I'm hoping to capitalize on it a little bit to improve our infrastructure. Amplab has a jenkins instance we could use I'm sure if we wanted to piecewise make this transition.

It's a sign of maturity of the project to begin maintaining its own scaffolding and release processes. The ease of use draws in the early Open Source project, and the nice features make them stay!

dcolligan commented 7 years ago

We're not running a critical live service and can tolerate an S3 outage. The benefits of using travis, github, rtd, etc. way outweigh the costs.

Maybe there's a specific compelling case for setting up a Jenkins server somewhere, but all other things being equal I'd rather avoid it. Admining the Jenkins instance(s) and the server it is on can be a time consuming business.