Age | Commit message (Collapse) | Author |
|
|
|
'security-11-7'
[11.7] Validate bundle files before unpacking them
See merge request gitlab/gitlabhq!2773
(cherry picked from commit 3f631ca5d24533e2d90617e1fa0a510268c35b1c)
74f447d1 Validate bundle files before unpacking them
|
|
Fix no avatar not showing in user selection box
Closes #56268
See merge request gitlab-org/gitlab-ce!24346
(cherry picked from commit 8285205815ccdb25238fcae1c1e91063a46f19b0)
2265ce34 Fix no avatar not showing in user selection box
|
|
Remove `releases_page` feature flag
Closes #56072
See merge request gitlab-org/gitlab-ce!24215
(cherry picked from commit b682a6f8981d303e7ee7ecc4273768ee6ed66864)
9b823af4 Remove releases_page feature flag
|
|
Revert "Merge branch '3062-improve-project-cache' into 'master'"
Closes #56103
See merge request gitlab-org/gitlab-ce!24244
(cherry picked from commit a0aca3ac3a4ef56429104c27cd03ce00dcaeafce)
e884795e Revert "Merge branch '3062-improve-project-cache' into 'master'"
|
|
Import issues from CSV
Closes #49231
See merge request gitlab-org/gitlab-ce!23532
|
|
|
|
Fix Bitbucket Server import only including first 25 pull requests
Closes #55914
See merge request gitlab-org/gitlab-ce!24178
|
|
Allow to include another project files
Closes #53903
See merge request gitlab-org/gitlab-ce!24101
|
|
This adds `project:, file:, ref:` specification support.
|
|
The change to paginate repos in
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/22825 caused the
paginator to stop after 25 pull requests because the limit was set to 25
if none was defined. To fix this, we should only stop if the limit has
actually been set and use the limit parameter to determine the maximum
number of items to process per page.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/55914
|
|
Add tests for the API and add a couple of tests
Add
revert
revert
|
|
Authorize against release not project
|
|
Load whole file in memory to simplify code
|
|
Also changes old calls to the service
|
|
Use BuildMetadata to store build configuration in JSONB form
See merge request gitlab-org/gitlab-ce!21499
|
|
Fix multipart attachments not uploading
Closes gitlab-ee#9035
See merge request gitlab-org/gitlab-ce!24170
|
|
Add API Support for Kubernetes integration
Closes #40473
See merge request gitlab-org/gitlab-ce!23922
|
|
Mixing and matching the use of Rack::Request and ActionDispatch::Request
in Rails 5 is bad, particularly if you have middleware that
manipulates or accesses environment variables.
`Gitlab::Middleware::Multipart` attempts to rewrite request parameters
to the proper values (e.g. replacing `data_file` with
`UploadedFile`). It does this by calling `Rack::Request#update_params`,
which essentially updates `env['rack.request.form_hash']`.
By changing to `ActionDispatch::Request`, the Go middleware was causing
the request parameters to be stored inside
`env['action_dispatch.request.request_parameters']`. Later calls to
`Rack::Request#update_params` would not have any effect because it would
attempt to update `env['rack.request.form_has']` instead of
`env['action_dispatch.request.request_parameters']`. As a result, the
controller still saw the old parameters.
Since the Go middleware appears to be using `ActionDispatch::Request`
for authorization methods, we can switch the multipart middleware to
use it too.
Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/9035
|
|
'4553-geo-hashed-storage-migration-failure-does-not-log-to-sentry-or-geo-log-well-ee' into 'master'
Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8926
See merge request gitlab-org/gitlab-ce!24129
|
|
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
|
|
Backport of https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8926
|
|
Don't ignore conflicts in db/schema.rb
See merge request gitlab-org/gitlab-ce!24152
|
|
Expose `CI_API_V4_URL` CI/CD variable
Closes #54621
See merge request gitlab-org/gitlab-ce!23936
|
|
Include templates
Closes #53445
See merge request gitlab-org/gitlab-ce!23495
|
|
These are data columns that store runtime configuration
of build needed to execute it on runner and within pipeline.
The definition of this data is that once used, and when no longer
needed (due to retry capability) they can be freely removed.
They use `jsonb` on PostgreSQL, and `text` on MySQL (due to lacking
support for json datatype on old enough version).
|
|
It's not entirely clear to me why we were ignoring db/schema.rb in the
first place, but this should not be done now that we merge CE into EE
automatically. Doing so can lead to changes being thrown away in the
event of a conflict, which can then lead to EE pipelines failing.
|
|
Don't ingore the `gitlab.pot` in ee_compat_check
See merge request gitlab-org/gitlab-ce!24151
|
|
|
|
If there are new strings in CE, they need to be added to EE
manually. As the `locale/gitlab.pot` file can't be merged
automatically during the upstream merge.
|
|
This rewrites a syntax to allow include of templates.
This also normalises the syntax used by include: feature
|
|
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
|
|
'49056-configure-auto-devops-deployed-applications-with-secrets-that-aren-t-committed-to-the-repo' into 'master'
Configure Auto DevOps deployed applications with secrets from prefixed CI variables
See merge request gitlab-org/gitlab-ce!23719
|
|
Support new issue creation by email without subaddressing
Closes #29951
See merge request gitlab-org/gitlab-ce!23523
|
|
[CE] Don't run checks for changed refs when specific changes are unknown
See merge request gitlab-org/gitlab-ce!23990
|
|
- DRY up setting deploy name
- DRY up application_secret_name
|
|
|
|
Use --from-env-file with bash process substitution
We still need bash as process substition (`<()`) is not available in sh
|
|
ie. fix below quoting issue:
```
kubectl create secret -n project-with-autodevops-900057eb1ce34399-77 \
generic production-secret \
'--from-literal=OPTIONAL_MESSAGE=You' can see this secret \
-o yaml --dry-run
```
With fix, it should be generating:
```
kubectl create secret -n project-with-autodevops-900057eb1ce34399-77 \
generic production-secret \
--from-literal 'OPTIONAL_MESSAGE=You can see this secret' \
-o yaml --dry-run
```
Call via bash -c, instead of assuming bash
The shell is /bin/sh, so we cannot asssume bash. Hence we use `bash -c`
bash is installed for deploy jobs in a prior step
|
|
Find any CI variables from `env` which has a prefix. If there are any
such CI variables, strip prefix from variable name then create a generic
Kubernetes secret containing all these CI variables as key-value pairs.
Also, Pass in secretname to application container
The secretname may be present, if nil, the chart does nothing. If
present, the chart will load the key-value pairs from the secret into
the application container. See
https://gitlab.com/charts/auto-deploy-app/blob/master/README.md#configuration
|
|
|
|
|
|
including verifying the project_slug
|
|
|
|
We now use `-issue` in order to support catch all email addresses
|
|
We now use `-merge-request` instead of `+merge-request+`
in order to support catch all email addresses
|
|
We now use `-unsubscribe` instead of `+unsubscribe`
in order to support catch all email addresses
|
|
Webhook URLs were recently encrypted in the database via
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/21645, and as a
result they are no longer exported. When an exported project with
Webhooks is imported, the project import service will fail with
`URI::InvalidURIError: bad URI(is not URI?)` due to a blank URL.
We avoid this by disabling the export/import of Webhooks in
the first place.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/53513
|
|
|