| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
Creates a new filename to register auth logs.
This change should allow SRE's queries to make better queries
through logging infrastructure.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/54528
|
|\
| |
| |
| |
| |
| |
| | |
Create a unified script to run Jest & Karma tests
Closes #58869
See merge request gitlab-org/gitlab-ce!27239
|
| |
| |
| |
| |
| |
| |
| | |
This is already supported karma feature, but it wasn't respected
because our wrapper threw an error no matter what.
https://github.com/karma-runner/karma/blob/fe9a1dd13b5eb3969f9e08acbce020e2a382fd9e/lib/cli.js#L201
|
|\ \
| | |
| | |
| | |
| | | |
Move some project routes under /-/ scope
See merge request gitlab-org/gitlab-ce!28435
|
| | |
| | |
| | |
| | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | | |
For settings, branches and tags
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | |
| | |
| | |
| | | |
Signed-off-by: Utkarsh Gupta <guptautkarsh2102@gmail.com>
|
|/ / |
|
| |
| |
| |
| | |
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Part of adding Let's Encrypt certificates for pages domains
Add acme-client gem
Client is being initialized by private key stored in secrets.yml
Let's Encrypt account is being created lazily.
If it's already created, Acme::Client just gets account_kid by
calling new_account method
Make Let's Encrypt client an instance
Wrap order and challenge classes
|
|/ |
|
|\
| |
| |
| |
| | |
Expain usage of `artifacts_server` in `gitlab.yml`
See merge request gitlab-org/gitlab-ce!28230
|
| |
| |
| |
| |
| |
| | |
Add comment to clarify intended usage of `artifacts_server`.
Related to https://gitlab.com/gitlab-org/gitlab-ce/issues/49475.
|
|\ \
| | |
| | |
| | |
| | | |
Add EE fixtures to SeedFu fixture paths
See merge request gitlab-org/gitlab-ce!28241
|
| |/
| |
| |
| | |
Signed-off-by: Balasankar "Balu" C <balasankar@gitlab.com>
|
|/
|
|
| |
[ci skip]
|
| |
|
|
|
|
|
|
| |
Remove puts
Remove puts
|
|\
| |
| |
| |
| | |
Generate EE-specific JavaScript fixtures into ee/ directory (CE-backport)
See merge request gitlab-org/gitlab-ce!28032
|
| |
| |
| |
| | |
(cherry picked from commit 7cde57bf7367bce130a2e7f149c8dafd362de3f8)
|
|\ \
| | |
| | |
| | |
| | | |
Instance level k8s clusters
See merge request gitlab-org/gitlab-ce!27196
|
| | |
| | |
| | |
| | |
| | | |
Instance level clusters were already mostly supported, this change adds
admin area controllers for cluster CRUD
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
If the UI sends a string value for lock_version (e.g. "0"), then the
previous monkey patch did not properly handle that properly. This
commit casts the value to an integer to determine whether to look for
NULL lock_versions.
For merge requests, GitLab sends a POST request to
`namespace/project/merge_requests/:iid` with the
`merge_request[lock_version]` parameter with a string `0`. The string
value comes from the form field, which explains why
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28145 wasn't
sufficient.
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
|
| |
Rails 5.1's `exec_no_cache` doesn't call `async_exec` any more, but
`exec_params`: https://github.com/rails/rails/pull/33188
This means that the DB summary in the performance bar was wrong. The
individual query details were still correct (we subscribe to
ActiveRecord events for those).
We can remove this once the upstream PR to peek-pg is in a release and
we update to use that release.
|
|
|
|
|
|
|
|
|
|
| |
- Adds an endpoint on PipelinesController
- Adds a service that iterates over every build in a stage and
plays it.
- Includes 'play_manual' details on EntitySerializer
- Builds a new Stage state: PlayManual. An stage can take this status if
it has manual builds or an skipped, scheduled or manual status
- Includes FE modifications and specs
|
| |
|