Skip to content
GitLab
Menu
Projects
Groups
Snippets
/
Help
What's new
6
Help
Support
Community forum
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
Menu
Open sidebar
gitlab-com
migration
Commits
d2e5c272
Verified
Commit
d2e5c272
authored
Jul 27, 2018
by
Nick Thomas
Browse files
Clarify how to disable/enable Pages cronjob
parent
6e139b8d
Changes
2
Hide whitespace changes
Inline
Side-by-side
.gitlab/issue_templates/failback.md
View file @
d2e5c272
...
...
@@ -86,6 +86,7 @@ working order, including database replication between the two sites.
1.
[ ] ↩️ {+ Fail-back Handler +}: Set the GitLab shared runner timeout back to 3 hours
1.
[ ] ↩️ {+ Fail-back Handler +}: Restart automatic incremental GitLab Pages sync
*
Enable the cronjob on the
**Azure**
pages NFS server
*
`sudo crontab -e`
to get an editor window, uncomment the line involving rsync
1.
[ ] ↩️ {+ Fail-back Handler +}: Update GitLab shared runners to expire jobs after 3 hours
*
In a Rails console, run:
*
`Ci::Runner.instance_type.update_all(maximum_timeout: 10800)`
...
...
.gitlab/issue_templates/failover.md
View file @
d2e5c272
...
...
@@ -156,6 +156,7 @@ an hour before the scheduled maintenance window.
*
Production:
`bin/snapshot-dbs production`
1.
[ ] 🔪 {+ Chef-Runner +}: Stop automatic incremental GitLab Pages sync
*
Disable the cronjob on the
**Azure**
pages NFS server
*
`sudo crontab -e`
to get an editor window, comment out the line involving rsync
1.
[ ] 🔪 {+ Chef-Runner +}: Start parallelized, incremental GitLab Pages sync
*
Expected to take ~30 minutes, run in screen/tmux! On the
**Azure**
pages NFS server!
*
Updates to pages after now will be lost.
...
...
Write
Preview
Supports
Markdown
0%
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!
Cancel
Please
register
or
sign in
to comment