Closed arschles closed 8 years ago
@arschles @slack @sgoings
This is the solution we have in place at present:
We should consider the above "experimental" in terms of process, especially the federated responsibility among Jenkins and travis. This experimental phase will give us some real-world experience (pros/cons) with both Jenkins and travis, during which we can tease out the various CI options of both platforms; and at the conclusion of which we'll have the expertise to build a permanent CD-type workflow (using only Jenkins or only travis) for the API. At that point we'll create a follow up issue w/ details on implementation objectives.
We'll favor Jenkins over travis, which is the company-wide idiom at this point (unless we determine that travis more effectively does what we want).
This issue is for setting up auto deployment to production. It's intended for the following: