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
bbcc1808
Commit
bbcc1808
authored
Feb 13, 2018
by
Dylan Griffith
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update sidekiq_style_guide.md
parent
e8648270
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
2 additions
and
2 deletions
+2
-2
doc/development/sidekiq_style_guide.md
doc/development/sidekiq_style_guide.md
+2
-2
No files found.
doc/development/sidekiq_style_guide.md
View file @
bbcc1808
...
@@ -17,8 +17,8 @@ would be `process_something`. If you're not sure what queue a worker uses,
...
@@ -17,8 +17,8 @@ would be `process_something`. If you're not sure what queue a worker uses,
you can find it using
`SomeWorker.queue`
. There is almost never a reason to
you can find it using
`SomeWorker.queue`
. There is almost never a reason to
manually override the queue name using
`sidekiq_options queue: :some_queue`
.
manually override the queue name using
`sidekiq_options queue: :some_queue`
.
You must always add any new queues to
`
gitlab/app/workers/all_queues.yml`
You must always add any new queues to
`
app/workers/all_queues.yml`
otherwise
otherwise
your worker will not run.
your worker will not run.
## Queue Namespaces
## Queue Namespaces
...
...
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