FYI we just added an API and code to the runner to let it deregister itself. I think it will release this month on the 22nd.
Best regards, Sytse Sijbrandij CEO GitLab B.V. On Wed, Mar 11, 2015 at 3:06 AM, paul <gcha...@gmail.com> wrote: > Yes, this is a good idea. Easier than cloning as in my 1. possibility. > > [What I do not yet know with this variant (or my 1. poss.), how I would > isolate the tests. A subsequent test should not be able to access any > remains of a previous test. To destroy and recreate the container (and also > re-register the runner) after each test seems to be a hassle. Maybe my 2. > possibility would provide better isolation. But I'll ask again if necessary, > this is another subject.] > > Thanks for your comment! > > > On Tuesday, 10 March 2015 23:16:21 UTC+1, sytse wrote: >> >> Can you take your docker image and add any runner from >> https://about.gitlab.com/gitlab-ci/#gitlab-runner to it and save that >> as a new image? >> >> > -- > 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/6c44c8dc-8804-4117-a03c-f2a76e3ec87a%40googlegroups.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/CAJTzhG-kxVRtgb62p%2BKQ8xKmfw-kgSaHKvXfk_dqproU%2Bm9M6g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
