Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitlab-foss.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
AgeCommit message (Collapse)Author
2019-12-13Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-12-13Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-12-12Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-12-11Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-12-10Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-12-10Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-12-05Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-11-28Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-11-26Ensure attributes that end in `_ids` are cleanedDJ Mountney
This prevents an issue where you can steal other projects objects by asking for ids that don't belong to you in import.
2019-11-19Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-11-19Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-11-19Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-11-18Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-11-15Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-11-12Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-11-11Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-11-09Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-31Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-30Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-28Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-28Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-25Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-18Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-11Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-07Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-04Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-04Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-03Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-03Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-10-01Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-30Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-27Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-27Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-25Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-19Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-18Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-13Add latest changes from gitlab-org/gitlab@masterGitLab Bot
2019-09-09Improve performance and memory usage of project exportKamil Trzciński
ActiveModel::Serialization is simple in that it recursively calls `as_json` on each object to serialize everything. However, for a model like a Project, this can generate a query for every single association, which can add up to tens of thousands of queries and lead to memory bloat. To improve this, we can do several things: 1. We use `tree:` and `preload:` to automatically generate a list of all preloads that could be used to serialize objects in bulk. 2. We observe that a single project has many issues, merge requests, etc. Instead of serializing everything at once, which could lead to database timeouts and high memory usage, we take each top-level association and serialize the data in batches. For example, we serialize the first 100 issues and preload all of their associated events, notes, etc. before moving onto the next batch. When we're done, we serialize merge requests in the same way. We repeat this pattern for the remaining associations specified in import_export.yml.
2019-09-06Normalize import_export structureKamil Trzciński
This brings a significant refactor to how we handle `import_export.yml`, merge it with EE and how we handle that for reader and saver. This is meant to simplify the code, and remove a ton of conditions to handle different models of the structure. This is also meant to prepare the structure to extend it much easier, like adding `preload:` or additional object types when needed. This does not change the behavior of import/export, rather unifies and simplifies the current implementation.
2019-09-06Merge branch 'ce-detect-github-pull-requests' into 'master'Kamil Trzciński
Port CreateGithubPullRequestEvents migration from EE See merge request gitlab-org/gitlab-ce!31802
2019-09-06Stop empty external auth classification labels overriding default labelsWill Chandler
Most of the project templates bundled with GitLab have an empty string set for `external_authorization_classification_label` in their `project.json`. When imported this overrides the default label set on the instance, causing the label to appear empty. This change sets empty labels to nil during import, allowing the default label to override it and be applied to the project.
2019-09-05CE port for pipelines for external pull requestsFabio Pitino
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.
2019-09-04Avoid calling freeze on already frozen strings in lib/gitlabdineshpanda
2019-08-15Allow disabling group/project email notificationsBrett Walker
- Adds UI to configure in group and project settings - Removes notification configuration for users when disabled at group or project level
2019-08-11Properly save suggestions in project exportsStan Hu
Previously imports would fail if a merge request note included a suggestion with an `ActiveRecord::HasManyThroughCantAssociateThroughHasOneOrManyReflection` exception. This was happening because suggestions were listed as a descendant of merge requests, but this doesn't work because suggestions are directly associated with notes, not merge requests, and that association is lost. Rails also disallows creating intializing a has_many association through a different object. We fix this by making `suggestions` a child of `notes` within a merge request. This doesn't fix previously broken exported project exports, but new exports will work. Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/65880
2019-08-05Make Issue boards importableJason Colyer
- Added space to li definiton - Remove milestone from import_export.yml
2019-08-02Make issue boards importableJason Colyer
- Added Importable to models/list.rb - Did unless: :importable? on board validation - Created changelog - Modified haml to show issue boards are importable - Added needed spec tests - Modified project.json to include board information - Added relevant models to all_models - Added relevant models to import_export - Added relevant models to safe_model_attributes
2019-07-24Merge branch 'optimise-import-performance' into 'master'Stan Hu
Optimise import performance Closes #64924 See merge request gitlab-org/gitlab-ce!31045
2019-07-24Optimise import performanceKamil Trzciński
- Fix `O(n)` complexity of `append_or_update_attribute`, we append objects to an array and re-save project - Remove the usage of `keys.include?` as it performs `O(n)` search, instead use `.has_key?` - Remove the usage of `.keys.first` as it performs a copy of all keys, instead use `.first.first`
2019-07-24LFS export records repository_type dataLuke Duncalfe
A project can have the same `LfsObject` linked with up to three `LfsObjectsProject` records. Each of these records would be for a different repository, recorded in the `repository_type` property. The different repositories at time of writing are "project", "wiki", and "design". See https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/13894 This change exports the list of `repository_type`s as a JSON mapping of oid => repository_types, which are imported to recreate the correct `LfsObjectsProject` records. https://gitlab.com/gitlab-org/gitlab-ee/issues/11090