Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
c3aca05d
Commit
c3aca05d
authored
Nov 02, 2020
by
Thong Kuah
Committed by
Amy Qualls
Nov 02, 2020
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Describe how to update requirements.yaml
List how to move from old to new stable repo location
parent
2cfd792a
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
23 additions
and
1 deletion
+23
-1
doc/topics/autodevops/index.md
doc/topics/autodevops/index.md
+23
-1
No files found.
doc/topics/autodevops/index.md
View file @
c3aca05d
...
@@ -498,7 +498,29 @@ include:
...
@@ -498,7 +498,29 @@ include:
Keep in mind that this approach will eventually stop working when the stable repository is removed,
Keep in mind that this approach will eventually stop working when the stable repository is removed,
so you must eventually fix your custom chart.
so you must eventually fix your custom chart.
You can find more information in
[
this issue
](
https://gitlab.com/gitlab-org/gitlab/-/issues/263778
)
.
To fix your custom chart:
1.
In your chart directory, update the
`repository`
value in your
`requirements.yaml`
file from :
```
yaml
repository
:
"
https://kubernetes-charts.storage.googleapis.com/"
```
to:
```
yaml
repository
:
"
https://charts.helm.sh/stable"
```
1.
In your chart directory, run
`helm dep update .`
using the same Helm major version as Auto DevOps.
1.
Commit the changes for the
`requirements.yaml`
file.
1.
If you previously had a
`requirements.lock`
file, commit the changes to the file.
If you did not previously have a
`requirements.lock`
file in your chart,
you do not need to commit the new one. This file is optional, but when present,
it's used to verify the integrity of the downloaded dependencies.
You can find more information in
[
issue #263778, "Migrate PostgreSQL from stable Helm repo"
](
https://gitlab.com/gitlab-org/gitlab/-/issues/263778
)
.
## Development guides
## Development guides
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment