Does stderr capture the wrong thing, or my config is wrong ? #267

zsimple · 2020-02-26T00:41:30Z

First thanks for your great work, it a very helpful tool.

I used the docker version, and also tried run jobber in a clean alpine image, it's the same result.

.jobber file

version: 1.4

jobs:
  Example:
    cmd: /root/test.sh
    time: "*"
    notifyOnSuccess:
      - type: stdout
        data: [stdout, stderr]

test.sh

#!/bin/sh

echo "hello stdout"
echo "hello stderr" >&2

The output result was expected to be

{"job":{"command":"/root/test.sh","name":"Example","status":"Good","time":"* * * * * *"},"startTime":1582677064,"stderr":"hello stderr\n","stdout":"hello stdout\n","succeeded":true,"user":"root","version":"1.4"}

But in fact it outputs(watch the stderr field, same as stdout):

{"job":{"command":"/root/test.sh","name":"Example","status":"Good","time":"* * * * * *"},"startTime":1582677064,"stderr":"hello stdout\n","stdout":"hello stdout\n","succeeded":true,"user":"root","version":"1.4"}

By the way, if I use type: filesystem, it works fine.

The text was updated successfully, but these errors were encountered:

dshearer self-assigned this May 10, 2020

dshearer added the bug label May 10, 2020

TheJuffo linked a pull request Apr 28, 2021 that will close this issue

Fixed capturing of stderr #330

Open

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Does stderr capture the wrong thing, or my config is wrong ? #267

Does stderr capture the wrong thing, or my config is wrong ? #267

zsimple commented Feb 26, 2020 •

edited

Does stderr capture the wrong thing, or my config is wrong ? #267

Does stderr capture the wrong thing, or my config is wrong ? #267

Comments

zsimple commented Feb 26, 2020 • edited

zsimple commented Feb 26, 2020 •

edited