Infrastructure

Integration testing

We currently use Codeship for integration testing. Codeship uses github for authentication and requires access to the repository to set the hooks. We have created a separate github user, @kframework-bot, which has full access to the kframework repository. To adjust any integration test settings, login into Codeship using this github user, select the project, and go to the "Test Settings" page under "Project Settings".

For documentation, the "Setup Commands" contains:

jdk_switcher use oraclejdk8

and the "Test commands" contains:

mvn verify

KWeb

• kweb is deployed in /srv/kweb. The code is in /srv/kweb/kweb and the workspaces are stored in /srv/kweb/kfiles.
• The K deployment it uses is the one rooted at /k on that box. Currently this is a symlink to /var/www/imgs/releases.
• Each user on kweb has a workspace when creating an account. This workspace is their version of the files they are working on. By default, /k/samples and /k/tutorials are copied into kweb workspaces into the samples and tutorials "collections" (top level folders in kweb are collections).
• The kweb README is here and describes setting up an instance: https://github.com/kframework/kweb. The deployment on fslweb uses an Apache CGI script as described here: http://flask.pocoo.org/docs/0.10/deploying/cgi/. The CGI script is modified to do things like modify the K options environment variable and the user PATH (to make sure the right version of Java is used).