If you are running another sidekiq instance on your server, e.g. GitLab
CI, the check script would parse the output of `ps aux` searching for
`sidekiq` and returning success, although the GitLab sidekiq may not be
running.

Now the `ps` call will only print the processes run by the GitLab user.

* GitLab Shell 1.7.1 is required
* Global projects are not supported (refs #5152)

You should update to 6.0 before proceed with update to higher version.
So its no reason to keep old tasks any more.
It should be still available in 6-0-stable but not in master

* call set_iid before validation
* make rake task pass event if objects are invalid
* show iid in comment event at dashboard

Store diff with line note. It makes possible to see inline notes with proper diff even if MR diff changed

Use gitlab-shell authorized_keys truncation. Fix issue with authorized_keys stored in different location

When the file that pointed git bin_path in gitlab.yml dose'nt exist,
bundle rake gitlab:app:check would be aborted.

refs #4205

Signed-off-by: Axilleas Pipinellis <axilleas@archlinux.gr>

These fixes will allow a restore of gitlab when the backups and
repositories directories are in non-standard locations (ie sub-dirs
of gitlabhq).  Also allows the restore to be run from script
overriding the need of a user to confirm the rebuild of the
authorized_keys file.

Expand the import glob to include `**/*.git` to find projects in groups
as well as top level projects.  Check for existing group, and create
group if needed.  Set namespace_id for imported projects.

e.g.: the sidekiq in my Debian box is v2.11.1

Since version 4.1, notes.line_code means:
  {SHA1 hash of file path}_{old line}_{new line}
but the older version means:
  {file index of the commit}_{old line}_{new line}

This rake task migrate the above differences.