The whole point of omnibus I thought was a seamless upgrade via apt-get. In my case the CI was on the same server as the gitlab server... the migration guide seems to outline steps for migrating data from a separate server.
The upgrade process did not convert the build scripts to yml files, and the build and CI menus were not visible. To resolve this I ended up doing the following: - disable the gitlab-ci service in the project settings and click save. - enable the gitlab-ci service in the project settings and click save.... the build and CI menu options are available after this is donoe. - create a yml file and check into the root of the project's git source Relating to the runner - install latest runner on runner instance via apt-get process - configure it with token created on gitlab - change the permissions of the builds folder in the new gitlab-runner installation folder tree so that builds would not fail on permissions On Wednesday, November 18, 2015 at 7:44:36 AM UTC-6, Matt V wrote: > > After performing an omnibus apt-get upgrade of a Gitlab CE install, the CI > integration stopped working. There is no gitlab runner instance > registered and none of the previous build scripts are present in the > projects. > > Where can I find the original build scripts and re-register an existing > CI-runner instance? > > Thanks, > Matt > > > > -- 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/56b09a33-ab9e-4fd1-be99-b8c79daf52a5%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
