Adding in ability to check status of automatic branch jobs in jenkins
The current documentation for integrating Jenkins and Gitlab EE indicates that the Gitlab Hook Plugin should be used. When you use that plugin you can set up Jenkins to automatically create new jobs for the branches used in merge requests. The CI Status check for Jenkins does not currently handle those automatic jobs. The result of this is shows an error checking the status on all Merge Requests. This merge request is a small change to the jenkins_service to utilize the ref param being passed in and appending the branch name if not master to the project url which will allow the status checks to succeed.
See merge request !9
Add yellow/unstable build as a failure
Jenkins has more build statuses than any 'CI' tool I've ever seen. Apparently a build can be 'successful' but if tests fail it's called 'unstable'. However, 'unstable' is not considered a failing build. Bleh...
Anyway, GitLab needs to consider unstable or yellow builds a failure for CI purposes.
See merge request !11
add missing space
From
> Restrict commits by author(email) to existing GitLab users
to
> Restrict commits by author (email) to existing GitLab users
See merge request !17
link to configured gravatar host on profile page
This MR updates the profile page to display the correct address for the configured gravatar service. Previously this always showed gravatar.com even if gravatar.com was not being used as the gravatar service.
See merge request !1093
Cache all events
Use CSS to determine if the current user needs to see "Congratulations! Tweet about it" by project creation events and "Create Merge Request" by push events.
Implemented as described here: https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/911#note_1559710
Addresses #2054, in part.
cc @dzaporozhets
See merge request !1103
Show incompatible projects in Bitbucket import status
### What does this MR do?
This MR displays incompatible Bitbucket projects (e.g. SVN, hg) in the status table.
### Why was this MR needed?
Users are confused when they don't see projects show up. The import list should show incompatible projects as we do for Google Code to make it more obvious to the user what is happening. (See !586 and 9c76a6fa).
### Screenshot
### What are the relevant issue numbers?
#1871
See merge request !1114
Improve merge requests
- [x] Fetch merge request refs by IID
- [x] Ability to fetch any merge request
- [x] Link commits and diffs in merge request to target project
- [x] Improve merge request UI and command line instructions
- [x] Check merge request widget loading test coverage double
See merge request !1115
Show who last edited a comment if it wasn't the original author
Fixes#1796.
The `updated_by` user is also tracked for issues and merge requests, but it isn't currently shown, because "edited by Person" would give the idea that Person edited the description, while most updates to those are assignee/milestone/labels, in which case who made that change is already visible in the comments.
See merge request !1075
Now when changes in merge requests stored in target project we can
always link commits and diffs to target project. So even people without
access to fork can browse commits and diffs
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
Apply markdown filter for project descriptions on explore view
When you open the explore page, then the project descriptions are not rendered correctly (e.g., https://gitlab.com/search?search=tortoisegit).
See merge request !1098
Dmitriy Zaporozhets
Chris Rohr
Sytse Sijbrandij
Douwe Maan
Stan Hu
Nikita Verkhovin
Stan Hu
Robert Speicher
Robert Speicher
Stefan Tatschner
