Note that there are some explanatory texts on larger screens.

plurals
  1. POJenkins Windows slave failing the Play! framework build
    primarykey
    data
    text
    <p>We are using the Play! framework and I've setup our Jenkins CI to run auto-test and other things on a master Unix machine. As a second step I want to setup a windows slave to run some in browser webdriver tests. Unfortunately my build doesn't get to that point. The source checks out fine in the workspace directory. As a first build step I run </p> <pre><code>play clean </code></pre> <p>Which seems to fail everytime. I've given full permissions to admin for that directory and I'm running the jenkins slave under that administrator like so</p> <pre><code>runas /noprofile /user:DOMAIN\Administrator "javaws http://jenkins:8080/computer/Keith/slave-agent.jnlp" </code></pre> <p>The console output I see from jenkins is:</p> <pre><code>Building remotely on Keith in workspace C:\Documents and Settings\administrator\My Documents\Jenkins\workspace\windows Updating http://svnrepo.. At revision 448 no change for http://svnrepo.. since the previous build play path is C:\Software\Play\play Executing C:\Software\Play\play clean "C:\Documents and Settings\administrator\My Documents\Jenkins\workspace\windows" [windows] $ C:\Software\Play\play clean "C:\Documents and Settings\administrator\My Documents\Jenkins\workspace\windows" Build step 'Play!' marked build as failure Finished: FAILURE </code></pre> <p>Note that when I run the command below manually on the windows box it works fine:</p> <pre><code>C:\Software\Play\play clean "C:\Documents and Settings\administrator\My Documents\Jenkins\workspace\windows" </code></pre> <p>Anyone got any ideas what I'm doing wrong?</p> <p>Thanks!</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload