delta/gitlab/gitlab-ce.git/lib, branch project_moving gitlab.com: gitlab-org/gitlab-ce.git Delegate ci_project parameters to projects 2015-09-30T10:48:40+00:00 Kamil Trzcinski ayufan@ayufan.eu 2015-09-23T10:47:29+00:00 b9ccc79cb5d67e356edce3778b6a17def985ed22 - It delegates name, path, gitlab_url, ssh_url_to_repo - Remove ability to set this parameters using CI API This fixes GitLab project rename, namespace change, repository rename, etc. 
- It delegates name, path, gitlab_url, ssh_url_to_repo
- Remove ability to set this parameters using CI API

This fixes GitLab project rename, namespace change, repository rename, etc.
Merge branch 'master' into 'master' 2015-09-29T10:31:42+00:00 Jacob Vosmaer contact@jacobvosmaer.nl 2015-09-29T10:31:42+00:00 958af6f5c220731a2ee274c343d818751d388762 Add support for AWS S3 Server-Side Encryption support This adds support for AWS S3 SSE with S3 managed keys, this means the data is encrypted at rest and the encryption is handled transparently to the end user as well as in the AWS Console. ## Points to double check I'm unsure on the best way to the handle the default. I've followed the `multipart_upload` de facto in the app. I'm happy to change this if required or if it will impact elsewhere e.g. omnibus packages I also think I've managed to catch all of the documentation for this change as well. ### Why is this required Many enterprises require good backup support but also for this to be encrypted. By default backups aren't encrypted, this allows at rest encryption to be supported in GitLab backups providing a layer of security should the physical media not be properly disposed of. Relates to issue #2478. See merge request !1280 

Add support for AWS S3 Server-Side Encryption support

This adds support for AWS S3 SSE with S3 managed keys, this means the
data is encrypted at rest and the encryption is handled transparently to
the end user as well as in the AWS Console.

## Points to double check
I'm unsure on the best way to the handle the default. I've followed the `multipart_upload` de facto in the app. I'm happy to change this if required or if it will impact elsewhere e.g. omnibus packages

I also think I've managed to catch all of the documentation for this change as well.

### Why is this required
Many enterprises require good backup support but also for this to be encrypted. By default backups aren't encrypted, this allows at rest encryption to be supported in GitLab backups providing a layer of security should the physical media not be properly disposed of.

Relates to issue #2478.


See merge request !1280
 Merge branch 'orphaned-repo-cleanup' into 'master' 2015-09-29T07:35:59+00:00 Douwe Maan douwe@gitlab.com 2015-09-29T07:35:59+00:00 084e35527c6269ce20db03c24516c45dfe362c0b Improve repo cleanup task I accidentally wrote a new script, not seeing we already had one. But the old one did not do enough (it only handled global namespace orhpans) so I figured I should just drop in the new script. See merge request !1298 

Improve repo cleanup task

I accidentally wrote a new script, not seeing we already had one.
But the old one did not do enough (it only handled global namespace orhpans) so I figured I should just drop in the new script.

See merge request !1298
 Merge pull request #9650 from szechyjs/fb-close-comment 2015-09-25T23:46:50+00:00 Stan Hu stanhu@gmail.com 2015-09-25T23:46:50+00:00 4957415e00207e0eae6184237f19bcd7c7401598 FogBugz Import: Include closed comments since they may contain user data 
FogBugz Import: Include closed comments since they may contain user data
 Add support for AWS S3 Server-Side Encryption support 2015-09-25T16:06:31+00:00 Paul Beattie paul@paul-beattie.com 2015-09-10T15:57:43+00:00 253d2320ab3d3473509d6abe4a62be90428f20c4 This adds support for AWS S3 SSE with S3 managed keys, this means the data is encrypted at rest and the encryption is handled transparently to the end user as well as in the AWS Console. This is optional and not required to make S3 uploads work. 
This adds support for AWS S3 SSE with S3 managed keys, this means the
data is encrypted at rest and the encryption is handled transparently to
the end user as well as in the AWS Console. This is optional and not
required to make S3 uploads work.
api: add enable_ssl_verification to PUT/POST hooks 2015-09-24T16:34:16+00:00 Ben Boeckel ben.boeckel@kitware.com 2015-09-24T16:34:16+00:00 eb912a534bee312d5d5e5bcc44767860c1c41864 






api: expose note_events and enable_ssl_verification for hooks
2015-09-24T16:33:11+00:00

Ben Boeckel
ben.boeckel@kitware.com

2015-09-24T16:33:11+00:00

22db4398c69e75da8c56775a7c815b6e2cb38496












Merge branch 'cleanup-ci-dashboard' into 'master'

2015-09-24T07:32:29+00:00

Douwe Maan
douwe@gitlab.com

2015-09-24T07:32:29+00:00

a58c6e9a9561ffbb3d16a3a9a45bd90a34735b50


Cleanup ci dashboard

Part of #2594. Based on !1403

* remove rendering GitLab projects with not enabled CI on CI dashboard
* remove enabling CI for projects from CI dashboard (now its done by simply pushing `.gitlab-ci.yml`)
* simplify the projects query for CI dashboard 

See merge request !1405





Cleanup ci dashboard

Part of #2594. Based on !1403

* remove rendering GitLab projects with not enabled CI on CI dashboard
* remove enabling CI for projects from CI dashboard (now its done by simply pushing `.gitlab-ci.yml`)
* simplify the projects query for CI dashboard 

See merge request !1405






Fix LDAP attribute mapping
2015-09-23T14:37:59+00:00

Douwe Maan
douwe@gitlab.com

2015-09-23T14:37:59+00:00

73a3df4de351528dfe954c0f44af1f0e45b221d0












Simplify CI projects query
2015-09-23T13:30:24+00:00

Dmitriy Zaporozhets
dmitriy.zaporozhets@gmail.com

2015-09-23T13:30:24+00:00

31b15e3dce2817d8cd6d70cda97c6b9dbf5c7f8a

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>





Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>