I installed Warnings plugin and it works fine. A violations plugin's bug
have been reported here:
https://github.com/jenkinsci/violations-plugin/issues/36
вторник, 22 октября 2013 г., 14:53:57 UTC+4 пользователь Ullrich Hafner
написал:
>
> Seems that something is broken there. Please create a b
Seems that something is broken there. Please create a bug report in our issue
tracker.
Can you please check if the pep8 parser in the warnings plug-in works for your
file? If the same exceptions appears there too then maybe your input file is
somehow corrupt?
Ulli
Am 22.10.2013 um 12:37 s
reports\pep8.log
вторник, 22 октября 2013 г., 14:23:05 UTC+4 пользователь Ullrich Hafner
написал:
>
> What did you specify as file pattern?
>
> Ulli
>
> Am 22.10.2013 um 12:07 schrieb Dmitry S
> >:
>
> I'm using pytest to run pep8 check:
>
> py.test --pep8 --junitxml=reports\pep8.log
>
> I setup
What did you specify as file pattern?
Ulli
Am 22.10.2013 um 12:07 schrieb Dmitry S :
> I'm using pytest to run pep8 check:
>
> py.test --pep8 --junitxml=reports\pep8.log
>
> I setup a job to look for pep8.log file in reports\pep8.log
>
> But when i run the job I see that the path where violat
I'm using pytest to run pep8 check:
py.test --pep8 --junitxml=reports\pep8.log
I setup a job to look for pep8.log file in reports\pep8.log
But when i run the job I see that the path where violations plugin looks
for reports makes no sense:
generated xml file:
C:\Jenkins\jobs\python-template-2
