Le mar. 15 mars 2016 à 22:35, honas grael <honasgraeym...@gmail.com> a
écrit :
> Hi reading the docs I came across
>
> *decodeRC**This is a dictionary that decodes exit codes into results
> value. For example, {0:SUCCESS,1:FAILURE,2:WARNINGS}, will treat the exit
> code 2 as WARNINGS. The default is to treat just 0 as successful.
> ({0:SUCCESS}) any exit code not present in the dictionary will be treated
> as FAILURE*
>
> this seems pretty cool to me so I am trying to make use of it in my
> buildstep, I am trying to use it in conjunction with HaltOnFailure
>
> the build step launches an executable(yes I'm on windows 7), the
> executable does a number of things, sometimes calling other executalbes,
> and eventually returns with an exit code of 0(if successful) or 1 if
> unsuccessful.
>
> so the master.cfg looks somewhat like this
>
> factory.addStep(steps.ShellCommand(
>
> command=["run_my_custom_executable.exe","config_file_for_executable.txt"],
> logfiles={"triallog": {"filename": "c:\\temp\\test.log",
> HaltOnFailure=True,
> DecodeRC={0:"success",1:"failure"}
> }}))
>
>
Hi honas , you should not use 'failure' as a string, but rather the FAILURE
constant from the buildbot.process.results module.
_______________________________________________
users mailing list
users@buildbot.net
https://lists.buildbot.net/mailman/listinfo/users
