- 30 Sep, 2015 24 commits
-
-
Robert Speicher authored
We're now using default Devise behavior, so these tests were redundant.
-
Robert Speicher authored
-
Robert Speicher authored
-
Robert Speicher authored
Addresses internal https://dev.gitlab.org/gitlab/gitlabhq/issues/2611
-
Robert Speicher authored
-
Kamil Trzcinski authored
-
Robert Speicher authored
Fixes english information paragraph in admin/applications view See merge request !1470
-
Kamil Trzcinski authored
-
Diogo Resende authored
-
Diogo Resende authored
-
Robert Speicher authored
Apache needs gitlab-git-http-server on TCP [ci skip] See merge request !1462
-
Robert Speicher authored
Bump Ruby and Golang versions [ci skip] See merge request !1467
-
Dmitriy Zaporozhets authored
Use data stored in projects instead of ci_projects - 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. /cc @dzaporozhets See merge request !1404
-
Dmitriy Zaporozhets authored
Fix bug when removed file was not appearing in merge request diff Finally we can see removed files in merge request diff
✨ Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> Fixes #2533 See merge request !1471 -
Dmitriy Zaporozhets authored
Cleanup ci helpers Part of #2594 See merge request !1466
-
Kamil Trzciński authored
Add a missing RAILS_ENV=production to fix crontab clearing in the CI migration guide All other commands in the guide set this env var, but it's missing for the `whenever --clear-crontab` call and this causes it to not clear the crontab properly. See merge request !1474
-
Dimitar Dimitrov authored
All other commands in the guide set this env var, but it's missing here and this causes whenever not to clear the crontab file of gitab_ci properly.
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
- 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.
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Move CI project settings page to CE project settings area Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> Part of #2594 See merge request !1465
-
Diogo Resende authored
-
- 29 Sep, 2015 16 commits
-
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
Dmitriy Zaporozhets authored
Link directly to the projects page instead of the root controller If "Your Projects' Activity" dashboard setting were selected, it would be impossible to navigate to the projects page since the redirection would always bounce back to the activity dashboard. Fixes bug introduced by !1446. See merge request !1459
-
Dmitriy Zaporozhets authored
Make Ci::Commits belong to Project instead of Ci::Project See merge request !1455
-
Dmitriy Zaporozhets authored
Move CI triggers page to project settings area Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com> Part of #2594 See merge request !1461
-
Jacob Vosmaer authored
-
Jacob Vosmaer authored
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
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-
Kamil Trzcinski authored
-