http://localhost/ticket/2344 <p> After checking out a commit to test from CKAN's <a class="missing wiki">GitHub?</a>, Jenkins runs a script that creates a new virtual environment and installs CKAN and its dependencies into it, and does some other necessary tasks. Jenkins then runs the tests in this virtualenv. </p> <p> The install script may have to change from one commit to the next as CKAN's install instructions change, so it would be good if the script was shipped in CKAN core. That way Jenkins will run different versions of the script depending on which commit it's testing and if the tests fail because the script is wrong then that's actually a bug that needs to be fixed in CKAN core. Also the CKAN install instructions could be simplified a lot by just having users run this script instead of doing each step by hand. </p> en-us http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png http://localhost/ticket/2344 Trac 0.12.3 seanh Tue, 01 May 2012 13:34:03 GMT http://localhost/ticket/2344#comment:1 http://localhost/ticket/2344#comment:1 <ul> <li><strong>priority</strong> changed from <em>awaiting triage</em> to <em>minor</em> </li> </ul> Ticket seanh Tue, 01 May 2012 15:14:09 GMT http://localhost/ticket/2344#comment:2 http://localhost/ticket/2344#comment:2 <ul> <li><strong>milestone</strong> changed from <em>current-ckan-sprint-2012-05-15</em> to <em>ckan-v1.8</em> </li> </ul> Ticket seanh Mon, 18 Jun 2012 17:27:29 GMT http://localhost/ticket/2344#comment:3 http://localhost/ticket/2344#comment:3 <ul> <li><strong>keywords</strong> <em>[2d]</em> removed </li> <li><strong>status</strong> changed from <em>new</em> to <em>closed</em> </li> <li><strong>resolution</strong> set to <em>duplicate</em> </li> </ul> Ticket