Closed ekohl closed 11 years ago
not a django-jenkins issue
I investigated a bit further and discovered that running pylint from the command line was also broken. Somehow it wasn't processing the logilab-common>=0.60.0
dependency. After I upgrade that, I can reproduce the pylint error on the command line.
However, I do think this is a django-jenkins issue since 0.14.1 requires pylint 1.0.0 so the pylint runner is broken in the latest version. Also, the warning is triggered because django-jenkins uses a deprecated pylint reporter.
does this issue solved in some way? I tried the django-jenkins on a fresh django installation and I got the same issue.
Every time I run, I get the following error (I think it's a warning and then an error):
Since it exits with code 1, all my builds start to fail.
Tried on django-jenkins 0.13.0 and 0.14.1.