Repository navigation
Easier debugging ideas #146
Description
Activity
How the keep-alive could work: A simple solution would be to add sleep to the cleanup script:
$ keep_time=$(echo "${ghprbCommentBody}" | grep -o '\[keep-machine[^]]*\]' | sed -e 's/\[keep-machine:\([^]]*\)\]/\1/') [ -n "${keep_time}" ] && echo "Keeping the machine $IP alive for ${keep_time}" && sleep "${keep_time}"Of course this can be enhanced by sending a github comment, tagging the person who added that comment etc...
Do you want to keep the VM allocated by resalloc alive, or the jenkins
machine? If the former, new resalloc feature will be shipped in v3.0;
you could put the machine into sandbox by--sandbox... and anyone
(perhaps person doing the debugging) could re-take the machine with
the same--sandboxoption (within pre-configured time-limit).This would be really awesome. I am a volunteer for testing. :)
Brain dump of some ideas how to make the debugging easier:
[keep-alive: 2h]in the github comment could make the machine be kept a little longer after the test is done (see https://plugins.jenkins.io/ghprb/ for how to work with the comments)[debug]could turn on the debug (more verbose) output for the tests