- 19 9月, 2017 1 次提交
-
-
由 Yorick Peterse 提交于
This removes the need for a default scope that adds a "WHERE project_id = X" clause. This commit also includes an additional index for Environment#last_deployment, ensuring this query uses just an index scan instead of also applying a Filter. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/36877
-
- 16 9月, 2017 1 次提交
-
-
由 Felipe Artur 提交于
-
- 15 9月, 2017 1 次提交
-
-
由 Yorick Peterse 提交于
This index is required to allow fast retrieval of recent push events without merge requests. Without this index in place the query would lead to PostgreSQL scanning over 150 000 index entries all the time, easily taking up between 200 and 500 milliseconds. This index reduces the time spent in this process to around 40 milliseconds on GitLab.com.
-
- 13 9月, 2017 1 次提交
-
-
由 Yorick Peterse 提交于
-
- 11 9月, 2017 1 次提交
-
-
由 Annabel Dunstone Gray 提交于
This reverts merge request !14148
-
- 08 9月, 2017 2 次提交
-
-
由 Rubén Dávila 提交于
Revert "Merge branch '35012-navigation-add-option-to-change-navigation-color-palette' into 'master'" This reverts merge request !13619
-
由 Jarka Kadlecova 提交于
-
- 07 9月, 2017 4 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
由 Dmitriy Zaporozhets 提交于
Signed-off-by: NDmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
-
由 Kamil Trzcinski 提交于
-
由 Rubén Dávila 提交于
-
- 06 9月, 2017 7 次提交
-
-
由 Yorick Peterse 提交于
This finishes the procedure for migrating events from the old format into the new format. Code no longer uses the old setup and the database tables used during the migration process are swapped, with the old table being dropped. While the database migration can be reversed this will 1) take a lot of time as data has to be coped around 2) won't restore data in the "events.data" column as we have no way of restoring this. Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37241
-
由 Alexander Keramidas 提交于
-
由 Sean McGivern 提交于
-
由 Sean McGivern 提交于
-
由 Ashley Dumaine 提交于
-
由 Ashley Dumaine 提交于
-
由 Zeger-Jan van de Weg 提交于
-
- 05 9月, 2017 6 次提交
-
-
由 Kamil Trzcinski 提交于
-
由 Jarka Kadlecova 提交于
-
由 Alexis Reigel 提交于
-
由 Alexis Reigel 提交于
To avoid having to implement legacy code handling for the obsolete `verified_signature` attribute and to avoid any race conditions during the zero-downtime-deployment we do the following: 1. Destroy all records 2. Migration: Use add_column_with_default to add the new attribute and update the verification_status values on records created between 1. and 2. 3. Deploy the new code 4. Post migration: Destroy all records Like this we make sure that at no point there is a record with a `nil` value for the new `verification_status` attribute.
-
由 Alexis Reigel 提交于
-
由 Shinya Maeda 提交于
-
- 04 9月, 2017 1 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
- 03 9月, 2017 6 次提交
-
-
由 Shinya Maeda 提交于
-
由 Shinya Maeda 提交于
Remove access_level index from runner. Add protected on ci_pipelines. Add protected index on ci_builds.
-
由 Shinya Maeda 提交于
Re-organize schema. Drop protected from runner. Add access_level to runner. Drop protected from pipeline. Add protected to ci_bilds.
-
由 Shinya Maeda 提交于
-
由 Shinya Maeda 提交于
Solution 1. Persists protected(ref) flag on ci_pipelines table. builds_for_shared_runner and builds_for_specific_runner read the flag instead of executing protected_for? one by one.
-
由 Shinya Maeda 提交于
-
- 01 9月, 2017 4 次提交
-
-
由 Zeger-Jan van de Weg 提交于
-
由 Zeger-Jan van de Weg 提交于
Given the user can soon have multiple config sources for CI, we now store what type at the time of the pipeline run we chose. This will give us insight into what triggered the new pipeline so we can display it to the enduser.
-
由 Zeger-Jan van de Weg 提交于
-
由 Zeger-Jan van de Weg 提交于
Behind an application setting, which defaults to false, this commit implements the implied CI/CD config. Which means that in the case we can't find the `.gitlab-ci.yml` on the commit we want to start a pipeline for, we fall back to an implied configuration. For now the Bash template has been copied to `Auto-Devops.gitlab-ci.yml` so the tests actually work. Fixes #34777
-
- 31 8月, 2017 2 次提交
-
-
由 Nick Thomas 提交于
`allowed_key_types` is removed and the `minimum_<type>_bits` fields are renamed to `<tech>_key_restriction`. A special sentinel value (`-1`) signifies that the key type is disabled. This also feeds through to the UI - checkboxes per key type are out, inline selection of "forbidden" and "allowed" (i.e., no restrictions) are in. As with the previous model, unknown key types are disallowed, even if the underlying ssh daemon happens to support them. The defaults have also been changed from the lowest known bit size to "no restriction". So if someone does happen to have a 768-bit RSA key, it will continue to work on upgrade, at least until the administrator restricts them.
-
由 Nick Thomas 提交于
This is an amalgamation of: * Cory Hinshaw: Initial implementation !5552 * Rémy Coutable: Updates !9350 * Nick Thomas: Resolve conflicts and add ED25519 support !13712
-
- 25 8月, 2017 1 次提交
-
-
由 Yorick Peterse 提交于
This column isn't always set (e.g. when upgrading from older instances) and technically it could be NULL (e.g. when flushing the cache). Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/36919
-
- 22 8月, 2017 2 次提交
-
-
由 Grzegorz Bizon 提交于
-
由 Gabriel Mazetto 提交于
-