It should be a single imperfect-tense verb, like compiling or testing. description This will be used to describe the command (on the Waterfall display) while the command is still running. alwaysRun if True, this build step will always be run, even if a previous buildstep with haltOnFailure=True has failed. The remaining steps will still be executed. warnOnFailure when True, a FAILURE of this build step will mark the overall build as having WARNINGS. warnOnWarnings when True, a WARNINGS or FAILURE of this build step will mark the overall build as having WARNINGS. flunkOnFailure when True, a FAILURE of this build step will mark the overall build as a FAILURE. flunkOnWarnings when True, a WARNINGS or FAILURE of this build step will mark the overall build as FAILURE. This can be achieved with haltOnFailure=True, flunkOnFailure=False. In some cases, particularly series of tests, it makes sense to haltOnFailure if something fails early on but not flunkOnFailure. Generally speaking, haltOnFailure implies flunkOnFailure (the default for most BuildSteps). haltOnFailure if True, a FAILURE of this build step will cause the build to halt immediately. Since 0.9.8, this argument might be renderable. Others are used to specify which Locks (see Interlocks) should be acquired before allowing the step to run.Īrguments common to all BuildStep subclasses: name the name used to describe the step on the status display. Some of these control how their individual status affects the overall build.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |