delta/gitlab/gitlab-shell.git, branch use-stdin

Pipe RPUSH command to Redis via stdin to avoid overrunning command-line

2016-05-10T21:43:04+00:00

Closes gitlab-org/gitlab-ce#17329

Merge branch 'remove-batch' into 'master'

2016-05-10T09:55:46+00:00


Remove broken badge

The state is shown on the repository anyway

See merge request !39

Set the GL badge

2016-05-10T09:13:35+00:00

Merge branch 'fix-spelling-mistakes' into 'master'

2016-05-09T02:33:28+00:00


Fix spelling mistakes in README.md



See merge request !57

Fix spelling mistakes in README.md

2016-05-05T20:05:43+00:00

Merge branch 'remove-update-head' into 'master'

2016-04-28T16:07:06+00:00


Remove the update-head command since GitLab doesn't use it anymore

It looks like we tend to remove commands that are not used by GitLab anymore (see gitlab-org/gitlab-shell!26) and the `update-head` command will soon be in that case (see https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3705), so I think we should remove it from here too.

Note: I'm setting this as a WIP to ensure this doesn't get merged since the GitLab MR is not merged at that moment.

See merge request !51

Remove the update-head command since GitLab doesn't use it anymore

2016-04-28T15:58:55+00:00

Signed-off-by: Rémy Coutable

Merge branch 'revert-53' into 'master'

2016-04-28T09:33:27+00:00


Revert "Remove unused #list_remote_tags"

This reverts commit f5e87590d463b4b3d1bf5cd6b49a9d0d60acd552 because `#list_remote_tags` is still used by EE:https://gitlab.com/gitlab-org/gitlab-ee/blob/2c364a79ee110a3adf49d6bd30be985ed13c3ec5/lib/gitlab/backend/shell.rb#L45.

/cc @razer6 

See merge request !56

Revert "Remove unused #list_remote_tags"

2016-04-25T15:43:22+00:00

This reverts commit f5e87590d463b4b3d1bf5cd6b49a9d0d60acd552.

Signed-off-by: Rémy Coutable

Merge branch 'aiionx/gitlab-shell-aiionx-post_receive_jid' into 'master'

2016-04-20T04:33:22+00:00


Update post receive worker so it logs a unique JID in sidekiq

Taken from !50.

Instead of

```
2016-04-14T03:07:32.373Z 5285 TID-osycgmlyo PostReceive JID- INFO: start
2016-04-14T03:07:32.374Z 5285 TID-osycgmlyo PostReceive JID- INFO: arguments: [...]
2016-04-14T03:07:32.534Z 5285 TID-osycgmlyo PostReceive JID- INFO: done: 0.161 sec
```

Have this log

```
2016-04-14T03:07:32.373Z 5285 TID-osycgmlyo PostReceive JID-54b0b2f6616cae37e3e87f8a INFO: start
2016-04-14T03:07:32.374Z 5285 TID-osycgmlyo PostReceive JID-54b0b2f6616cae37e3e87f8a INFO: arguments: [...]
2016-04-14T03:07:32.534Z 5285 TID-osycgmlyo PostReceive JID-54b0b2f6616cae37e3e87f8a INFO: done: 0.161 sec
```


This way sidekiq can Log a unique JID in the sidekiq.log for PostReceive.
So when parsing the logs (with logstash for example) you know it belongs to that unique job.

This puts the logs in a uniform manner like the other workers that are pushed to redis (which do have a JID)
For example the ProjectWebHookWorker

```
2016-04-14T03:13:07.917Z 5285 TID-osycsh7z0 ProjectWebHookWorker JID-800085fb3cf7241fdeecc6ec INFO: start
2016-04-14T03:13:07.918Z 5285 TID-osycsh7z0 ProjectWebHookWorker JID-800085fb3cf7241fdeecc6ec INFO: arguments: [...]
2016-04-14T03:13:12.500Z 5285 TID-osycsh7z0 ProjectWebHookWorker JID-800085fb3cf7241fdeecc6ec INFO: done: 4.583 sec
```


See merge request !55