- Dec 20, 2022
-
-
Changelog: changed
-
- Dec 16, 2022
-
-
Configure GitlabSubscriptions cron job and remove MembersAddedEvent subscription
-
- Dec 13, 2022
-
-
- Dec 07, 2022
-
-
Tan Le authored
This reverts merge request gitlab-org/gitlab!105975
-
- Dec 06, 2022
-
-
This change adds a worker to prune ProjectExportJob records that are older than 7 days. This will ensure the project_export_jobs DB table remains a reasonable size. It currently contains millions of rows. Changelog: performance
-
This adds a new internal API to create access token for Suggested Reviewers. Suggested Reviewers is an Machine Learning enabled feature that requires merge request data for build project-specific feature sets. The access token is used by the CI pipeline to call GitLab public GraphQL API to fetch merge requests. This change was introduced in !103881 but reverted !105930 because it breaks the migration due to write permission error.
-
Andy Schoenen authored
This adds some configuration options to be able to test the JiraConnect app in a development environment using the testing tool: https://gitlab.com/gitlab-org/manage/integrations/jira-connect-test-tool
-
- Dec 03, 2022
-
-
This reverts commit 6496911b.
-
-
- Dec 02, 2022
-
-
Gonzalo Servat authored
This reverts merge request !103881
-
- Dec 01, 2022
-
-
Tan Le authored
-
- Nov 24, 2022
-
-
Valery Sizov authored
As we migrated replication to SSF, it's not needed anymore Changelog: removed
-
- Nov 14, 2022
-
-
This worker will detect container repositories in need of a destruction and enqueue a delete container repository worker. In addition, this will also detect stale container repository removals and reset them so that they are retried. This worker is gated behind a feature flag.
-
Michał Zając authored
-
- Nov 09, 2022
-
-
Marco (Gregorius) authored
This reverts commit 724c1506, reversing changes made to ee7598ca. This revert fixes Sidekiq performance degradation on the default routing rules introduced in 15.4 for self-managed. In short, if users are configuring Sidekiq queue_groups with queue selector, some processes could be idle because all jobs are routed to the `default` queue instead of named queue as they'd expect. See below issue for more info: https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/1991 Changelog: fixed
-
- Nov 02, 2022
-
-
David Fernandez authored
Changelog: changed
-
- Oct 24, 2022
-
-
Nikola Milojevic authored
-
- Oct 18, 2022
-
-
Alejandro Rodríguez authored
This should reduce the load into redis for a setup with a large number of Sidekiq processes. In practice this is bringing a bugfix that is already implemented in a newer version of Sidekiq. Until we upgrade, we can take this approach. See gitlab-org/gitlab!99030 (comment 1117078517) for more details.
-
Imre Farkas authored
-
This change migrates the following queues; - security_findings_delete_by_job_id - cronjob:security_findings_cleanup Changelog: changed
-
- Sep 29, 2022
-
-
Manoj M J authored
Shift `can_create_group` to ApplicationSetting Changelog: added
-
- Sep 27, 2022
-
-
Alejandro Rodríguez authored
In order to enqueue sidekiq-cron scheduled jobs, a poller runs in Sidekiq at a configurable interval (30 seconds by default) and retrieves all the cron jobs configured in redis. In a setup with multiple Sidekiq instances this can result in a significant amount of load in redis (see https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/1932). We introduce a setting that allows specifying a cron polling interval, and disables polling at all if the interval is 0. In the future this will also enable having multiple Sidekiq clusters pointing at different redis instances, by disabling the sidekiq-cron poller in all but one of those clusters (see https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/1439).
-
- Sep 16, 2022
-
-
Account takeovers are a common cybersecurity threat made much easier when a user decides to use a weak password to protect their account. This MR introduces a static list of known weak passwords against which the user's chosen password can be compared. The password is also validated against components of the user's attributes, such as their name, email, and username. Weak passwords are prevented only when the `block_weak_passwords` feature flag is enabled, and only at registration or when a password is changed. (It is not checked or enforced when the password is not changed, such as during sign-in). Notably, and in comparison to password complexity rules, blocking weak passwords is a requirement of NIST SP 800-63B: > When processing requests to establish and change memorized secrets, > verifiers SHALL compare the prospective secrets against a list that > contains values known to be commonly-used, expected, or compromised. > > - https://pages.nist.gov/800-63-3/sp800-63b.html See also: - !86310 - #23610
-
- Sep 15, 2022
-
-
Marin Hannache authored
Signed-off-by:
Marin Hannache <git@mareo.fr>
-
Bogdan Denkovych authored
Support delivery of emails using Microsoft Graph API with OAuth 2.0 client credentials flow. Related to &8259 Closes #369980 Closes #365524 Changelog: added
-
Marin Hannache authored
The internal kerberos_spnego provider was added as a replacement for the omniauth-kerberos gem, the later is password-based and thus vulnerable to the Zanarotti attack while the former is ticket-based. To ease the transition before the removal of the password-based kerberos provider, an override was added to make the kerberos_spnego provider compatible with the kerberos provider existing identities, this compatibility layer unfortunately introduced two bugs: #241318 #344071 Since the removal of the old password-based kerberos provider in !86036, we can now rename the new provider, as suggested in #241318 (comment 409272802) Changelog: changed EE: true Signed-off-by:
Marin Hannache <git@mareo.fr>
-
- Sep 13, 2022
-
-
- no longer needed due to change in direction Changelog: removed
-
Marco (Gregorius) authored
We want to update self-managed instances to route all Sidekiq jobs to the 'default' queue. By updating the Rails initializer, we wouldn't need to update all other installations such as Omnibus and Helm Chart. https://gitlab.com/gitlab-com/gl-infra/scalability/-/issues/1491 Changelog: changed
-
- Sep 09, 2022
-
-
Imre Farkas authored
-
- Sep 06, 2022
-
-
- Aug 25, 2022
-
-
Steve Abrams authored
Update the container_registry_migration_enqueuer_worker cron to run at 15 and 45 past every hour.
-
- Aug 11, 2022
-
-
Projects with no activity for an year are considered inactive.
-
- Jul 31, 2022
-
-
Thiago Figueiró authored
In config/ directory
-
- Jul 27, 2022
-
-
Pedro Pombeiro authored
Change ci_runner_versions_reconciliation_worker to @daily with randomness for better workload distribution Changelog: changed
-
- Jul 12, 2022
-
-
with existing ci_runners records Changelog: added
-
- Jul 01, 2022
-
-
Removes the unused `add_pusher` and `all_broken_builds` setting Changelog: removed
-
- Jun 29, 2022
-
-
This is required for FIPS compliance. Changelog: added
-
- Jun 07, 2022
-
-
Corinna Gogolok authored
This change introduces a new callout feature name called `submit_license_usage_data_banner`. It will be used in an upcoming banner to ask an instance admin to submit seat utilization data via email. The banner can be dismissed after exporting the license usage data. But it will be reset each month relative to the license's start date. The new worker `ResetSubmitLicenseUsageDataBannerWorker` will run every day at midnight for a possible reset. Changelog: added EE: true
-
- Jun 01, 2022
-
-
- Use each_batch instead of find_each to traverse the table using primary index and prevent statement timeouts. - Monitor the elapsed time of inactive_projects_deletion_cron_worker and exit before 5 minutes to avoid breaching the maximum allowed execution latency for low urgency workers. - Update inactive_projects_deletion_cron_worker to run at every 10th minute instead of running daily. Changelog: performance
-
- May 19, 2022
-
-
Adam Hegyi authored
This change moves out the loose foreign key cron scheduling from EE so it will run also on CE. Changelog: fixed
-