Thanks for your quick reply! The reboot is indeed successful. And I thought about setting a delay as well. But I'm afraid this can cause trouble when there is a pending test the runner might pick up.
On Wed, 29 Oct 2014 12:52 David Bezuidenhout <a...@hero.za.net> wrote: > Just to confirm, the reboot is always successful, but the sending of > the results is hit and miss? > > If that is the case, tell the reboot to wait a minute before actually > rebooting, eg. in the script: > sudo shutdown -r 60 > > Don't think you need the & at the end, but perhaps that is something > you can test. > > > On Wed, Oct 29, 2014 at 1:43 PM, Erik <etimm...@gmail.com> wrote: > > Hi, > > > > Maybe I'm just looking to hard, but I can't find the right information > > for the set-up I desire. > > > > I have successfully installed GitLab and GitLab CI on a server within > > my LAN. I have also successfully installed a GitLab CI runner on a > > virtual machine (VM, VirtualBox) on another server within my LAN. > > > > The thing is, I would like to have my VM start 'clean' for every test > > the runner runs. Using an immutable disk[1] I have managed to make my > > VM boot into the same state each time it is (re)started. > > > > Is there any (simple) way to make my runners reboot after running a > > test? I have tried adding something like `sudo shutdown -r now &` to > > the test script, but this only seems to work occasionally (it makes > > sense the runner has no or little time to send its testing results). > > > > Any thoughts on this? > > > > Many thanks in advance. > > > > Regards, > > Erik > > > > [1] > > http://www.virtuatopia.com/index.php/Understanding_and_ > Configuring_VirtualBox_Virtual_Hard_Disks#Normal.2C_ > Immutable_and_Write-Through_Disk_Images > > > > -- > > You received this message because you are subscribed to the Google Groups > > "GitLab" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to gitlabhq+unsubscr...@googlegroups.com. > > To view this discussion on the web visit > > https://groups.google.com/d/msgid/gitlabhq/808631af-11d4- > 4e1a-a624-0e6be788adb0%40googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to a topic in the > Google Groups "GitLab" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/gitlabhq/MnLPqjCGdrw/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > gitlabhq+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/gitlabhq/CABGih0nEmgP1t4XU_YezpaLei1TJ8p%3DX6NEDEX% > 2BjqxD-7MssEA%40mail.gmail.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "GitLab" group. To unsubscribe from this group and stop receiving emails from it, send an email to gitlabhq+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/gitlabhq/CA%2B24CoT6Y%3DspN%3D%2BvZxgMqcxCohGvcou3bvj4x%3DX5F-K_ErSjSg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
