| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
Show disabled mirrors with a badge so that they
can be deleted by project owners.
|
| |
|
|
|
|
|
|
|
| |
Add env_var and file as supported types for CI variables. Variables of
type file expose to users existing gitlab-runner behaviour - save
variable value into a temp file and set the path to this file in an ENV
var named after the variable key.
Resolves https://gitlab.com/gitlab-org/gitlab-ce/issues/46806.
|
| |\
| |
| |
| |
| |
| |
| | |
Remove cleaned up OIDs from database and cache
Closes #30093
See merge request gitlab-org/gitlab-ce!26555
|
| | | |
|
| |/
|
|
| |
Refactor
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is step one of resolving
https://gitlab.com/gitlab-org/gitlab-ce/issues/56838.
Here is what changed:
- Revert the security fix from bdee9e8412d.
- Do not leak repository information (tag name, commit) to guests in API
responses.
- Do not include links to source code in API responses for users that do
not have download_code access.
- Show Releases in sidebar for guests.
- Do not display links to source code under Assets for users that do not
have download_code access.
GET ':id/releases/:tag_name' still do not allow guests to access
releases. This is to prevent guessing tag existence.
|
| |
|
|
|
|
|
|
| |
When this option is enabled, GitLab will create namespaces and service
accounts as usual. When disabled, GitLab wont create any project
specific kubernetes resources
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56557
|
| |
|
|
|
|
|
|
|
|
| |
- 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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new two-step Gitaly `Rebase` RPC yields the rebase commit SHA to the
client before proceeding with the rebase.
This avoids an issue where the rebase commit SHA was returned when the
RPC had fully completed, and in some cases this would be after the Rails
`post_receive` worker services had already run. In these situations,
the merge request did not yet have its rebase_commit_sha attribute set
introducing the possibility for bugs (such as previous approvals being
reset).
https://gitlab.com/gitlab-org/gitlab-ee/issues/5966
|
| |
|
|
|
| |
Include link to user and commit title.
Rearrange text
|
| |
|
|
|
| |
This new field will allow to keep track of the storage used by the
packages features, it provides also aggregation at namespace level.
|
| |\
| |
| |
| |
| | |
[CE] Remove deprecated usage of `attribute_changed?`
See merge request gitlab-org/gitlab-ce!27577
|
| | |
| |
| |
| | |
Prepares us for upgrade to Rails 5.2
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
'53064-bypassing-pipeline-jobs-by-canceling-the-pipeline-and-manually-running-later-jobs' into 'master'
Disable retrying cancelled jobs
Closes #53064
See merge request gitlab-org/gitlab-ce!27503
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Specs that test canceled jobs now
- expect them not to be retryable or playable
- expect them not to show retry buttons
Specs that test retryability now
- use failed status instead of canceled status
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Allow a member to have an access level equal to parent group
Closes gitlab-ee#11323
See merge request gitlab-org/gitlab-ce!27913
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Suppose you have this configuration:
1. Subgroup `hello/world`
2. Subgroup `hello/mergers`.
3. Project `hello/world/my-project` has invited group `hello/world` to
access protected branches.
4. The rule allows the group to merge but no one can push.
5. User `newuser` has Owner access to the parent group `hello`.
Previously, there was no way for the user `newuser` to be added to the
`hello/mergers` group since the validation only allowed a user to be
added at a higher access level.
Since membership in a subgroup confers certain access rights, such as
being able to merge or push code to protected branches, we have to
loosen the validation and allow someone to be added at an equal level
granted by the parent group.
Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/11323
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Updates the EnvironmentController#metrics_dashboard endpoint
to support a "dashboard" param, which can be used to specify
the filepath of a dashboard configuration from a project
repository. Dashboard configurations are expected to be
stored in .gitlab/dashboards/.
Updates dashboard post-processing steps to exclude custom
metrics, which should only display on the system dashboard.
|
| |\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
CE Backport: Add project level config for merge train
See merge request gitlab-org/gitlab-ce!27819
|
| | | | |
| | | |
| | | |
| | | | |
We add the option and expose the parameter for frontend work
|
| |/ / /
| | |
| | |
| | |
| | |
| | |
| | | |
Due to the nature of pipelines for merge requests, deployments.ref can
be a merge request ref instead of a branch name.
We support the environment auto-stop hook for this case
|
| | | |
| | |
| | |
| | |
| | | |
Domain will be removed by verification worker after 1 week
of being disabled
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
In order to not miss any errors since we are not checking the return
value of update
|
| | | |
| | |
| | |
| | | |
Basically does the reverse of after_transition to :installed.
|
| | | |
| | |
| | |
| | | |
Add specs
|
| | |/
|/|
| |
| |
| |
| |
| |
| | |
Only prometheus can be uninstalled atm, the rest will be dealt with
later.
Presumption is that new application types will have uninstallation
implmemented at the same time.
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Make `CI_COMMIT_REF_NAME` and `SLUG` variable idempotent
Closes #60822
See merge request gitlab-org/gitlab-ce!27663
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | | |
With Pipelines for Merge Requests feature, users cannout keep using
$CI_COMMIT_REF_NAME and _SLUG predefined variables for dynamic
environments. We fix this problem by explicitly looking at the source
ref.
|
| |\ \ \
| | | |
| | | |
| | | |
| | | | |
Use keyword args for databuilder push
See merge request gitlab-org/gitlab-ce!24088
|
| | | | | |
|
| |\ \ \ \ |
|
| | |\ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Port changes for design management to CE
See merge request gitlab-org/gitlab-ce!27555
|
| | | | |/ /
| | |/| |
| | | | |
| | | | |
| | | | |
| | | | | |
This ports the changes from
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10462/
to CE
|
| | |/ / /
| | | |
| | | |
| | | | |
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/27687
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Store Let's Encrypt account email in application settings
Also add explicit terms of service consent
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
This enables sending a chat message to Slack or Mattermost
upon a successful, failed, or canceled deployment
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This new table will be used to store the external_dashboard_url which
allows users to add a link to their external dashboards (ex Grafana)
to the Metrics dashboard.
|
| | |\ \ \
| | |/ /
| |/| |
| | | |
| | | | |
Use constants for asserstion for helm chart test
See merge request gitlab-org/gitlab-ce!27629
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
We are duplicating the value from the constant
`Clusters::Applications::Runner::VERSION` inside of the tests which
results into developers having to update the tests as well when they
want to upgrade the Helm chart used for GitLab Runner
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Add ApplicationRecord#safe_ensure_unique method
See merge request gitlab/gitlabhq!3054
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Port of https://dev.gitlab.org/gitlab/gitlab-ee/merge_requests/866
to CE excluding the migration and service changes as they don't
apply to CE.
|
| |\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
Stop sending emails to users who can't read commit
See merge request gitlab/gitlabhq!3060
|
| | |/ / /
| | | |
| | | |
| | | |
| | | |
| | | | |
This is to ensure that only users will be able receive
an email if they can read a commit from the repository
even if they are watching the activity of it.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Ensure that we only request blobs in one batch
Closes #60829
See merge request gitlab-org/gitlab-ce!27625
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Blob.lazy adds a blob to a batch to load at a later point, using the
BatchLoader library. Whenever any lazy blob's attributes are accessed,
all lazy blobs requested to that point will be loaded.
BatchLoader, the library we use for this, should only request items in a
batch once. That is, if we have these batches:
1. a, b, c
2. d, e, f
Then a, b, and c should only be requested in the first batch. But if you
modify the list of items in the batch, then the second batch will
request a, b, c, d, e, f, which is almost certainly not what we want!
https://github.com/exAspArk/batch-loader/issues/44 is the upstream issue
for this, but we can also solve this in our application by not modifying
the arguments we're using inside a BatchLoader batch.
|
| | | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Updates the gitaly client to use path_bytes field instead of the
deprecated path field in list_last_commits_for_tree_response.
Also adds a test to guard against non-utf8 path data
|
| | |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Inside a wiki, when we show the sidebar or browse to the `pages`,
all page contents are retrieved from Gitaly and that is a waste
of resources, since no content from that pages are going to be
showed.
This MR introduces the method `ProjectWiki#list_pages`,
which uses new wiki_list_pages RPC call to retrieve
pages without content
Also in the `WikisController` we're using the method to show
pages in the sidebar and also on the `pages` page.
|
| |\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Add CI variable CI_REF_PROTECTED
See merge request gitlab-org/gitlab-ce!26716
|
| | | | | | |
|
