c810234357
Ci Project migrate - This doesn't migrate: allow_git_fetch, coverage_regex, timeout. Since this are project configuration settings I would propose to migrate them to `.gitlab-ci.yml`. - This requires offline migrations. - It simplifies database models making all CI objects to be attached to: Project. - It removes Ci::Project, but makes /ci/projects working by adding method: Project.find_by_ci_id for backward compatibility (badges, triggers). - We should add default `timeout` to Application Settings. - It misses specs. - It is based on ci-services-migrate for now. - It removes CI events. - It removes administrator CI projects overview. - It removes CI application settings. In 8.4 or 8.5 we can remove redundant tables and columns. See merge request !1987
23 lines
1.1 KiB
Text
23 lines
1.1 KiB
Text
%h3 Shared runners
|
|
|
|
.bs-callout.bs-callout-warning
|
|
GitLab Runners do not offer secure isolation between projects that they do builds for. You are TRUSTING all GitLab users who can push code to project A, B or C to run shell scripts on the machine hosting runner X.
|
|
%hr
|
|
- if @project.shared_runners_enabled?
|
|
= link_to toggle_shared_runners_namespace_project_runners_path(@project.namespace, @project), class: 'btn btn-warning', method: :post do
|
|
Disable shared runners
|
|
- else
|
|
= link_to toggle_shared_runners_namespace_project_runners_path(@project.namespace, @project), class: 'btn btn-success', method: :post do
|
|
Enable shared runners
|
|
for this project
|
|
|
|
- if @shared_runners_count.zero?
|
|
This GitLab server does not provide any shared runners yet.
|
|
Please use specific runners or ask the administrator to create one.
|
|
- else
|
|
%h4.underlined-title Available shared runners - #{@shared_runners_count}
|
|
%ul.bordered-list.available-shared-runners
|
|
= render partial: 'runner', collection: @shared_runners, as: :runner
|
|
- if @shared_runners_count > 10
|
|
.light
|
|
and #{@shared_runners_count - 10} more...
|