- Feb 18, 2020
-
-
GitLab Bot authored
-
- Feb 17, 2020
-
-
GitLab Bot authored
-
- Feb 14, 2020
-
-
GitLab Bot authored
-
- Feb 12, 2020
-
-
GitLab Bot authored
-
- Feb 11, 2020
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- Feb 10, 2020
-
-
GitLab Bot authored
-
- Feb 08, 2020
-
-
GitLab Bot authored
-
- Feb 07, 2020
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- Feb 05, 2020
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- Feb 03, 2020
-
-
GitLab Bot authored
-
- Jan 28, 2020
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- Jan 22, 2020
-
-
GitLab Bot authored
-
- Jan 21, 2020
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- Jan 20, 2020
-
-
GitLab Bot authored
-
- Jan 16, 2020
-
-
GitLab Bot authored
-
- Jan 11, 2020
-
-
GitLab Bot authored
-
- Jan 10, 2020
-
-
GitLab Bot authored
-
- Jan 07, 2020
-
-
GitLab Bot authored
-
- Dec 24, 2019
-
-
GitLab Bot authored
-
- Dec 10, 2019
-
-
GitLab Bot authored
-
- Nov 19, 2019
-
-
GitLab Bot authored
-
- Nov 11, 2019
-
-
GitLab Bot authored
-
- Oct 29, 2019
-
-
GitLab Bot authored
-
- Oct 17, 2019
-
-
GitLab Bot authored
-
GitLab Bot authored
-
- Sep 05, 2019
-
-
Fabio Pitino authored
Detect if pipeline runs for a GitHub pull request When using a mirror for CI/CD only we register a pull_request webhook. When a pull_request webhook is received, if the source branch SHA matches the actual head of the branch in the repository we create immediately a new pipeline for the external pull request. Otherwise we store the pull request info for when the push webhook is received. When using "only/except: external_pull_requests" we can detect if the pipeline has a open pull request on GitHub and create or not the job based on that.
-
- Aug 13, 2019
-
-
Kamil Trzcińśki authored
We migrated all logic to `PipelineProcessWorker` and this worker become redundant.
-
- Aug 01, 2019
-
-
Kamil Trzcińśki authored
This implements the support for `needs:` keyword as part of GitLab CI. That makes some of the jobs to be run out of order.
-
- Jul 18, 2019
-
-
Andrew Newdigate authored
This allows the chaos endpoints to be invoked in Sidekiq so that this environment can be tested for resilience.
-
- Jul 02, 2019
-
-
Mayra Cabrera authored
- Add two new ActiveRecord models: - RootNamespaceStoragestatistics will persist root namespace statistics - NamespaceAggregationSchedule will save information when a new update to the namespace statistics needs to be scheduled - Inject into UpdateProjectStatistics concern a new callback that will call an async job to insert a new row onto NamespaceAggregationSchedule table - When a new row is inserted a new job is scheduled. This job will update call an specific service to update the statistics and after that it will delete thee aggregated scheduled row - The RefresherServices makes heavy use of arel to build composable queries to update Namespace::RootStorageStatistics attributes. - Add an extra worker to traverse pending rows on NAmespace::AggregationSchedule table and schedule a worker for each one of this rows. - Add an extra worker to traverse pending rows on NAmespace::AggregationSchedule table and schedule a worker for each one of this rows
-
- Jun 24, 2019
-
-
Add index for pages domain ssl auto renewal Add PagesDomain.needs_ssl_renewal scope Add cron worker for ssl renewal Add worker for ssl renewal Add pages ssl renewal worker queues settings
-
- Jun 04, 2019
-
-
Shinya Maeda authored
As we have a central domain for auto merge process today, we should use a single worker for any auto merge process.
-
- Apr 30, 2019
-
-
Domain will be removed by verification worker after 1 week of being disabled
-
Thong Kuah authored
Add endpoint to delete/uninstall a cluster application
-
Thong Kuah authored
+ to monitor progress of uninstallation pod
-