| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
| |
Unfortunately, it seems that the migration to
clusters_kubernetes_namespace still needs to create the new restricted
service accounts and then fetch the tokens. Until that is done, we
cannot use it and have to fall back to the main token from
clusters_platform_kubernetes.
|
|
|
|
| |
And also check KUBE_TOKEN in other scenarios
|
|\
| |
| |
| |
| | |
Fix error handling bugs in kubernetes integration
See merge request gitlab-org/gitlab-ce!22922
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
I have also extracted an issue in
https://gitlab.com/gitlab-org/gitlab-ce/issues/53738 to surface these
errors to users but now I am just fixing the bug where
kubernetes_namespace is undefined while handling this error
|
| |
| |
| |
| |
| |
| | |
There is no reason to specially handle 404 here. We only handle 404
specifically if we are fetching something and want to return `nil` if
404. This does not apply here.
|
|\ \
| | |
| | |
| | |
| | | |
Use gitlab-ui in jobs and pipelines
See merge request gitlab-org/gitlab-ce!22782
|
|/ / |
|
|\ \
| | |
| | |
| | |
| | | |
Remove circular dependency on Redactable in migration
See merge request gitlab-org/gitlab-ce!22951
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Gitlab::BackgroundMigration::RedactLinks was prepending
EE::Gitlab::BackgroundMigration::RedactLinks, while
EE::Gitlab::BackgroundMigration::RedactLinks was trying to include
Gitlab::BackgroundMigration::RedactLinks::Redactable. Ruby 2.5.3 failed
with an uninitialized constant
(https://gitlab.com/gitlab-org/gitlab-ee/-/jobs/118388511).
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Resolve "GitLab Pages settings regressions"
Closes #48475
See merge request gitlab-org/gitlab-ce!22821
|
|/ / / |
|
|\ \ \
| |/ /
|/| |
| | |
| | | |
Updates clipboard button with gitlab-ui
See merge request gitlab-org/gitlab-ce!22923
|
| | |
| | |
| | |
| | |
| | |
| | | |
Updates clipboard button component to use
the new glTooltipDirective and the new glButton
component from gitlab-ui
|
|\ \ \
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Fix alignment of diff comment buttons
Closes #53768
See merge request gitlab-org/gitlab-ce!22944
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
Fix DashboardHelper reference in spec
See merge request gitlab-org/gitlab-ce!22948
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
Helpers::DashboardHelper doesn't actually exist, and Ruby 2.5 gets rid
of the automatic top-level constant lookup
(https://bugs.ruby-lang.org/issues/11547).
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Resolve possible cherry pick API race condition
Closes #53773
See merge request gitlab-org/gitlab-ce!22946
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Previously, we just fetched the latest commit for the given branch when
presenting the resulting commit, but because something could have been
committed to that branch between the time we cherry-picked and the time
we render the result, the wrong commit could have been presented.
Now, we fetch the commit object with the commit SHA returned by the
commit change service, which should always be the correct commit.
Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/53773
|
|\ \ \ \ \
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Enable even more frozen string in lib/gitlab
See merge request gitlab-org/gitlab-ce!22863
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Enables frozens string for the following:
* lib/gitlab/conflict/**/*.rb
* lib/gitlab/cross_project_access/**/*.rb
* lib/gitlab/cycle_analytics/**/*.rb
* lib/gitlab/data_builder/**/*.rb
* lib/gitlab/database/**/*.rb
* lib/gitlab/dependency_linker/**/*.rb
* lib/gitlab/diff/**/*.rb
* lib/gitlab/downtime_check/**/*.rb
* lib/gitlab/email/**/*.rb
* lib/gitlab/etag_caching/**/*.rb
Partially addresses gitlab-org/gitlab-ce#47424.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Symlinked hooks aren't executed
See merge request gitlab-org/gitlab-ce!22933
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
This recently changed on the Gitaly side, but now spotted this in the
docs for the next release. Updated to be more precise, and to signal
users should not want control over this specific hook location.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | |
| | | | | | | | |
Ensure we create the secrets at the right time
Closes #53621
See merge request gitlab-org/gitlab-ce!22938
|
| | |_|_|_|_|/
| |/| | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
In `deploy`, if the previous deployment failed, we delete/cleanup all
the objects related to the release, including secrets. The problem is
that if we create the root password before that, it will be then
recreated during the deploy with a random value!
By creatigng the secret just before actually deplying a new release, we
ensure that it won't be overriden.
Signed-off-by: Rémy Coutable <remy@rymai.me>
|
|\ \ \ \ \ \ \
| |_|_|_|/ / /
|/| | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Add revert to commits API
Closes gitlab-org/release/framework#48
See merge request gitlab-org/gitlab-ce!22919
|
| | | | | | | |
|
| | |_|_|/ /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Previously the string was spanning multiple lines and included a
needless `\n` character in the resulting error message.
This change also reduces duplication by assigning two variables.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
'master'
Improve Debugging Capabilities For Helm Application Installs
See merge request gitlab-org/gitlab-ce!22924
|
|/ / / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
User can create a group level cluster and install applications
See merge request gitlab-org/gitlab-ce!22450
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
However, we only need to raise for project_type clusters to maintain
previous behaviour.
In all probablity this requirement to have actual_namespace came from
KubernetesService and will no longer be required soon.
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Use presenters instead otherwise we will have x2 overides in EE
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Refacotr project or group specific `if` logic to be contained within
each presenter instead.
Also add :override to ensure super method exists.
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Use model method as single source of truth instead of splitting between
presenter and Kubernetes model
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Group clusters should not allow Project Namespace so don't show that
field input too
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Based on BE reviewer feedback
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
As the frontend is still in progress and other related backend is still
in prgress we need a feature flag to turn off Group Clusters.
|
| | | | | | | |
|
| | | | | | | |
|