Skip to content
GitLab
Next
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Primary navigation
Search or go to…
Project
GitLab
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Privacy statement
Keyboard shortcuts
?
What's new
4
Snippets
Groups
Projects
Show more breadcrumbs
GitLab.org
GitLab
Commits
9cbed108
Commit
9cbed108
authored
5 years ago
by
Bill Bagdon
Committed by
Achilleas Pipinellis
5 years ago
Browse files
Options
Downloads
Patches
Plain Diff
ci_builds also has encrypted tokens
These need to be reset
parent
8c5f583a
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/raketasks/backup_restore.md
+23
-0
23 additions, 0 deletions
doc/raketasks/backup_restore.md
with
23 additions
and
0 deletions
doc/raketasks/backup_restore.md
+
23
−
0
View file @
9cbed108
...
...
@@ -923,6 +923,29 @@ backup beforehand.
UPDATE
ci_runners
SET
token
=
null
,
token_encrypted
=
null
;
```
#### Reset pending pipeline jobs
1.
Enter the DB console:
For Omnibus GitLab packages:
```
sh
sudo
gitlab-rails dbconsole
```
For installations from source:
```
sh
sudo
-u
git
-H
bundle
exec
rails dbconsole
RAILS_ENV
=
production
```
1.
Clear all the tokens for pending jobs:
```
sql
-- Clear build tokens
UPDATE
ci_builds
SET
token
=
null
,
token_encrypted
=
null
;
```
A similar strategy can be employed for the remaining features - by removing the
data that cannot be decrypted, GitLab can be brought back into working order,
and the lost data can be manually replaced.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment