Documents that users with two-factor authentication enabled may also need to create a personal access token to use git over HTTPS.
To address a support issue (gitlab-com/support-forum#980) about why passwords don't work in git when two-factor auth is enabled.
gitlab-com/support-forum#980
See merge request !6616
Add all endoints to JIRA service API documentation
## What does this MR do?
Add missing API endpoints to the JIRA service.
## What are the relevant issue numbers?
https://gitlab.com/gitlab-org/gitlab-ee/issues/440
See merge request !7122
users should remove former Go installation folder
## What does this MR do?
It ensure users installing or updating from source will remove their former Go installation folder in `/usr/local/go`, to avoid raising errors that could lead to new issues being created.
## Are there points in the code the reviewer needs to double check?
1. The `rm -rf` should not be verbose if folder does not exists.
1. May a user have some kind of configuration files in this folder ?
## Why was this MR needed?
I did faced the error, that led me to the solution stated here : https://gitlab.com/gitlab-org/gitlab-workhorse/issues/29#note_4155517
gitlab-org/gitlab-workhorse#29
See merge request !6602
This will change the update process to checkout gitlab-shell version 3.6.6 instead of 3.6.3 as currently described in the update document
See merge request !6976
Fix docker.sock reference in config.toml
## What does this MR do?
`config.toml` sample did not correctly represent the `/var/run/docker.sock` mapping, causing it to be created as a volume instead.
## Why was this MR needed?
It was broken.
See merge request !5172
Refactor and add new environment functionality to CI yaml reference
## What does this MR do?
Add new `environment` functionality to the yaml reference.
## What are the relevant issue numbers?
Part of https://gitlab.com/gitlab-org/gitlab-ce/issues/23484
See merge request !7026
Fix wrong example in api/users documentation
## What does this MR do?
Just a small typo fix in API docs. While greping for this typo I also found couple more places with same mistake and included them in the MR too.
See merge request !7043
Changed gitlab-shell version to avoid warning when precompiling the assets.
## What does this MR do?
Changes installation instructions from source to install v3.6.1 of gitlab-shell to avoid a pre-compile warning on gitlab.
See merge request !6747
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.
Fixesgitlab-org/gitlab-ce#23370
Update Documentation image when configuring Build emails in Services
## What does this MR do?
Replace old GitLab image in documentation with a new image showing the new position of Services and the module 'Build emails'
## Why was this MR needed?
GitLab's layout changed with version 8.9 and the buttons were moved.
See merge request !5139
[Doc] Fix `ref` parameter name for `commits/statuses`
The attribute to filter by branch or tag needs to be named `ref`, not `ref_name`. And indeed the attribute in the JSON response is `ref` (and not `ref_name`).
Tested on Gitlab CE 8.9.
See merge request !4876