delta/gitlab/gitlab-ce.git/spec/models, branch fix-diff-comments gitlab.com: gitlab-org/gitlab-ce.git Add sentry integration 2016-01-18T16:15:10+00:00 Jeroen Nijhof jeroen@jeroennijhof.nl 2016-01-18T16:15:10+00:00 85e0fce9eee4f20c6c627209828f7351ab0aedae 






Use a more sensible message for the AbuseReport uniqueness validation
2016-01-16T21:50:43+00:00

Robert Speicher
rspeicher@gmail.com

2016-01-16T21:25:35+00:00

d633755350f1549d4643ac527980c9b28aa1287c

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





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

Kamil Trzcinski
ayufan@ayufan.eu

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

ac652d82f17d378e485dcef15a8fabdcf9bad76b

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





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

Douglas Barbosa Alexandre
dbalexandre@gmail.com

2016-01-12T04:05:18+00:00

a6a5990ee5f504107944c3bba5c18dbdea9f5207












Update build model specs
2016-01-14T11:48:16+00:00

Grzegorz Bizon
grzesiek.bizon@gmail.com

2016-01-11T10:18:21+00:00

f80d7a868e83f7cbba2d0c42ed9464552d9c7a0b












Update build specs for artifacts browser support
2016-01-14T11:48:15+00:00

Grzegorz Bizon
grzesiek.bizon@gmail.com

2016-01-05T13:05:44+00:00

cfffc9eff2c394259000090fb8c4c116863c9199












Add method that checks if artifacts browser is supported
2016-01-14T11:48:14+00:00

Grzegorz Bizon
grzesiek.bizon@gmail.com

2015-12-28T11:06:27+00:00

5ff7ec42dc8759717c485478261128d61ea70b9a

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





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

Grzegorz Bizon
grzesiek.bizon@gmail.com

2015-12-28T10:43:15+00:00

8eeed761a9c25ea8ccfc347fbd3f5894b5957d9e

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





`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

Grzegorz Bizon
grzesiek.bizon@gmail.com

2015-12-28T10:21:01+00:00

9e0e9342a47022a9caaa4a5596ec3ddb91fddc58












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

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

Douwe Maan
douwe@gitlab.com

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

4d64a32c88dd5f87621d391c0f10f6acef094073


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





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