4 ms·

We're working hard on making CI super easy to use and setup. If you want to give it a spin, check out our recent blog post on starting from 0: https://about.gi

We're working hard on making CI super easy to use and setup. If you want to give it a spin, check out our recent blog post on starting from 0: https://about.gitlab.com/2016/07/29/the-basics-of-gitlab-ci/ https://about.gitlab.com/2016/07/29/the-basics-of-gitlab-ci/

scrollaway 10y ago
I was trying to look into Gitlab Runner the other day. How decoupled is it from Gitlab itself? Would I be able to somewhat easily write a completely different UI, with a different framework/language (say, Django), hook it all up to Github/Gogs and use Gitlab runner for the jobs themselves? Because if that's what it is, that is pretty kickass.
- jobvandervoort 10y ago
  AFAIK you would not be able to do that. I've asked the author of Runner to comment here.
- sytse 10y ago
  The Runner interfaces with GitLab through a pretty simple API, so you could do that. One caveat is that we might introduce a new API by releasing a new version of GitLab and GitLab Runner at the same time, then you would need to upgrade you project to stay compatible. BTW To ensure nobody is confused, you can use GitLab Runner to test all kinds of projects on all kinds of hardware. We're discussing developing an alternative to GitLab but reusing GitLab Runner.
bisby 10y ago
Im using Jenkins right now to basically handle docker deployments. Without taking the time to actually read up on it in depth, does GitLab CI handle ways for me to essentially just pull prebuilt images and run them on a targeted server with desired settings? I'm already preparing to move to GitLab CI for images that I build myself (since Im already storing the Dockerfiles on gitlab)
- Snappy 10y ago
  Yes, using prebuilt images is easy. Basically, just add `image: ruby:2.3.1-alpine` to a job, for example. Docs: http://docs.gitlab.com/ce/ci/docker/using_docker_images.html#define-image-and-services-from-.gitlab-ci.yml http://docs.gitlab.com/ce/ci/docker/using_docker_images.html...
  - bisby 10y ago
    That seems to be referring to using docker images as part of the build process. Im referring to using docker images as the deliverable. I mostly want to just have a gui to do "docker pull x" "docker stop xcon && docker rm xcon" "docker run --name xcon -v /volumes/x/config:/var/www/config -p 8080:80 x" for me. There would technically be nothing to be stored in the gitlab repo here, except the config. Replace the "docker pull x" step with docker build in the event that I'm using a dockerfile to build a custom image, which could trigger as a result of updating the dockerfile... but usually the dockerfile doesnt change, it just needs to be re-run to pull in upstream changes.
    - Snappy 10y ago
      Thanks for clarifying. I'm pretty sure you can do everything you want here. You could install a runner on your production box and run those commands within a deploy job. Two options for configuring the runner: 1: http://docs.gitlab.com/ce/ci/docker/using_docker_build.html#use-shell-executor http://docs.gitlab.com/ce/ci/docker/using_docker_build.html#... 2: http://docs.gitlab.com/ce/ci/docker/using_docker_build.html#use-docker-socket-binding http://docs.gitlab.com/ce/ci/docker/using_docker_build.html#...
      - bisby 10y ago
        Thanks, this looks like it describes my use case exactly. I'll have to read into this more!

scrollaway 10y ago

I was trying to look into Gitlab Runner the other day. How decoupled is it from Gitlab itself? Would I be able to somewhat easily write a completely different UI, with a different framework/language (say, Django), hook it all up to Github/Gogs and use Gitlab runner for the jobs themselves? Because if that's what it is, that is pretty kickass.

jobvandervoort 10y ago
AFAIK you would not be able to do that. I've asked the author of Runner to comment here.
sytse 10y ago
The Runner interfaces with GitLab through a pretty simple API, so you could do that. One caveat is that we might introduce a new API by releasing a new version of GitLab and GitLab Runner at the same time, then you would need to upgrade you project to stay compatible. BTW To ensure nobody is confused, you can use GitLab Runner to test all kinds of projects on all kinds of hardware. We're discussing developing an alternative to GitLab but reusing GitLab Runner.

bisby 10y ago

Im using Jenkins right now to basically handle docker deployments. Without taking the time to actually read up on it in depth, does GitLab CI handle ways for me to essentially just pull prebuilt images and run them on a targeted server with desired settings? I'm already preparing to move to GitLab CI for images that I build myself (since Im already storing the Dockerfiles on gitlab)

Snappy 10y ago
Yes, using prebuilt images is easy. Basically, just add `image: ruby:2.3.1-alpine` to a job, for example. Docs: http://docs.gitlab.com/ce/ci/docker/using_docker_images.html#define-image-and-services-from-.gitlab-ci.yml http://docs.gitlab.com/ce/ci/docker/using_docker_images.html...
- bisby 10y ago
  That seems to be referring to using docker images as part of the build process. Im referring to using docker images as the deliverable. I mostly want to just have a gui to do "docker pull x" "docker stop xcon && docker rm xcon" "docker run --name xcon -v /volumes/x/config:/var/www/config -p 8080:80 x" for me. There would technically be nothing to be stored in the gitlab repo here, except the config. Replace the "docker pull x" step with docker build in the event that I'm using a dockerfile to build a custom image, which could trigger as a result of updating the dockerfile... but usually the dockerfile doesnt change, it just needs to be re-run to pull in upstream changes.
  - Snappy 10y ago
    Thanks for clarifying. I'm pretty sure you can do everything you want here. You could install a runner on your production box and run those commands within a deploy job. Two options for configuring the runner: 1: http://docs.gitlab.com/ce/ci/docker/using_docker_build.html#use-shell-executor http://docs.gitlab.com/ce/ci/docker/using_docker_build.html#... 2: http://docs.gitlab.com/ce/ci/docker/using_docker_build.html#use-docker-socket-binding http://docs.gitlab.com/ce/ci/docker/using_docker_build.html#...
    - bisby 10y ago
      Thanks, this looks like it describes my use case exactly. I'll have to read into this more!