Nightly Builds and Other Infrastructure

Colin Clark colinbdclark at
Thu Jan 30 01:27:05 UTC 2014

That sounds pretty convincing to me. Let's do it. 


On Jan 29, 2014, at 6:45 PM, "Gill, Avtar" <agill at> wrote:

>> Can someone outline the features and benefits that Jenkins will provide us in comparison to a simple script that listens for Github hooks? I’m sure there are good ones, I’d just like to hear them enumerated.
> Jenkins would allow one to view all builds and statuses (whether a build was successful or not) in one location. In addition to serving build artifacts it would also provide a history of each build showing how each commit affected a particular project. Having scripts triggered by commits could result in an unwieldy process as time goes on as opposed to a more scalable approach of letting Jenkins oversee the testing process and then pushing the resulting artifacts to VMs that would be dedicated to just serving them. If TestSwarm (or an alternative like needs to be revived in the future we will benefit by having Jenkins in the picture along with its various plugins.

More information about the fluid-work mailing list