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
Include more information in hook error messages
When pushing commits to the remote, if a pre-receive hook gets triggered that prevents the push, it may not be clear which commit is causing the issue. Having the values of what caused the comparison to fail in the error message will help debugging, whether it be the user or the administrator.
See merge request !14
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
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
Fix redirection after sign in when using auto_sign_in_with_provider
Logic for redirect path moved to a filter. This allows it to run properly when the auto_sign_in_with_provider filter takes control.
See merge request !1146
Workaround the insecure password warnings emitted by MySQL 5.6
When using MySQL 5.6, the following output is emitted every time a backup is created, even with CRON=1.
```
Warning: Using a password on the command line interface can be insecure.
```
This fix works around that by sending the password via the [`MYSQL_PWD`](http://dev.mysql.com/doc/refman/5.6/en/environment-variables.html) environment variable.
See merge request !1139
Disable internal issue tracker if external tracker in use
### What does this MR do?
This MR disables routes to the internal issue tracker if an external issue tracker (e.g. Redmine) is in use. A 404 page is returned if a user attempts to access any of the issue routes.
### Why was this MR needed?
Enabling the external issue tracker would still keep the internal one active, which would lead to odd behavior where users could create issues but not close them.
### What are the relevant issue numbers?
Closes#2006
See merge request !993
Provide more feedback what went wrong if HipChat service failed test
This MR adds support for displaying the error message during HipChat service test. Before an Error 500 would be displayed with no helpful remarks.
Screenshot:
Issue gitlab-com/support-forum#213
See merge request !1144
Dmitriy Zaporozhets
Sytse Sijbrandij
Douwe Maan
Darby
Dmitriy Zaporozhets
Robert Speicher
Robert Speicher
Robert Schilling
Sven Strickroth
Chris Rohr
Stan Hu
Boyan Tabakov
Valery Sizov
ranjith
Job van der Voort
Robert Schilling
Andrea Ruggiero
