delta/gitlab/gitlab-ce.git/spec/models, branch doc_refactor_namespaces_api

Use a more sensible message for the AbuseReport uniqueness validation

2016-01-16T21:50:43+00:00

Previously it was "user has already been taken", when really we were
saying the user has already been reported.

Let the CI runner know about builds that this build depends on

2016-01-14T18:45:55+00:00

This allows us to implement artifacts passing: runner will download artifacts from all prior builds

Add Banzai::Filter::GollumTagsFilter for parsing Gollum's tags in HTML

2016-01-14T14:09:31+00:00

Update build model specs

2016-01-14T11:48:16+00:00

Update build specs for artifacts browser support

2016-01-14T11:48:15+00:00

Add method that checks if artifacts browser is supported

2016-01-14T11:48:14+00:00

This is needed because of backward compatibility. Previously artifacts
archive had `.tar.gz` format, but artifacts browser requires ZIP format
now.

Update specs for CI Build, add `artifacts?` method

2016-01-14T11:48:14+00:00

`artifacts?` method checks if artifacts archive is available.

Rename method that returns url to CI build artifacts download

2016-01-14T11:48:14+00:00

Merge branch 'feature/ldap-sync-edgecases' into 'master'

2016-01-14T11:00:08+00:00


LDAP Sync blocked user edgecases

Allow GitLab admins to block otherwise valid GitLab LDAP users
(https://gitlab.com/gitlab-org/gitlab-ce/issues/3462)

Based on the discussion on the original issue, we are going to differentiate "normal" block operations to the ldap automatic ones in order to make some decisions when its one or the other.

Expected behavior:

- [x] "ldap_blocked" users respond to both `blocked?` and `ldap_blocked?`
- [x] "ldap_blocked" users can't be unblocked by the Admin UI
- [x] "ldap_blocked" users can't be unblocked by the API
- [x] Block operations that are originated from LDAP synchronization will flag user as "ldap_blocked"
- [x] Only "ldap_blocked" users will be automatically unblocked by LDAP synchronization
- [x] When LDAP identity is removed, we should convert `ldap_blocked` into `blocked`
 
Mockup for the Admin UI with both "ldap_blocked" and normal "blocked" users:
![image](/uploads/4f56fc17b73cb2c9e2a154a22e7ad291/image.png)

There will be another MR for the EE version.

See merge request !2242

Merge branch 'fix/private-references' into 'master'

2016-01-14T10:36:39+00:00


Show referenced MRs & Issues only when the current viewer can access them

This addresses both issues identified in #6066.

## The private MR by user `remy2` with a note referencing to a public issue

![Screen_Shot_2016-01-12_at_16.45.02](/uploads/c245ec2c1fdea1f9ba05183c24e142d9/Screen_Shot_2016-01-12_at_16.45.02.png)

---

## The public issue viewed by user `remy` **who doesn't have access to `remy2/private-project`** before the fix

![Screen_Shot_2016-01-12_at_18.14.50](/uploads/8db5580e803f5bddd6cb935233c579a0/Screen_Shot_2016-01-12_at_18.14.50.png)

---

## The public issue viewed by user `remy` **who doesn't have access to `remy2/private-project`** with the fix

![Screen_Shot_2016-01-13_at_12.02.32](/uploads/cb199f7b78191fba486a11412412e307/Screen_Shot_2016-01-13_at_12.02.32.png)

---

## The public issue viewed by user `remy2` with the fix (no change)

![Screen_Shot_2016-01-13_at_11.54.06](/uploads/ddece590d69f597a95559beddcd36660/Screen_Shot_2016-01-13_at_11.54.06.png)


See merge request !2405