summaryrefslogtreecommitdiff
path: root/db/fixtures
Commit message (Collapse)AuthorAgeFilesLines
* Remove seed file from the development envrc/followup-40690Rémy Coutable2017-12-041-15/+0
| | | | | | | This backport a change made in the CE upstream MR, see https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/3593 Signed-off-by: Rémy Coutable <remy@rymai.me>
* Add a fixture file that uses seed-fu in the test env so that a borken ↵40690-rake-dev-setup-is-broken-due-to-the-latest-update-of-seed-fuRémy Coutable2017-11-301-0/+15
| | | | | | seed-fu is detected Signed-off-by: Rémy Coutable <remy@rymai.me>
* Update CycleAnalytics seed to account for multiple issue assigneesrs-cycle-analytics-seedRobert Speicher2017-11-161-37/+48
|
* Remove depreceted and big projectsZeger-Jan van de Weg2017-09-201-2/+2
|
* Move GitHooksService to Gitlab::GitJacob Vosmaer2017-08-231-1/+1
|
* Skip creating the merge request if repo is emptyLin Jen-Shin2017-08-111-0/+2
|
* Replace invalid chars while seeding environmentsZeger-Jan van de Weg2017-06-211-1/+1
|
* Merge branch 'instrument-infra' into 'master'Grzegorz Bizon2017-06-071-7/+17
|\ | | | | | | | | Add Prometheus metrics endpoint and basic infrastructure to meter code See merge request !11553
| * Handle case where GITLAB_PROMETHEUS_METRICS_ENABLED is non boolean value by ↵Pawel Chojnacki2017-06-061-1/+1
| | | | | | | | defaulting to false
| * Make production settings fixture use ↵Pawel Chojnacki2017-06-021-13/+10
| | | | | | | | | | | | Gitlab::CurrentSettings.current_application_settings small code formatting changes
| * Make fixture message more descriptivePawel Chojnacki2017-06-021-1/+1
| | | | | | | | + use strip_heredoc to make the text in tests much more readable
| * Allow enabling Prometheus metrics via ENV variable when db is seededPawel Chojnacki2017-06-021-7/+20
| |
* | Fix error while seeding projects in databaseda-fix-db-seedDouglas Barbosa Alexandre2017-06-061-1/+3
| |
* | Merge branch 'sidekiq-transaction' into 'master'Sean McGivern2017-06-051-1/+10
|\ \ | | | | | | | | | | | | | | | | | | Forbid Sidekiq scheduling in transactions Closes #27233 See merge request !9376
| * | Fix keys seedDouwe Maan2017-06-021-1/+10
| |/
* | Merge branch '30469-convdev-index' into 'master'Sean McGivern2017-06-051-0/+40
|\ \ | | | | | | | | | | | | | | | | | | ConvDev Index Closes #30469 See merge request !11377
| * | Add Conversational Development Index page to admin panelTaurie Davis, Simon Knox and Adam Niedzielski2017-06-011-0/+40
| |/
* | Make sure that environment was created before deployingLin Jen-Shin2017-06-021-0/+4
| |
* | Fix other use of CreateDeploymentService and makeLin Jen-Shin2017-06-021-6/+3
|/ | | | | it a bit more robust against missing options, which we did guard on for some cases.
* Introduce source to pipeline entitytrigger-sourceKamil Trzcinski2017-05-312-2/+2
|
* Backport of multiple_assignees_feature [ci skip]Valery Sizov2017-05-041-1/+1
|
* Move the nested groups seed behind an environment flagrs-skip-nested-groups-seedRobert Speicher2017-04-102-33/+41
| | | | | | | | | This seed downloads 2.1 GB worth of repositories. Google can afford the bandwidth, but if a person using the GDK is on a metered connection, that's not so great. Also the GDK test suite runs this seed, so every CI run for that project had to download those as well. Needlessly wasteful.
* Optimise trace handling code to use streaming instead of full readKamil Trzciński2017-04-061-1/+1
|
* Added mock deployment and monitoring service with environments fixturesKamil Trzciński2017-04-052-0/+70
|
* Ensure we generate unique usernames otherwise validations failrc/fix-transient-failures-following-no-ffakerRémy Coutable2017-04-041-2/+2
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Ensure the AbuseReport fixtures create unique reported usersRémy Coutable2017-04-031-1/+1
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Don't use FFaker in factories, use sequences insteadRémy Coutable2017-04-031-15/+17
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Fix the AbuseReport seederRémy Coutable2017-04-031-3/+23
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Fix production admin fixture to use the new `Users::CreateService`Rémy Coutable2017-03-301-3/+5
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Remove useless options from db/fixtures/development/17_cycle_analytics.rbRémy Coutable2017-03-201-1/+1
| | | | Signed-off-by: Rémy Coutable <remy@rymai.me>
* Fix up @DouweM reviewEric Eastwood2017-03-061-1/+1
|
* Fix the `Gitlab::Seeder` monkey patch to disable mail deliveryrs-dev-seed-timeRobert Speicher2017-03-021-2/+2
|
* Add development fixtures for nested groupsdz-nested-groups-fixturesDmitriy Zaporozhets2017-02-271-0/+69
| | | | Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
* Rename commit_file, commit_dir and remove_file and update specsDouwe Maan2017-02-241-1/+1
|
* Consistently create, update, and delete files, taking CRLF settings into accountDouwe Maan2017-02-241-9/+1
|
* Seed abuse reportsseed-abuse-reportsEric Eastwood2017-02-151-0/+5
| | | | | | | | | ``` rake db:seed_fu FILTER=abuse_reports ``` Thanks to @stanhu, https://gitlab.com/gitlab-org/gitlab-ce/issues/28059#note_23325328
* replace `find_with_namespace` with `find_by_full_path`Adam Pahlevi2017-02-031-1/+1
| | | | add complete changelog for !8949
* Fix race conditions for AuthorizedProjectsWorkerrefresh-authorizations-fork-joinYorick Peterse2017-01-2514-11/+37
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | There were two cases that could be problematic: 1. Because sometimes AuthorizedProjectsWorker would be scheduled in a transaction it was possible for a job to run/complete before a COMMIT; resulting in it either producing an error, or producing no new data. 2. When scheduling jobs the code would not wait until completion. This could lead to a user creating a project and then immediately trying to push to it. Usually this will work fine, but given enough load it might take a few seconds before a user has access. The first one is problematic, the second one is mostly just annoying (but annoying enough to warrant a solution). This commit changes two things to deal with this: 1. Sidekiq scheduling now takes places after a COMMIT, this is ensured by scheduling using Rails' after_commit hook instead of doing so in an arbitrary method. 2. When scheduling jobs the calling thread now waits for all jobs to complete. Solution 2 requires tracking of job completions. Sidekiq provides a way to find a job by its ID, but this involves scanning over the entire queue; something that is very in-efficient for large queues. As such a more efficient solution is necessary. There are two main Gems that can do this in a more efficient manner: * sidekiq-status * sidekiq_status No, this is not a joke. Both Gems do a similar thing (but slightly different), and the only difference in their name is a dash vs an underscore. Both Gems however provide far more than just checking if a job has been completed, and both have their problems. sidekiq-status does not appear to be actively maintained, with the last release being in 2015. It also has some issues during testing as API calls are not stubbed in any way. sidekiq_status on the other hand does not appear to be very popular, and introduces a similar amount of code. Because of this I opted to write a simple home grown solution. After all, all we need is storing a job ID somewhere so we can efficiently look it up; we don't need extra web UIs (as provided by sidekiq-status) or complex APIs to update progress, etc. This is where Gitlab::SidekiqStatus comes in handy. This namespace contains some code used for tracking, removing, and looking up job IDs; all without having to scan over an entire queue. Data is removed explicitly, but also expires automatically just in case. Using this API we can now schedule jobs in a fork-join like manner: we schedule the jobs in Sidekiq, process them in parallel, then wait for completion. By using Sidekiq we can leverage all the benefits such as being able to scale across multiple cores and hosts, retrying failed jobs, etc. The one downside is that we need to make sure we can deal with unexpected increases in job processing timings. To deal with this the class Gitlab::JobWaiter (used for waiting for jobs to complete) will only wait a number of seconds (30 by default). Once this timeout is reached it will simply return. For GitLab.com almost all AuthorizedProjectWorker jobs complete in seconds, only very rarely do we spike to job timings of around a minute. These in turn seem to be the result of external factors (e.g. deploys), in which case a user is most likely not able to use the system anyway. In short, this new solution should ensure that jobs are processed properly and that in almost all cases a user has access to their resources whenever they need to have access.
* Merge remote-tracking branch 'origin/master' into improve-pipeline-fixturesimprove-pipeline-fixturesKamil Trzcinski2016-12-186-26/+35
|\
| * Made Ci::Builds to have same ref as Ci::Pipeline in dev fixturestwonegatives2016-12-151-1/+1
| |
| * Allow users to seed the initial runner registration token using an ↵DJ Mountney2016-12-011-0/+16
| | | | | | | | | | | | | | environment variable This is useful for when runner is bundled with gitlab, like in a kubernetes stack, and we want the runner to be able to register with gitlab as soon as they both come up.
| * Refresh project authorizations using a Redis leaserefresh-authorizations-with-leaseYorick Peterse2016-11-254-12/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When I proposed using serializable transactions I was hoping we would be able to refresh data of individual users concurrently. Unfortunately upon closer inspection it was revealed this was not the case. This could result in a lot of queries failing due to serialization errors, overloading the database in the process (given enough workers trying to update the target table). To work around this we're now using a Redis lease that is cancelled upon completion. This ensures we can update the data of different users concurrently without overloading the database. The code will try to obtain the lease until it succeeds, waiting at least 1 second between retries. This is necessary as we may otherwise end up _not_ updating the data which is not an option.
| * Update ProjectTeam#fetch_members to use project authorizationsfix/drop-project-authorized-for-userAhmad Sherif2016-11-231-14/+19
| |
* | Improve pipeline fixturesKamil Trzcinski2016-11-281-19/+44
|/
* Merge branch 'feature/precalculate-authorized-projects' into 'master' Douwe Maan2016-11-183-0/+11
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Precalculate authorized projects in database ## What does this MR do? It caches user's authorized projects in database instead of using multiple unions, which should simplify and speed-up things since this operation (getting authorized projects) is used a lot. ## Are there points in the code the reviewer needs to double check? Did we miss a scenario where we need to refresh the list of projects? ## Does this MR meet the acceptance criteria? - [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [ ] ~~[Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md)~~ - [ ] ~~API support added~~ - Tests - [x] Added for this feature/bug - [x] All builds are passing - [x] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html) - [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [x] Branch has no merge conflicts with `master` (if it does - rebase it please) - [x] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) ## What are the relevant issue numbers? #23150 See merge request !6839
| * Precalculate user's authorized projects in databaseAhmad Sherif2016-11-183-0/+11
| | | | | | | | Closes #23150
* | Merge branch 'feature/cycle-analytics-events' into 'master' Douwe Maan2016-11-181-0/+2
|\ \ | |/ |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Cycle Analytics: Events per stage Adds list of events to each stage: - Issue: list of issues created in the last XX days, that have been labeled or added to a milestone. - Plan: list of commits that reference for the fist time an issue from the last stage. - Code: list of MR created in this stage - Test: List of unique builds triggered by the commits. - Review: List of MR merged - Staging: List of deployed builds - Production: list of issues with the time from idea to production Fixes #23449 - [x] [CHANGELOG](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CHANGELOG) entry added - [ ] [Documentation created/updated](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/doc/development/doc_styleguide.md) - Tests - [x] Added for this feature/bug - [x] All builds are passing - [x] Conform by the [merge request performance guides](http://docs.gitlab.com/ce/development/merge_request_performance_guidelines.html) - [x] Conform by the [style guides](https://gitlab.com/gitlab-org/gitlab-ce/blob/master/CONTRIBUTING.md#style-guides) - [x] Branch has no merge conflicts with `master` (if it does - rebase it please) - [ ] [Squashed related commits together](https://git-scm.com/book/en/Git-Tools-Rewriting-History#Squashing-Commits) See merge request !6859
| * run pipeline worker in cycle analytics dev setupJames Lopez2016-11-181-0/+2
| |
* | Remove empty db fixtures fileSemyon Pupkov2016-11-171-0/+0
|/
* Refactor code to use available and stopped statuses and refactor views to ↵Kamil Trzcinski2016-10-171-2/+2
| | | | use separate renders