kotovalexarian-likes-gitlab
/
gitlab-org--gitlab-foss
1
0
Fork 0
Code Releases Activity
gitlab-org--gitlab-foss/app/views/projects/runners/index.html.haml

27 lines
726 B
Plaintext
Raw Normal View History

CI details cleanup - Add page titles to CI settings. - Fix CI admin navigation. - Remove duplicated scope. - Use monospace font for commit sha. - Add page title and header title to build page. - Proper authorization for cancel/retry builds. - Use gitlab pagination theme for builds and group members. - Don't paginate builds widget on build page. - Add badges to commit page Changes/Builds tabs. - Add "Builds" to commit Builds tab page title. - Add and use Ci::Build#retryable? method. - Add CI::Build#retried? method. - Allow all failed commit builds to be retried. - Proper authorization for cancel/retry all builds. - Remove unused param. - Use time_ago_with_tooltip where appropriate. - Tweak builds index text - Remove duplication between builds/build and commit_statuses/commit_status. - Use POST rather than GET for canceling and retrying builds. - Remove redundant URL helpers. - Add build ID to build page. - Link branch name on build page. - Move commit/:sha/ci to commit/:sha/builds.
2015-11-03 10:44:07 +00:00
- page_title "Runners"
Groundwork for merging CI into CE
2015-08-26 01:42:46 +00:00
.light
%p
A 'runner' is a process which runs a build.
You can setup as many runners as you need.
%br
Runners can be placed on separate users, servers, and even on your local machine.
%p Each runner can be in one of the following states:
%div
%ul
%li
%span.label.label-success active
\- runner is active and can process any new build
%li
%span.label.label-danger paused
\- runner is paused and will not receive any new build
%hr
%p.lead To start serving your builds you can either add specific runners to your project or use shared runners
.row
.col-sm-6
= render 'specific_runners'
.col-sm-6
= render 'shared_runners'