> On 3 Apr 2020, at 19:13, Christopher Head <open...@chead.ca> wrote: > > ... why is it problematic to just > stand up a simulator environment somewhere else, outside Travis—perhaps > on an AWS container, booted on demand, or something of the sort,
Can you suggest a free solution for setting such a simulator environment? It needs to be accessible from Travis, which means a public ip address and outgoing access allowed from inside Travis to it (I know that it is possible to do some deployment from Travis, i.e. to initiate outgoing connections, but I don't know what the restrictions are, if any). > or > maybe it would even work in a Docker container, since that seems to be > the popular solution these days, and runnable under many hosts—so that > the simulator can run in the one environment where it’s known to work > well, and have the OpenOCD instance running under Travis connect to it? Being a heavy Docker user, I like this solution. Just that it needs two Docker images, one for Intel and one for Arm machines. Unfortunately, please correct me if I'm wrong, the Windows and macOS virtual machines available on Travis do not have Docker installed. :-( Regards, Liviu _______________________________________________ OpenOCD-devel mailing list OpenOCD-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openocd-devel
