gitlab-org--gitlab-foss/doc/development/README.md

# Development

## Outside of docs

- [CONTRIBUTING.md](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md) main contributing guide
- [PROCESS.md](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/PROCESS.md) contributing process
- [GitLab Development Kit (GDK)](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/doc/howto/README.md) to install a development version

## Styleguides

- [API styleguide](api_styleguide.md) Use this styleguide if you are
  contributing to the API.
- [Documentation styleguide](doc_styleguide.md) Use this styleguide if you are
  contributing to documentation.
- [SQL Migration Style Guide](migration_style_guide.md) for creating safe SQL migrations
- [Testing standards and style guidelines](testing.md)
- [UI guide](ui_guide.md) for building GitLab with existing CSS styles and elements
- [Frontend guidelines](frontend.md)
- [SQL guidelines](sql.md) for working with SQL queries
- [Sidekiq guidelines](sidekiq_style_guide.md) for working with Sidekiq workers

## Process

- [Code review guidelines](code_review.md) for reviewing code and having code reviewed.
- [Merge request performance guidelines](merge_request_performance_guidelines.md)
  for ensuring merge requests do not negatively impact GitLab performance

## Backend howtos

- [Architecture](architecture.md) of GitLab
- [CI setup](ci_setup.md) for testing GitLab
- [Gotchas](gotchas.md) to avoid
- [How to dump production data to staging](db_dump.md)
- [Instrumentation](instrumentation.md)
- [Performance guidelines](performance.md)
- [Rake tasks](rake_tasks.md) for development
- [Shell commands](shell_commands.md) in the GitLab codebase
- [Sidekiq debugging](sidekiq_debugging.md)

## Databases

- [What requires downtime?](what_requires_downtime.md)
- [Adding database indexes](adding_database_indexes.md)

## Compliance

- [Licensing](licensing.md) for ensuring license compliance
create migration style guide. Fixes #2305 2015-05-11 09:09:36 -04:00			`# Development`
Add doc file for dev rake tasks 2014-04-24 13:53:18 -04:00
Structure the development documentation 2016-08-04 06:45:59 -04:00			`## Outside of docs`

			`- [CONTRIBUTING.md](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md) main contributing guide`
			`- [PROCESS.md](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/PROCESS.md) contributing process`
Link to doc root, not readme of GDK 2016-08-08 11:14:36 -04:00			`- [GitLab Development Kit (GDK)](https://gitlab.com/gitlab-org/gitlab-development-kit/blob/master/doc/howto/README.md) to install a development version`
Structure the development documentation 2016-08-04 06:45:59 -04:00
			`## Styleguides`

Add an API styleguide Signed-off-by: Rémy Coutable <remy@rymai.me> 2016-10-13 12:44:52 -04:00			`- [API styleguide](api_styleguide.md) Use this styleguide if you are`
			`contributing to the API.`
