| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
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
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This variable shows if the branch the runner is executing is protected
or not.
References: #50909
|
|\ \ \ \
| |_|/ /
|/| | |
| | | |
| | | |
| | | |
| | | | |
Always use internal ID tables in development and production
Closes #60718
See merge request gitlab-org/gitlab-ce!27544
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
To avoid quiet failures that cause consistency errors in the database,
we should now assume that the internal_ids table is available since
we've had this table for close to a year.
For tests that have migrations, we make this check thread-safe via
SafeRequestStore.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/60718
|
|/ / /
| | |
| | |
| | | |
Model.new.attributes now also returns encrypted attributes.
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Update GitLab Runner Helm Chart to 0.4.0/11.10.0
See merge request gitlab-org/gitlab-ce!27508
|
| | | | |
|
| | | | |
|
|/ / /
| | |
| | |
| | | |
Refactor existing tests as a shared example
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Return group information on Project endpoint
Closes #39858
See merge request gitlab-org/gitlab-ce!27427
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Namespace now return avatar_url and web_url
- NamespaceBasic entity was modified to include avatar_url and web_url,
information is fetched differently depending if the Namespace is a user
or a group
Includes documentation changes
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/39858
|
|/ / / |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
Backport metrics report type
See merge request gitlab-org/gitlab-ce!26798
|
| |/ /
| | |
| | |
| | |
| | | |
This backports the changes from
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/10452
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Rewind iid on pipelines
Closes #59362
See merge request gitlab-org/gitlab-ce!26490
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
If no pipeline is created we currently have IID gap.
This is due to fact that we generate IID not on save,
but rather ahead of time. This results, us,
losing IIDs.
|
|/ / /
| | |
| | |
| | | |
with expired artifacts
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
If a page has the same name as a directory
the WikiPage#group_by_directory method can have
a wrong behaviour
This commit fixes it
|
| | |
|