| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| |\
| |
| |
| |
| | |
Add group ful path to project's shared_with_groups
See merge request gitlab-org/gitlab-ce!24052
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | | |
Allow setting of feature gates per project
See merge request gitlab-org/gitlab-ce!24184
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
For features the feature gates are sometimes projects, not groups or
users. For example for git object pools:
https://gitlab.com/gitlab-com/gl-infra/infrastructure/issues/5872
This commit allows for setting feature group gates based on projects, by its
path as that seems most convenient.
|
| | | | |
|
| | |/
|/| |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
'master'
Improves restriction of multiple Kubernetes clusters via API
Closes #56110
See merge request gitlab-org/gitlab-ce!24251
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Modifies authorize! method to accept a third param, and then use it in
combination with 'add_cluster' policy to appropriately restrict adding
multiple clusters
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/56110
|
| |/ /
| |
| |
| |
| |
| | |
We introduced releases_page feature flag.
Given this feature is deemed stable, we should remove
this flag before 19th.
|
| | | |
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Refactor artifact api endpoint
Closes #55445
See merge request gitlab-org/gitlab-ce!23582
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
`project.latest_successful_builds_for(ref)` is being used to find a
single job all the time. This results into us having to call `find_by`
inside of the controller which violates our CodeReuse/ActiveRecord
rubocop rule.
Refactor `project.latest_successful_builds_for(ref)` to
`project.latest_successful_build_for(job_name, ref)` which will execute
the `find_by` inside of the model.
Also create `project.latest_successful_build_for!(job_name, ref)` which
raises an exception instead of returning nil.
|
| |\ \
| | |
| | |
| | |
| | | |
Switch use of Rack::Request to ActionDispatch::Request
See merge request gitlab-org/gitlab-ce!24199
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
As mentioned in
https://gitlab.com/gitlab-org/gitlab-ee/issues/9035#note_129093444,
Rails 5 switched ActionDispatch::Request so that it no longer inherits
Rack::Request directly. A middleware that uses Rack::Request to
read the environment may see stale request parameters if
another middleware modifies the environment via ActionDispatch::Request.
To be safe, we should be using ActionDispatch::Request everywhere.
|
| |\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
Import issues from CSV
Closes #49231
See merge request gitlab-org/gitlab-ce!23532
|
| | |/
| |
| |
| | |
Also changes old calls to the service
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Allow to include another project files
Closes #53903
See merge request gitlab-org/gitlab-ce!24101
|
| | | |
| | |
| | |
| | | |
This adds `project:, file:, ref:` specification support.
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Add tests for the API and add a couple of tests
Add
revert
revert
|
| | |/
|/|
| |
| | |
Authorize against release not project
|
| |\ \
| | |
| | |
| | |
| | |
| | |
| | | |
Add API Support for Kubernetes integration
Closes #40473
See merge request gitlab-org/gitlab-ce!23922
|
| | | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Adds the following initial CRUD endpoints for Clusters API:
- GET list of clusters
- GET specific cluster
- POST add existing cluster (mimic of "Add cluster")
- PUT update cluser
- DELETE destroy cluster
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/40473
|
| |\ \ \
| |_|/
|/| |
| | |
| | |
| | |
| | | |
Expose `CI_API_V4_URL` CI/CD variable
Closes #54621
See merge request gitlab-org/gitlab-ce!23936
|
| | | | |
|
| | | | |
|
| | | |
| | |
| | |
| | |
| | | |
This commits adds a new class that is supposed to represent Grape API
version, like `v3` or `v4`.
|
| | |/ |
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fix coding style
Improve coding style
Decouple UPDATE and DELETE operations of asset links
Rename links_attributes to assets:links
Rename exposed param and updated spec
|
| |/
|
|
|
|
| |
- Add Releases::Links model
- Expose it in release API
- Add integration tests
|
| |\
| |
| |
| |
| |
| |
| | |
Handle 'git push -o ci.skip'
Closes #18667
See merge request gitlab-org/gitlab-ce!15643
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
gitlab-org/gitlab-shell!166 added support for collecting push options
from the environment, and passing them along to the
/internal/post_receive API endpoint.
This change handles the new push_options JSON element in the payload,
and passes them on through to the GitPushService and GitTagPushService
services.
Futhermore, it adds support for the first push option, ci.skip. With
this change, one can use 'git push -o ci.skip' to skip CI pipe
execution. Note that the pipeline is still created, but in the "skipped"
state, just like with the 'ci skip' commit message text.
Implements #18667
|
| |\ \
| |/
|/| |
|
| | |\
| | |
| | |
| | |
| | | |
[master] Guest users have access to all Job information via the API
See merge request gitlab/gitlabhq!2717
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| |\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fixed content-disposition in blob and files API endpoint
Closes #55781
See merge request gitlab-org/gitlab-ce!24078
|
| | | | | |
|
| | | | |
| | | |
| | | |
| | | |
| | | | |
Add spec for all release API - GET, POST, PUT, DELETE.
Also, fixes some minior bugs.
|
| | | | |
| | | |
| | | |
| | | | |
Introduce DELETE endpoint in Release API
|
| | | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
CreateReleaseService and UpdateReleaseService now takes all the release
attributes as constructor parameters. This will simplify attribute
expansion
|
| | | | | |
|
| | | | | |
|
| | |/ /
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This commit introduces Releases API under /api/v4/projects/:id/releases
* We are introducing release policies at project level.
* We are deprecating releases changes from tags, both api and web
interface.
* Tags::CreateService no longer create a release
This feature is controlled by :releases_page feature flag
|
| |/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
47d4890d changed the order of pagination so that the full list of
branches would be passed to Gitaly to determine which ones had been
merged, but this operation can timeout for large repositories with
many branches. We only need to determine whether the found branches have
been merged, so limit the scan to those.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/55724
|
| | | |
|
| |/
|
|
|
|
| |
- we now use the hierarchy class also for epics
- also rename supports_nested_groups? into supports_nested_objects?
- move it to a concern
|
| |
|
|
|
|
|
|
|
|
|
|
| |
We're filtering the events using `Event#visible_to_user?`.
At most we're loading 100 events at once.
Pagination is also dealt with in the finder, but the resulting array
is wrapped in a `Kaminari.paginate_array` so the API's pagination
helpers keep working. We're passing the total count into that
paginatable array, which would include confidential events. But we're
not disclosing anything.
|
