| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
discussion resolution
|
|
|
|
# Conflicts:
# db/schema.rb
|
|
|
|
as we destroy all gpg_signatures we don't need to downcase the email
addresses anymore.
|
|
|
|
|
|
This is faster for the deployment process, as the destroyed signatures
will be re-generated on demand again, instead of updating them all on
deploy.
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
protected index on ci_builds.
|
|
|
|
|
|
|
|
Drop protected from pipeline. Add protected to ci_bilds.
|
|
|
|
builds_for_shared_runner and builds_for_specific_runner read the flag instead of executing protected_for? one by one.
|
|
|
|
|
|
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.
|
|
|
|
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
|
|
|
|
`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.
|
|
This is an amalgamation of:
* Cory Hinshaw: Initial implementation !5552
* Rémy Coutable: Updates !9350
* Nick Thomas: Resolve conflicts and add ED25519 support !13712
|
|
backstage/gb/rename-ci-cd-processing-sidekiq-queues
* commit '2be34630623711fc20ef8c101b5cef688f207cc1':
Common Docker Documentation Location in `gitlab-ce`
fix deprecation warning present during webpack compiles
Enable 5 lines of Sidekiq backtrace lines to aid in debugging
Add support for copying permalink to notes via more actions dropdown
Handle creating a nested group on MySQL correctly
Decrease statuses batch size even more in a migration
Fix repo editor scrollbar
Replace 'source/search_code.feature' spinach test with an rspec analog
Authorizations regarding OAuth - style confirmation
Update README.md
Refactor complicated API group finding rules into GroupsFinder
Fix group and project search for anonymous users
Document version Group Milestones API introduced
Allow v4 API GET requests for groups to be unauthenticated
Adjust a range and a size in stages statuses migration
Update README.md
Point to /developers on docs/administration/authentiq.md
Indexes GFM markdown guide
use inline links instead of referenced
Add index on ci_runners.contacted_at
|
|
|
|
Adjust a range and a batch sizes in stages statuses migration
Closes #36793
See merge request !13767
|
|
# Conflicts:
# db/schema.rb
|
|
Re-allow appearances.description_html to be NULL
Closes #36919
See merge request !13806
|
|
|
|
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
|
|
Move GitHooksService into Gitlab::Git
See merge request !13739
|
|
|
|
|
|
|
|
* master: (115 commits)
Use event-based waiting in Gitlab::JobWaiter
Make sure repository's removal work for legacy and hashed storages
Use `@hashed` prefix for hashed paths on disk, to avoid collision with existing ones
Refactor project and storage types
Prevent using gitlab import task when hashed storage is enabled
Some codestyle changes and fixes for GitLab pages
Removed some useless code, codestyle changes and removed an index
Fix repository reloading in some specs
Changelog
Moving away from the "extend" based factory to a more traditional one.
Enable automatic hashed storage for new projects by application settings
New storage is now "Hashed" instead of "UUID"
Add UUID Storage to Project
Move create_repository back to project model as we can use disk_path and share it
Codestyle: move hooks to the same place and move dependent methods to private
Use non-i18n values for setting new group-level issue/MR button text
indexes external issue tracker
copyedit
indexes user/search/ from /user/index
Correctly encode string params for Gitaly's TreeEntries RPC
...
|
|
|
|
There might be some projects where the namespace was removed, but the
project wasn't. For these the projects still have a `namespace_id`
set. So this adds a post-deploy migration remove all projects that are
pending delete, and have a `namespace_id` that is non-existing.
|
|
|
