Specify a job as non-blocking?

I have two jobs categoriezed as code quality, rubocop, and codeclimate (cli).

I want the rubocop to be required before running tests, the next job.
but since codeclimate allows failures, and can sometimes take a while, I don’t want it holding up the tests job. BUT! I do want it to block my pages / artifacts deploy job. Is there a way to do this?

codeclimate / rubocop
v
tests (depends on rubocop)
v
deploy (depends on tests)
v
pages / artifacts / move to public (depends on tests and codeclimate)