| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
Before this commit we redefined properties for supported events on each
new instance of ChatNotificationService during "runtime".
This commit defines the properties only once during "compile time".
|
| |
|
|
| |
Wrong format on MS Teams integration push events with multi line commit messages
|
| |\
| |
| |
| |
| | |
Avoid calling freeze on already frozen strings in app/models
See merge request gitlab-org/gitlab-ce!32499
|
| | | |
|
| |\ \
| |/
|/|
| |
| | |
Improve chatops help output
See merge request gitlab-org/gitlab-ce!32208
|
| | |
| |
| |
| |
| |
| |
| | |
This improves the output produced when running an unknown command,
running the "help" command, and when trying to run a command you are not
allowed to run. The new help output includes links to the project of the
chatops integration, and a link to the chatops documentation.
|
| |\ \
| |/
|/|
| |
| | |
Fix DNS rebind vulnerability for JIRA integration
See merge request gitlab/gitlabhq!3266
|
| | |
| |
| |
| |
| | |
Uses Gitlab::HTTP for JIRA requests instead of Net::Http.
Gitlab::Http comes with some built in SSRF protections.
|
| | |
| |
| |
| |
| |
| | |
- Adds UI to configure in group and project settings
- Removes notification configuration for users when
disabled at group or project level
|
| |\ \
| | |
| | |
| | | |
'dev/security-2873-restrict-slash-commands-to-users-who-can-log-in'
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This commit fixes the project avatar images that are rendered in the
footer of Slack pipeline notifications. Previously, the image URLs
provided to Slack were relative URLs; now they are absolute.
|
| | | |
| | |
| | |
| | |
| | |
| | | |
Creating new records has been disabled, and all
existing records been migrated to clusters as of
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/28534
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Kubernetes deployments on new clusters will now have
a separate namespace per project environment, instead
of sharing a single namespace for the project.
Behaviour of existing clusters is unchanged.
All new functionality is controlled by the
:kubernetes_namespace_per_environment feature flag,
which is safe to enable/disable at any time.
|
| | |/
|/|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- Closes #60024
- Change PrometheusClient.new to accept a base url instead of an
already created RestClient
- Use Gitlab::HTTP in PrometheusClient instead of creating RestClient
in PrometheusService
- Move http_options from PrometheusService to
PrometheusClient (follow_redirects: false)
- ensure that base urls don't have the trailing slash
- Created a `PrometheusClient#url` method that might not be strictly
required
- Change rescued exceptions from RestClient::* to
HTTParty::ResponseError where possible and StandardError for the
rest
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Make pipeline failure Slack notifications prettier and more informative
Closes #32495
See merge request gitlab-org/gitlab-ce!27683
|
| | | |
| | |
| | |
| | |
| | |
| | | |
This commit adds some formatting to the Slack notifications for pipeline
statuses, as well as adds information about the stage and jobs
that failed in the case of pipeline failure.
|
| |/ / |
|
| |/
|
|
| |
Applies to issues_url and new_issue_url
|
| | |
|
| |
|
|
| |
Updates changed method names and fixes spec failures
|
| |
|
|
|
|
| |
Some services can raise OpenSSL::X509::CertificateError due
to an invalid SSL certificates, with OpenSSL::OpenSSLError
we can handle these errors.
|
| |
|
|
|
| |
Now that KubernetesService can no longer be a DeploymentPlatform we can
remove all kubernetes client code and KubernetesService edge cases.
|
| |
|
|
|
| |
- instead of using properties
- backward compatibility has to be kept for now
|
| |
|
|
|
|
| |
https://community.atlassian.com/t5/Jira-questions/Is-it-quot-JIRA-quot-or-quot-Jira-quot/qaq-p/681163
Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>
|
| |
|
|
|
|
| |
DroneCI and TeamCity shared the same validations methods
on the data received. These validations were extracted
into a concern
|
| |
|
|
|
|
|
|
|
|
|
| |
This is a take over from a community contribution:
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/20990
Skip TeamCity push event when related to branch delete
Support merge request events for TeamCity service.
Add checkbox for merge request triggers in the TeamCity
configuration page.
|
| | |
|
| |
|
|
|
|
|
|
| |
We are deprecating this service in favor of instance wide clusters.
Therefore we removed some code that is not anymore needed for a
readonly cluster and also we added some flags to allow for this
deprecation. These flags are to be removed in the next release when
we finally completelly remove KubernetesService.
|
| |
|
|
|
| |
- create tables for storing issue trackers properties
- add model and basic logic & spec
|
| |
|
|
|
| |
Relates to #42595.
Fixes #62661.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When Kubernetes clusters were originally built they could only
exist at the project level, and so there was logic included
that assumed there would only ever be a single Kubernetes
namespace per cluster. We now support clusters at the group
and instance level, which allows multiple namespaces.
This change consolidates various project-specific fallbacks to
generate namespaces, and hands all responsibility to the
Clusters::KubernetesNamespace model. There is now no concept of
a single namespace for a Clusters::Platforms::Kubernetes; to
retrieve a namespace a project must now be supplied in all cases.
This simplifies upcoming work to use a separate Kubernetes
namespace per project environment (instead of a namespace
per project).
|
| | |
|
| |
|
|
|
| |
Include link to user and commit title.
Rearrange text
|
