| Age | Commit message (Collapse) | Author |
|---|
|
Previously this behaviour was only available to group
and instance-level clusters, as some project clusters
relied on Kubernetes credentials being passed through
to the runner instead of having their resources managed
by GitLab (which is not available when using JIT). These
clusters have been migrated to unmanaged, so resources
can be created on demand for the remaining managed clusters.
|
|
Expose currently supported events properly on services API
Closes #56737
See merge request gitlab-org/gitlab-ce!29736
|
|
Refresh service_account_token for kubernetes_namespaces
See merge request gitlab-org/gitlab-ce!29657
|
|
Add collapsible sections to job log
See merge request gitlab-org/gitlab-ce!28642
|
|
|
|
This backports all EE schema changes to CE, including EE migrations,
ensuring both use the same schema.
== Updated tests
A spec related to ghost and support bot users had to be modified to make
it pass. The spec in question assumes that the "support_bot" column
exists when defining the spec. In the single codebase setup this is not
the case, as the column is backported in a later migration. Any attempt
to use a different schema version or use of "around" blocks to
conditionally disable specs won't help, as reverting the backport
migration would also drop the "support_bot" column. Removing the
"support_bot" tests entirely appears to be the only solution.
We also need to update some foreign key tests now that we have
backported the EE columns. Fortunately, these changes are very minor.
== Backporting migrations
This commit moves EE specific migrations (except those for the Geo
tracking database) and related files to CE, and also removes any traces
of the ee/db directory.
Some migrations had to be modified or removed, as they no longer work
with the schema being backported. These migrations were all quite old,
so we opted for removing them where modifying them would take too much
time and effort.
Some old migrations were modified in EE, while also existing in CE. In
these cases we took the EE code, and in one case removed them entirely.
It's not worth spending time trying to merge these changes somehow as we
plan to remove old migrations around the release of 12.0, see
https://gitlab.com/gitlab-org/gitlab-ce/issues/59177 for more details.
|
|
This is necessary for backporting the EE schema to ensure backported
foreign keys use the same key names.
|
|
|
|
|
|
Fix plan stage query and the way it is displayed
|
|
This brings the API permissions in line with the UI permissions
|
|
return boolean from Pipeline::Expression::Lexeme::Matches#evaluate
See merge request gitlab-org/gitlab-ce!29717
|
|
Fix inability to set visibility_level on project via API
Closes #63158
See merge request gitlab-org/gitlab-ce!29578
|
|
|
|
|
|
Expose comments on Noteables in GraphQL
Closes #62825
See merge request gitlab-org/gitlab-ce!29212
|
|
|
|
|
|
https://gitlab.com/gitlab-org/gitlab-ce into generate-spans-for-sections
|
|
|
|
Consider the scenario:
1. The default visibility level is set to internal
2. A user attempts to create a private project within a private group
Previously this would always fail because default_value_for would
overwrite the private visibility setting, no matter what
visibility_level were specified. This was happening because
default_value_for was confused by the default value of 0 specified by
the database schema.
default_value_for attempts to assign the default value in the block by
checking whether the attribute has changed. The problem is that since
the default value by the database was 0, and the user requested 0, this
appeared as though no changes were made. As a result, default_value_for
would always overwrite the user's preference.
To fix this, we remove the use of default_value_for and only set the
visibility level to the default application setting when no preference
has been given at creation time.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/63158
|
|
This exposes `Note`s on Issues & MergeRequests using a
`Types::Notes::NoteableType` in GraphQL.
Exposing notes on a new type can be done by implementing the
`NoteableType` interface on the type. The presented object should
be a `Noteable`.
|
|
|
|
See http://asciidoctor.org/docs/user-manual/#include-directive
|
|
Don't import pull request comments from Gitea repos
Closes #63071
See merge request gitlab-org/gitlab-ce!29521
|
|
There seems to be several examples where service_account_token is blank
even in GitLab.com newly created kubernetes_namespaces . We have not
figured out why they are blank but this should hopefully fix some issues
similar to https://gitlab.com/gitlab-org/gitlab-ce/issues/55362
|
|
|
|
Opts to cache a full list of cached dashboards
to better manage removing items from the cache.
This also allows dashboards to be stored in the
cache that don't necessarily correspond to a
single dashboard yml.
|
|
|
|
Backport changes from 'Partially revert d9cb907c: "Avoid loading objects from DB in ES results"'
See merge request gitlab-org/gitlab-ce!29597
|
|
Bring propagated SAST ENV vars into parity with docs
See merge request gitlab-org/gitlab-ce!29564
|
|
This reverts commit d9cb907c3e987363065136bafb2156e86bc5de26.
|
|
'61157-reviewer-roulette-shouldn-t-include-the-author-as-a-possibility' into 'master'
Review roulette excludes mr_author
Closes #61157
See merge request gitlab-org/gitlab-ce!28886
|
|
Excludes MR author from gitlab_ui and single_codebase Review roulette
results.
|
|
|
|
Bump omniauth_openid_connect to 0.3.1
See merge request gitlab-org/gitlab-ce!29387
|
|
Moved RackTimeout observer to a different location and ignore transition states
See merge request gitlab-org/gitlab-ce!29214
|
|
|
|
|
|
Expose default_git_depth via project API
Closes #62908
See merge request gitlab-org/gitlab-ce!29353
|
|
There is no reason to monitor transition states so we ignore
ready and active states. We can get ratio of completed vs failed
requests from final states.
|
|
Because there will be similar observer for PumaWorkerKiller,
it makes sense to keep both on better place.
|
|
Rename `BatchCommitLoader` to `BatchLfsOidLoader`
See merge request gitlab-org/gitlab-ce!29487
|
|
* master: (784 commits)
Update Serverless.gitlab-ci-yml to fix lint warning
Document when milestones and labels links are missing
Update git object deduplication overview
Apply tooltip on truncated commit title
Add link to import video
Update merge options for auto merge strategies
Update note style in various docs
Add link to Auto DevOps demo video
Add link to Groups video
Remove glossary content and make necessary doc edits to clarify terms
Docs for Gitlab Runner docker use of private registries
Metrics reports documentation is incomplete
Update issues/index.md with note on label priority sorting
API issues - minor cleanup of permission check
Fix gl_dropdown scrolling to top on assignee click
Final doc review
Remove docs for a removed ES rake task
Fixed markdown link in Docker compose note
Documented the Admin Area's *Groups* page
Docs: Updating issue data and actions doc
...
|
|
Enable Get and Update of ci_default_git_depth for
Project API.
Renaming Project#default_git_depth to :ci_default_git_depth
to give more context through the API usage.
Add API documentation
|
|
|
|
The Gitea API does not provide the following API endpoint for pull request
comments:
/api/v1/repos/{owner}/{repo}/pulls/comments
When the importer attempts to request this endpoint it receives a '404
Not Found' error which causes the import to fail. By skipping any
attempts to import pull requests comments from Gitea we can ensure that
the import can complete successfully.
|
|
Adds `set_issue_updated_at` similar to `set_issue_created_at`
permission and cleans up the related permission check in issues
API.
|
|
|
|
Since we're not actually loading commits in that loader, but we're
loading blobs with LFS oids in batch and returning only the oids.
|
