| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |\ \ \ \ \ \ \
| |_|_|/ / / /
|/| | | | | |
| | | | | | |
| | | | | | | |
Remove Sentry settings from application settings
See merge request gitlab-org/gitlab-ce!28447
|
| | | |/ / / /
| |/| | | | |
|
| |/ / / / / |
|
| | |_|_|/
|/| | | |
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
This is a small change to move AfterCommitQueue.inside_transaction?
to Gitlab::Database.inside_transaction? Since this change is required
by different changes which may not arrive in sequence, it's easier
to extract this change out on it's own.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Add ability to reorder issues
See merge request gitlab-org/gitlab-ce!29012
|
| | | | |
| | | |
| | | |
| | | | |
to support manual sorting on the frontend
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Backport changes made by EE to various YAML configuration files
See merge request gitlab-org/gitlab-ce!29606
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
To make this happen, we need to conditionally add the group_saml
strategy when running tests, but only on EE. This requires some changes
to Gitlab.ee? so that it can be used before/without loading the Rails
environment. We also have to change how we require a few files, so this
can run outside of Rails.
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| | | | | | |
|
| |\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
into 'master'
Errors in application settings panel shows wrong panel
See merge request gitlab-org/gitlab-ce!25434
|
| | |/ / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Updating multiple application settings panels through
a single action causes the incorrect action to be shown
when there are errors. Instead, make each panel action
handle both updating and display.
|
| |/ / / /
| | | |
| | | |
| | | | |
MySQL support has been removed
|
| |/ / /
| | |
| | |
| | |
| | | |
It's an empty file that was committed by accident on
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28565
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Remove deprecated group routes
See merge request gitlab-org/gitlab-ce!29351
|
| | | |/
| |/|
| | |
| | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Import bootstrap styles from gitlab-ui
See merge request gitlab-org/gitlab-ce!26165
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Use gitlab_ui.scss instead of all the bootstrap imports
Allow the ../node_modules path from gitlab_ui.scss to resolve
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
Backport EE changes to config/application.rb
See merge request gitlab-org/gitlab-ce!29557
|
| | |/ /
| | |
| | |
| | |
| | |
| | | |
This backports the EE changes made to this config file to CE. EE
specific bits do not need an `if Gitlab.ee?`, as everything will work
transparently when using CE.
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| | |
as per documentation https://docs.gitlab.com/ee/api/repository_files.html
You can use read_repository to access repository_file API.
Not sure about write_repository as it is new and not documented in that page.
|
| | | |
|
| | |
| |
| |
| |
| | |
Because there will be similar observer for PumaWorkerKiller,
it makes sense to keep both on better place.
|
| |\ \
| |/
|/|
| |
| | |
Update server API to enable switch prometheus endpoint
See merge request gitlab-org/gitlab-ce!29186
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
PumaWorkerKiller is used for periodically checking and killing
workers (the biggest one) if overall memory reaches specified
limit. This metric allows us to watch number of killed workers.
|
| | | |
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Extract acme double to helper
Create ACME challanges for pages domains
* Create order & challange through API
* save them to database
* request challenge validation
We're saving order and challenge as one entity,
that wouldn't be correct if we would order certificates for
several domains simultaneously, but we always order certificate
per domain
Add controller for processing acme challenges redirected from pages
Don't save acme challenge url - we don't use it
Validate acme challenge attributes
Encrypt private_key in acme orders
|
| |
|
|
|
|
| |
This allows the BetterErrors REPL to be available
when your GitLab instance is listening on
something _other_ than localhost.
|
| |
|
|
|
| |
As we have a central domain for auto merge process today,
we should use a single worker for any auto merge process.
|
| |\ |
|
| | |
| |
| |
| |
| |
| | |
Gitlab::HTTP now resolves the hostname only once, verifies the IP is not
blocked, and then uses the same IP to perform the actual request, while
passing the original hostname in the `Host` header and SSL SNI field.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
We have one auto merge strategy today - Merge When Pipeline
Succeeds.
In order to add more strategies for Merge Train feature,
we abstract the architecture to be more extensible.
Removed arguments
Fix spec
|
| |\ \
| | |
| | |
| | |
| | | |
Move some project routes under - scope
See merge request gitlab-org/gitlab-ce!28830
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Affected project routes are:
* services
* boards
* releases
* forks
* group_links
* import
* avatar
* labels
* milestones
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | | |
| | |
| | |
| | |
| | |
| | | |
- Select notification email by walking up group/subgroup path
- Add settings UI to set group email notification address
- Add tests
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This sets up all the basics for importing Phabricator tasks into
GitLab issues.
To import all tasks from a Phabricator instance into GitLab, we'll
import all of them into a new project that will have its repository
disabled.
The import is hooked into a regular ProjectImport setup, but similar
to the GitHub parallel importer takes care of all the imports itself.
In this iteration, we're importing each page of tasks in a separate
sidekiq job.
The first thing we do when requesting a new page of tasks is schedule
the next page to be imported. But to avoid deadlocks, we only allow a
single job per worker type to run at the same time.
For now we're only importing basic Issue information, this should be
extended to richer information.
|
| | | |
| | |
| | |
| | | |
It takes a lot of lines to move a script
|
| | | | |
|
| |/ /
| |
| |
| |
| |
| |
| | |
It assures that requests are aborted after 60 seconds, otherwise
an exception is raised. This exception is logged by Sentry, also
there is a Prometheus counter for measuring number of requests in each
state.
|
| |/
|
|
|
| |
This sampler gathers Puma-specific metrics which can be used by
Prometheus then.
|
| |\
| |
| |
| |
| | |
Move more project routes under /-/ scope
See merge request gitlab-org/gitlab-ce!28717
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Affected routes are:
* autocomplete_sources
* project_members
* deploy_keys
* deploy_tokens
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | |
| |
| |
| | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Storing this key in secrets.yml was a bad idea,
it would require users using HA setups to manually
replicate secrets across nodes during update,
it also needed support from omnibus package
* Revert "Generate Let's Encrypt private key"
This reverts commit 444959bfa0b79e827a2a1a7a314acac19390f976.
* Add Let's Encrypt private key to settings
as encrypted attribute
* Generate Let's Encrypt private key
in database migration
|
