| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
The configuration is currently only specified in CI, by moving it into
`.mdlrc` we get immediate feedback locally in supported editors.
To ensure `mdl` is available it's also added to the `Gemfile`, though
CI will still use the version installed in the `gitlab-docs-lint` image.
|
|
|
|
| |
Also fixes instances in Markdown that broke the rule.
|
|
|
| |
This reverts merge request !30130
|
|
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|\
| |
| |
| |
| | |
Use PostgreSQL 9.6.11 in CI tests
See merge request gitlab-org/gitlab-ce!30270
|
| |
| |
| |
| |
| |
| | |
Specify the minor version of postgresql for CI
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
|
| | |
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Squash old migrations
Closes #59177
See merge request gitlab-org/gitlab-ce!30226
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
The junit reports are creating 90mb files inside of redis for
`gitlab-ce/ee` project. There is an ongoing production incident
https://gitlab.com/gitlab-com/gl-infra/production/issues/928 that is
because of high CPU uitlaization on the redis nodes. GitLab-ce/ee are
the highest consumers of memory becuase of these junit reports.
This is a bandage until we can scale redis properly.
|
|/ /
| |
| |
| |
| |
| | |
Linting rule not enabled for now
because tooling produces false
positives.
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Get memory data after booting app in production
Closes #62722
See merge request gitlab-org/gitlab-ce!30185
|
| |/
| |
| |
| |
| |
| | |
Preload the app in `production` env, hit it with a single request, and
gather total gem memory consumption data using `derailed exec perf:mem`
from `derailed_benchmarks`. Present the result as MR metrics.
|
| |
| |
| |
| |
| | |
We repeat the same code in many places. With the support of multiple
extends, we can clean up several jobs.
|
| |
| |
| |
| | |
Adjusts asterisks to hyphens in assorted docs to allow lint rule to pass
|
|\ \
| |/
| |
| | |
# Conflicts:
# lib/gitlab/database.rb
|
| |
| |
| | |
This reverts merge request !30031
|
| |
| |
| |
| |
| |
| | |
Preload the app in `production` env, hit it with a single request, and
gather total gem memory consumption data using `derailed exec perf:mem`
from `derailed_benchmarks`. Present the result as MR metrics.
|
| | |
|
|/
|
|
|
|
| |
If you chose to use the rollback migration feature on your current
version for example, you should still have a way to migrate, being
that you are still on a supported migration path.
|
|\
| |
| |
| |
| |
| |
| |
| |
| | |
into 'master'
Improve Review Apps cleanup when previous deployment failed by only issuing an `helm delete` command
Closes #63639 and #62161
See merge request gitlab-org/gitlab-ce!28661
|
| |
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
| |
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|\ \
| |/
|/|
| |
| | |
Add gem size information to metrics.txt in memory CI artifacts
See merge request gitlab-org/gitlab-ce!29827
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This includes several changes:
- Rename memory-static to generate-gems-size-metrics-static
- Rename memory-static-objects to generate-gems-memory-metrics-static
- Change generate-gems-size-metrics-static interface. The script now
expect `bundle exec derailed bundle:mem` output as its input. The
script output to stdout, or stderr for error message.
- Change generate-gems-memory-metrics-static interface. The script now
expect `bundle exec derailed bundle:objects` output as its input.
The script output to stdout, or stderr for error message.
- Generate gem size metrics. Script generate-gems-size-metrics-static
extract each gem size from `bundle exec derailed bundle:mem` output.
Save output to metrics file in format: 'gem_size_mb{name="zip"} 0.5'
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Note: This commit relies on
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/26801
which brings support to multiple extends.
While `cache: {}` can disable a cache being set globally, it doesn't
work with extends, which will perform a reverse deep merge based on the
keys.
The cache defined in the base `.default-cache` job
won't be disabled in the report jobs.
As a side effect, the `code_quality`, `sast`, and `dependency_scanning`
jobs are running on a larger code base than expected, leading to
timeouts.
fixes https://gitlab.com/gitlab-org/gitlab-ee/issues/11303
fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/60879
fixes https://gitlab.com/gitlab-org/gitlab-ee/issues/12021
|
| | |
|
|/
|
|
|
| |
Also adds and one linting rule
and makes project conform to it.
|
|\
| |
| |
| |
| | |
Only support postgresql (minimal version)
See merge request gitlab-org/gitlab-ce!29790
|
| |
| |
| |
| | |
MySQL support has been removed
|
|/
|
|
|
|
|
|
| |
Two static memory benchmarks will be included in our CI pipeline. It
will load gems from the Gemfile and check the amount of RAM consumed
as well as the number of objects allocated and retained.
Aggregated values will be included as 'metrics' into MRs while full
reports will be downloadable as job artifacts.
|
|\
| |
| |
| |
| | |
Only push to assets-compile-cache when in master
See merge request gitlab-org/gitlab-ce!28854
|
| |
| |
| |
| | |
Also update dependencies to match updated job names
|
| | |
|
|/
|
|
|
|
|
|
|
|
| |
One can not upgrade straigt from 9.3 to 12.0, due to the schema changes
being backported. Instead, one must first upgrade to 11.11.X. Omnibus
already enforces this, and our online upgrade guidelines also cover
this.
By changing the CI config we don't have to adjust the backport migration
to handle a migration path that one can not take.
|
|
|
|
|
|
|
|
| |
This updates our build images to use node@12. We are also adding a
sentence to the from-source installation that while we require a minimum
version of node@8, we also recommend node@12. Last but not least, we
change the version of node in the .nvmrc so that developers using nvm
can automatically use node@12 with the project
|
|\
| |
| |
| |
| | |
Allow the review-deploy and review-qa-* jobs to fail for now
See merge request gitlab-org/gitlab-ce!29208
|
| |
| |
| |
| | |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
into 'master'
Harden gitlab:assets:compile against transient network failures
Closes gitlab-ee#10403
See merge request gitlab-org/gitlab-ce!29211
|
| |/ |
|
|/
|
|
|
|
|
| |
This commit adds CI job that validates all `*.yml`
with `yamllint`.
This commit fixes all offenses present in repository.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Add knapsack qa report and use it to run tests in parallel
Use the RSpec runner with knapsack
The way the Knapsack runner uses exec to start rspec seems
incompatible with the way we expect it to work. Plus, it requires
specifying KNAPSACK_TEST_DIR.
Instead, we use knapsacks AllocatorBuilder to select the spec
files to run, and then start rspec as normal, via
RSpec::Core::Runner.run
This also means we can incorporate tags.
Let the job run automatically
Include KNAPSACK_TEST_FILE_PATTERN in vars
Check all defined knapsack env vars before requiring knapsack
|
|
|
|
|
| |
Chrome is already installed in this image, and the apt-get update
is only used to install jq.
|
|
|
|
|
|
| |
[run mysql]
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
|
|
|
| |
This reverts commit 744f1f2e7037f5c70c3168d9e2e89b1c327465d2, reversing
changes made to c4d930e5f54e7da07c80cc028dfc0f5c08719146.
|
|
|
|
| |
This way even if review-deploy failed we can still run it.
|
|
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
|
|
|
|
|
| |
Ruby 2.6 offers better performance and memory usage:
https://www.rubyguides.com/2018/11/ruby-2-6-new-features/
Part of https://gitlab.com/gitlab-org/gitlab-ce/issues/57323
|
|
|
|
| |
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|
|
|
| |
Signed-off-by: Balasankar "Balu" C <balasankar@gitlab.com>
|