releases icon indicating copy to clipboard operation
releases copied to clipboard

Better error detection

Open bitprophet opened this issue 10 years ago • 1 comments

Attempt to detect whether a Sphinx build ran 100% without mutating a changelog, and bail out with a useful error. When this is not done, the only telltale sign is Sphinx-core complaining that it doesn't know what issue or release roles are (because they never got mutated into useful nodes.) This is kinda grody.

The only way I can think to do this offhand is to add A) some state keeping and B) a hook into the step after the one we currently hook into. I.e.:

  • Initialize some global variable (meh), e.g. did_a_changelog = False
  • Hook into the "build each document" step as we do now; set did_a_changelog = True if we do run.
  • In some step after that prior step, test did_a_changelog and die usefully if still False.

bitprophet avatar Apr 06 '14 18:04 bitprophet

N.B. that there is a skipped/empty integration level test for this already.

bitprophet avatar Apr 06 '14 18:04 bitprophet