<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Dec 6, 2014 at 7:27 PM, Wes Turner <span dir="ltr"><<a href="mailto:wes.turner@gmail.com" target="_blank">wes.turner@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote"><span class="">On Sat, Dec 6, 2014 at 9:07 AM, Donald Stufft <span dir="ltr"><<a href="mailto:donald@stufft.io" target="_blank">donald@stufft.io</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word"><div><div><div><br></div></div></div><div>Heh, one of my thoughts on deploying the bug tracker into production was via a container, especially since we have multiple instances of it. I got side tracked on getting the rest of the infrastructure readier for a web application and some improvements there as well as getting a big postgresql database cluster set up (2x 15GB RAM servers running in Primary/Replica mode). The downside of course to this is that afaik Docker is a lot harder to use on Windows and to some degree OS X than linux. However if the tracker could be deployed as a docker image that would make the infrastructure side a ton easier. I also have control over the python/ organization on Docker Hub too for whatever uses we have for it.</div></div></blockquote><div><br></div></span><div>Are you referring to <a href="https://registry.hub.docker.com/repos/python/" target="_blank">https://registry.hub.docker.com/repos/python/</a> ?</div><div><br></div><div>IPython / Jupyter have some useful Docker images:</div><div><br></div><div>* <a href="https://registry.hub.docker.com/repos/ipython/" target="_blank">https://registry.hub.docker.com/repos/ipython/</a></div><div>* <a href="https://registry.hub.docker.com/repos/jupyter/" target="_blank">https://registry.hub.docker.com/repos/jupyter/</a></div><div><br></div><div>CI integration with roundup seems to be the major gap here:</div><div><div><br>* <a href="https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin" target="_blank">https://wiki.jenkins-ci.org/display/JENKINS/Docker+Plugin</a><br></div></div><div>* <a href="https://wiki.jenkins-ci.org/display/JENKINS/saltstack-plugin" target="_blank">https://wiki.jenkins-ci.org/display/JENKINS/saltstack-plugin</a></div><div>* <a href="https://github.com/saltstack-formulas/docker-formula" target="_blank">https://github.com/saltstack-formulas/docker-formula</a></div></div></div></div></blockquote><div><br></div><div>ShiningPandas supports virtualenv and tox, but I don't know how well suited it would be</div><div> for fail-fast CPython testing across a grid/graph:</div><div><br></div><div>* <a href="https://wiki.jenkins-ci.org/display/JENKINS/ShiningPanda+Plugin">https://wiki.jenkins-ci.org/display/JENKINS/ShiningPanda+Plugin</a></div><div>* <a href="https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Project+Plugin">https://wiki.jenkins-ci.org/display/JENKINS/Matrix+Project+Plugin</a></div></div><br></div><div class="gmail_extra">The branch merging workflows of <a href="https://datasift.github.io/gitflow/IntroducingGitFlow.html">https://datasift.github.io/gitflow/IntroducingGitFlow.html</a> (hotfix/name, feature/name, release/name) are surely portable across VCS systems.</div><div class="gmail_extra"><br></div></div>