gitlab-runner merge requestshttps://staging.gitlab.com/gitlab-org/gitlab-runner/-/merge_requests2016-12-21T11:20:16Zhttps://staging.gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/275Push runner-helper image to Dockerhub during deploy stage2016-12-21T11:20:16Zusername-removed-182855Push runner-helper image to Dockerhub during deploy stageThis MR adds support for pushing both arm and x86_64 images for the runner-helper to Dockerhub. This was created to open discussion on how to deal with runner-helper when running on remote machines (aka on a Kubernetes cluster, where `do...This MR adds support for pushing both arm and x86_64 images for the runner-helper to Dockerhub. This was created to open discussion on how to deal with runner-helper when running on remote machines (aka on a Kubernetes cluster, where `docker import` is not available).
It pushes an arm and x86_64 image with the commit hash of the runner at that point in time in order to facilitate the runner versioning the helper image.
As a result of this MR, docker becomes required during the deploy stage. This is so that any version of the runner is able to use it's own build hash to pull a versioned copy of the runner-helper image. The build stage still does not enforce the use of Docker.v1.9username-removed-182855username-removed-182855https://staging.gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/432[WIP] Tempoprary add 'force' option to NetworkConnectionOptions2017-03-06T23:56:49ZTomasz Maczukintomasz@gitlab.com[WIP] Tempoprary add 'force' option to NetworkConnectionOptions## What does this MR do?
Adds a `Force` option to `NetworkConnectionOptions` struct to force stale containers disconnection from networks (which extends the code added in !390.
This is the temporary fix to test if such workflow wil...## What does this MR do?
Adds a `Force` option to `NetworkConnectionOptions` struct to force stale containers disconnection from networks (which extends the code added in !390.
This is the temporary fix to test if such workflow will resolve problems described in #1642. It should be fixed properly with switching to `github.com/docker/docker/client` (!301 - waiting for Docker 1.13 to be released).
## Why was this MR needed?
Please read #1642 for a reference.
## Are there points in the code the reviewer needs to double check?
## Does this MR meet the acceptance criteria?
- [ ] Documentation created/updated
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
- [ ] Branch has no merge conflicts with `master` (if you do - rebase it please)
## What are the relevant issue numbers?
Related to #1642v9.0Tomasz Maczukintomasz@gitlab.comTomasz Maczukintomasz@gitlab.comhttps://staging.gitlab.com/gitlab-org/gitlab-runner/-/merge_requests/469Added --cpus option support.2017-05-25T13:33:42Zusername-removed-15146Added --cpus option support.## What does this MR do?
Adds CPUS option for docker runner.
## Why was this MR needed?
Adds support for the --cpus option available in Docker 1.13. This allows limit number of CPUs available to each docker container.
## Are ...## What does this MR do?
Adds CPUS option for docker runner.
## Why was this MR needed?
Adds support for the --cpus option available in Docker 1.13. This allows limit number of CPUs available to each docker container.
## Are there points in the code the reviewer needs to double check?
## Does this MR meet the acceptance criteria?
- [x] Documentation created/updated
- Tests
- [ ] Added for this feature/bug
- [ ] All builds are passing
- [ ] Branch has no merge conflicts with `master` (if you do - rebase it please)
## What are the relevant issue numbers?
* #2101 -- Support Docker 1.13 --cpus option9.3