Problem with Jenkins CI due to "sys.stdin.isatty" check

When using gitlint on Jenkins it doesn’t work as it does locally simply by executing “gitlint” to check the latest commit.

gitlint

Since on Jenkins there is not tty present the command simply fails with several cryptical warnings (probably because stdin is empty). When using the -d option it tells me DEBUG: gitlint.lint Linting commit [SHA UNKNOWN] which was even more confusing.

After reading the code and re-reading the documentation I ended up sucessfully using this:

git log -1 --pretty=%B | gitlint

This is a little cumbersome and it seems unecessary to base the decision whether to perform GitContext.from_local_repository depending on if there is a TTY present or not.

Suggestions:

• Always use from_local_repository if there is a local repository AND (stdin is empty OR not tty). Use stdin in other cases.
• Alternatively or additionally document this more clearly. Maybe a doc section on how to use gitlint with CI tools.

[jorisroovers]

Great @pbregener, thanks! I’ll see if I can wrap this patch up properly over the weekend.

[pbregener]

I can confirm that it works in GitLab CI, too, @jorisroovers! 👍 Let me know if you need more details, I might have some time tomorrow…