Small refactor of doc/development/README.md - Fix wrong doc_styleguide URL - Clarify migrations refer to SQL - Capitalize CSS 2016-08-10 07:28:56 -04:00			`- [Documentation styleguide](doc_styleguide.md) Use this styleguide if you are`
Structure the development documentation 2016-08-04 06:45:59 -04:00			`contributing to documentation.`
Small refactor of doc/development/README.md - Fix wrong doc_styleguide URL - Clarify migrations refer to SQL - Capitalize CSS 2016-08-10 07:28:56 -04:00			`- [SQL Migration Style Guide](migration_style_guide.md) for creating safe SQL migrations`
Structure the development documentation 2016-08-04 06:45:59 -04:00			`- [Testing standards and style guidelines](testing.md)`
Small refactor of doc/development/README.md - Fix wrong doc_styleguide URL - Clarify migrations refer to SQL - Capitalize CSS 2016-08-10 07:28:56 -04:00			`- [UI guide](ui_guide.md) for building GitLab with existing CSS styles and elements`
Initial incomplete draft of the Frontend Development Guidelines. [ci skip] 2016-07-11 14:48:00 -04:00			`- [Frontend guidelines](frontend.md)`
Re-organize queues to use for Sidekiq Dumping too many jobs in the same queue (e.g. the "default" queue) is a dangerous setup. Jobs that take a long time to process can effectively block any other work from being performed given there are enough of these jobs. Furthermore it becomes harder to monitor the jobs as a single queue could contain jobs for different workers. In such a setup the only reliable way of getting counts per job is to iterate over all jobs in a queue, which is a rather time consuming process. By using separate queues for various workers we have better control over throughput, we can add weight to queues, and we can monitor queues better. Some workers still use the same queue whenever their work is related. For example, the various CI pipeline workers use the same "pipeline" queue. This commit includes a Rails migration that moves Sidekiq jobs from the old queues to the new ones. This migration also takes care of doing the inverse if ever needed. This does require downtime as otherwise new jobs could be scheduled in the old queues after this migration completes. This commit also includes an RSpec test that blacklists the use of the "default" queue and ensures cron workers use the "cronjob" queue. Fixes gitlab-org/gitlab-ce#23370 2016-10-21 12:13:41 -04:00			`- [SQL guidelines](sql.md) for working with SQL queries`
			`- [Sidekiq guidelines](sidekiq_style_guide.md) for working with Sidekiq workers`
Structure the development documentation 2016-08-04 06:45:59 -04:00
			`## Process`

			`- [Code review guidelines](code_review.md) for reviewing code and having code reviewed.`
Added performance guidelines for new MRs These guidelines cover the performance requirement for newly submitted merge requests. These guidelines are put in to place to prevent merge requests from negatively impacting GitLab performance as much as possible. 2016-08-19 11:21:00 -04:00			`- [Merge request performance guidelines](merge_request_performance_guidelines.md)`
			`for ensuring merge requests do not negatively impact GitLab performance`
Structure the development documentation 2016-08-04 06:45:59 -04:00
			`## Backend howtos`

Update docs to markdown style guide. 2014-04-24 18:48:22 -04:00			`- [Architecture](architecture.md) of GitLab`
CI setup docs Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> 2014-09-18 09:45:18 -04:00			`- [CI setup](ci_setup.md) for testing GitLab`
Add "Gotchas" development doc 2016-02-16 22:09:00 -05:00			`- [Gotchas](gotchas.md) to avoid`
Fix the "How to dump production data" link [ci skip] 2016-02-16 21:31:14 -05:00			`- [How to dump production data to staging](db_dump.md)`
Added dev guide for measuring Ruby blocks 2016-04-05 06:37:41 -04:00			`- [Instrumentation](instrumentation.md)`
Added performance guidelines Fixes gitlab-org/gitlab-ce#15254 gitlab-org/gitlab-ce#14277 [ci skip] 2016-04-28 15:44:21 -04:00			`- [Performance guidelines](performance.md)`
Alphabetize Development doc index [ci skip] 2016-02-16 21:29:54 -05:00			`- [Rake tasks](rake_tasks.md) for development`
			`- [Shell commands](shell_commands.md) in the GitLab codebase`
Disable Sidekiq arguments logging by default 2014-12-01 12:58:37 -05:00			`- [Sidekiq debugging](sidekiq_debugging.md)`
Added documentation on adding database indexes 2016-08-11 08:22:21 -04:00
			`## Databases`

Added guide about migrations and downtime This guide describes various commonly used operations and the impact they have on the availability of a GitLab instance. 2016-08-04 11:17:31 -04:00			`- [What requires downtime?](what_requires_downtime.md)`
Added documentation on adding database indexes 2016-08-11 08:22:21 -04:00			`- [Adding database indexes](adding_database_indexes.md)`
Structure the development documentation 2016-08-04 06:45:59 -04:00
			`## Compliance`

			`- [Licensing](licensing.md) for ensuring license compliance`