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
Make the `provider` argument for the LDAP group links API endpoint required
Related to #329
If no `provider` is passed to the API endpoint, the group link is not created properly. Making it required fixes the issue temporarily. It should default to the first provider.
Next step, as mentioned in #329, is to do that.
/cc @job
See merge request !475
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
Always add current user to autocomplete controller to support filter by "Me"
### What does this MR do?
This MR always adds the current user to the autocomplete list of users.
### Why was this MR needed?
Normally only the members from a team or the group are shown in the autocomplete list. However, this prevents a user from filtering issues belong to him/her if the user does not belong directly to either. To make this filtering more usable, we can be sure to add the current user to the list, which the JavaScript code will move to the top of the list.
### What are the relevant issue numbers?
Partial fix#2202
See merge request !1100
Only publish ssh key-type and key
Now when requesting my keys; my emailadres is exposed. [My keys](https://gitlab.com/zj.keys)
To prevent harvesting only key-type and the key itself are displayed instead of all data supplied when uploaded.
See merge request !850
HTML span elements only apply to a single line, and in the case of multi-line
comments, the highlighting was dropped as a result. Ensure that each line has
the proper styling to fix this.
Closes#1577
Prepare Markdown feature spec for testing multiple pipelines
This MR lays the groundwork for including or excluding certain HTML::Pipeline
filters depending on what we're parsing. For example, excluding reference
filters in the Issues and Merge Requests titles.
See merge request !1053
Add gitlab-shell to error message to give user a clue that something may be wrong there.
Ran into this in #2082. User was told that repositories were created when they were
not due to hooks symlink being wrong.
Dmitriy Zaporozhets
Douwe Maan
Chris Rohr
Patricio Cano
Robert Speicher
Robert Speicher
Stan Hu
Sytse Sijbrandij
Valery Sizov
Zeger-Jan van de Weg
Atsushi Ishida
