You'll need to add a load method override to this form that conditionally disables the manual run field depending on the version of Review Board that it's running on. See the version in Review Bot for an example.

Can we make the label "Run builds manually"?

Why do we need to check if we should build again? It seems like if we shouldn't build the first time, we'd never even end up creating a status update which can be run/retried.

Can we add a blank line between these two?

This comment doesn't add anything useful (the code is pretty clear that it's initializing variables)

Grammar here is a little off. It sounds like it should probably have a plural "requests": "Don't build any review requests that don't have matching configs"

This could all be combined together:

return (bool(matching_configs), repository, vcs_type,
        matching_configs)

These should use single quotes.
Alternatively, Christian was suggesting we could do the import test once, up at the top of the file:

try:
    from reviewboard.reviews.signals import status_update_request_run
except ImportError:
    status_update_request_run = None


and then here:

if status_update_request_run is None:
    self.disabled_fields = ['run_manually']
    ...


This has the advantage of only doing the import check once, though this form is very rarely accessed so it's probably not important either way. Your call if you want to change it.

Given that we only need the should_build flag once now, let's remove it from the return tuple of this method and then where we use it, we can define it using bool(matching_configs).
This is important here because of the _. Unfortunately for us, _ has two meanings: it's common to use it in python for unused return values, but we also often use it to name the ugettext import. This line could redefine the ugettext function as whatever the return value was (at least for the scope of this method). This is error-prone, so because we can avoid it entirely, we should.

Can we clarify the method name here? Maybe test_manual_run_no_build_on_publish ?

Just a couple little style nits.

We still should have two blank lines here.

Please add a space between the = and \

Awesome Work!

Unfortunately, I experienced a test failure for test #86 Testing circleCIIntegration build via a manual trigger.

I am not sure why this is the case. The steps I took for this was:
1) git checkout -b circleci from the master branch in rbintegrations repo.

2) rbt patch -c 11208 successfully pulled downed the patch and committed the files.

3) ./setup develop successfully ran

4) rbtext test -m rbintegrations.circleci this is where I had a test fail, am I invoking this correctly?
Otherwise, I just found some small styling comments, but I am not even completely sure whether they are correct.

I believe there should be a period at the end of every comment.

I could be wrong about this when it is in regard to import statements, versus from ... import ... statements. But I think that from datetime import datetime should come before import json to preserve alphabetical order. However, please correct me if I am wrong in this specific case.

Ship It!

Please put the """ on the next line here.

One last nit.

Unlike docstrings everywhere else, docstrings for test cases shouldn't end in a period (since the test runner will append an ellipsis when printing the test case name)

Same here.

And here.

And here.

Ship It!