Jenkins CI now running tests

Ted Mielczarek ted at
Thu Apr 30 00:54:23 UTC 2015

On Wed, Apr 29, 2015, at 07:57 PM, Robert O'Callahan wrote:
> On Thu, Apr 30, 2015 at 4:41 AM, Ted Mielczarek
> <ted at> wrote:
>> Obviously this isn't a great long-term solution, but it should
>> be okay
as a stopgap to have test coverage until we figure something better out.
> What do you mean by that?

This is currently just a DigitalOcean VM that I spun up using my
personal account (I'll expense the cost). If it gets shut down for some
reason we'll have to set it back up manually. I set up a cron job to
backup the Jenkins configuration, and the machine configuration isn't
particularly complicated, but that's still a hassle. It would be nice to
get things onto a more-well-supported setup, is what I mean. I think the
two most reasonable options here would be:
1) Find an unused server sitting in a datacenter somewhere with a new
   enough chipset that we can reimage and install Jenkins on, replicate
   the setup from my DigitalOcean VM (we could probably even just set it
   up as a Jenkins slave and put the config on
2) Get someone to fix the Taskcluster bug I filed[1] about supporting
   on-demand DigitalOcean VMs, use TaskCluster as our CI.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the rr-dev mailing list