Skipping steps.

[Itamar Bavli]

A question regarding skipping steps.

I have a job that checks if File exists, if it is is exists it will check the ChekSum of the file.

If the CheckSum, is the same with the users option, it should start installation, if the CheckSum is different, it should go to the next step and upload the file with file copy step.

My question, if I can jump the file copy step if the CheckSum and Filename checks to be OK.

which way is the best to tackle this?

Regards

Itamar 

[rac...@rundeck.com]

Hi Itamar,

That feature is available on Process Automation (formerly "Rundeck Enterprise")  via Ruleset Strategy, take a look at this. You can skip steps or jump to specific steps depending on some option or result.

On the community version, the best approach is to integrate all of that logic into a script (with conditional sentences).

Regards.

[Itamar Bavli]

Thanks, I'm using the community version, I'm testing now, logic using key-error handler with key/value data capture, to apply this logic.

so far looks good.

[Itamar Bavli]

Another Question half related,

Everything working well with the key-error handler.

My question is about quiet putout,

I'm sending 'exit 1' on my bash script to fail the step to invoice the error-handler step, I tried to use the quiet output to hide the "ERROR: Process exited with status 1", seems I can not get rid of it. It worked for other patterns.

Any known issue with that?

Thanks 

Itamar

[rac...@rundeck.com]

Hi Itamar,

Could you try with (.*ERROR.*) regex? I attached a Job Def example in YAML format for testing purposes :-)

Regards.