delta/gitlab/gitlab-ce.git, branch process-commit-worker-large-batches

Schedule at most 100 commits

2016-12-23T13:05:00+00:00

When processing push payloads we now schedule at most the 100 most
recent commits, instead of all commits that were in a payload. This
prevents one from overloading the system by pushing thousands if not
millions of commits in a single go.

Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/25827

Merge branch 'fix-latest-pipeine-ordering' into 'master'

2016-12-23T12:28:54+00:00


Fix code that selects latest pipelines

Closes #25993 and #26031

See merge request !8286

Update the description because it's more broader

2016-12-23T10:49:56+00:00

Feedback:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/8286/diffs#note_20435082

Merge branch 'zj-mattermost-config-username' into 'master'

2016-12-23T10:49:31+00:00


Post username as property, not user_name

See merge request !8261

Update description stating that ordering is important

2016-12-23T10:30:25+00:00

Feedback from Grzegorz

Prefer oneline and Rubocop prefers ternary operator

2016-12-23T10:17:25+00:00

Feedback:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/8286/diffs#note_20433402

Merge branch 'fixes-issues-api-reopen' into 'master'

2016-12-23T09:12:40+00:00


Fix state_event parameter to reopen an issue

Closes #25958

See merge request !8246

Ci::Pipeline.latest order by id DESC

2016-12-23T09:03:01+00:00

The name latest implies that it's reverse chronological,
and we did expect it that way.

https://gitlab.com/gitlab-org/gitlab-ce/issues/25993#note_20429761

>>>
ok, I think markglenfletchera is correct in
https://gitlab.com/gitlab-com/support-forum/issues/1394#note_20399939
that `Project#latest_successful_builds_for` is giving oldest pipeline
rather than latest pipeline. This is a ~regression introduced by !7333
where `order(id: :desc)` was removed causing this. The offending change
was:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/7333/diffs#b22732e5f39e176c7c719fe485847d0fb0564275_92_108

The confusion was caused by the `latest` name implication, which
actually didn't order anything, and I think we should add `order(id:
:desc)` to `Ci::Pipeline.latest` otherwise it's confusing that it's not
actually ordered.
>>>

Closes #25993

Merge branch 'docs/add_imgs_to_mr_resolution_issue' into 'master'

2016-12-22T22:02:25+00:00


Add more images to issue creation from unresolved discussions

See merge request !8279

Merge branch 'patch-9' into 'master'

2016-12-22T21:58:42+00:00


Fixed typo in test-and-deploy-ruby-application-to-heroku.md

See merge request !8236