1.559 does not have the problem, 1.560 does. To reproduce, create a job with a shell build step and following code :

dd if=/dev/urandom of=target.out bs=1M count=50
for a in 1 2 3 4
do
cat target.out >> bigtarget.out
done

and in post-build actions add a "Archive the artifacts", file : bigtarget.out


For every build on the same slave, the archived file will increase by 200 Mb.
Effects :

  • the slave will disconnect
  • the master will not be able to reconnect to the slave UNLESS you choose "configure" on the node, click "save" and then relaunch the slave connection
  • the master will not stop in a normal fasion, only kill -9 will do the trick
  • the slave.jar will keep running on the client and needs to be killed too ( otherwise multiple will keep running )
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators.
For more information on JIRA, see: http://www.atlassian.com/software/jira

--
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to