delta/gitlab/gitlab-ce.git/app/controllers/projects/runner_projects_controller.rb, branch docs/database-development

Add a rubocop rule to check if a method 'redirect_to' is used without explicitly set 'status' in 'destroy' actions of controllers

2017-06-06T22:45:16+00:00

Use Ability to check pre-requisite. Change back to 403 because:

2016-06-29T11:04:06+00:00

If we're using `can?` it would look weird to use 409

Use 409 to indicate that interface might be outdated

2016-06-28T11:54:18+00:00

Because invalid actions shouldn't be shown on the page.

Fix typo. It's ivar and the column was called locked

2016-06-15T09:29:07+00:00

Return the association and check it in controller instead:

2016-06-14T15:11:43+00:00

Feedback:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/4641#note_12444891

Avoid enabling locked runners. Give 403 in this case

2016-06-14T14:58:38+00:00

Make the CI permission model simpler

2016-02-02T08:18:08+00:00

This MR simplifies CI permission model:
- read_build: allows to read a list of builds, artifacts and trace
- update_build: allows to cancel and retry builds
- create_build: allows to create builds from gitlab-ci.yml (not yet implemented)
- admin_build: allows to manage triggers, runners and variables
- read_commit_status: allows to read a list of commit statuses (including the overall of builds)
- create_commit_status: allows to create a new commit status using API

Remove all extra methods to manage permission.
Made all controllers to use explicitly the new permissions.

Remove ci_ prefix from all ci related things

2015-12-11T17:02:09+00:00

Migrate CI::Project to Project

2015-12-11T17:02:09+00:00