[ 
https://issues.apache.org/jira/browse/NUTCH-3237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18141653#comment-18141653
 ] 

Hudson commented on NUTCH-3237:
-------------------------------

SUCCESS: Integrated in Jenkins build Nutch ยป Nutch-trunk #287 (See 
[https://ci-builds.apache.org/job/Nutch/job/Nutch-trunk/287/])
NUTCH-3237 Yetus markdownlint reports CLI usage for ignored CHANGES.md on 
master (#993) (github: 
[https://github.com/apache/nutch/commit/7c5310749b36b19545bb445ae386b529b59dda9f])
* (edit) .yetus/personality.sh
* (edit) .markdownlintignore


> Yetus markdownlint reports CLI usage for ignored CHANGES.md on master
> ---------------------------------------------------------------------
>
>                 Key: NUTCH-3237
>                 URL: https://issues.apache.org/jira/browse/NUTCH-3237
>             Project: Nutch
>          Issue Type: Sub-task
>          Components: ci/cd
>    Affects Versions: 1.23
>            Reporter: Lewis John McGibbney
>            Assignee: Lewis John McGibbney
>            Priority: Major
>             Fix For: 1.24
>
>
> Apache Yetus on {{master}} fails in full mode. GitHub Actions run 
> [42068070475|https://github.com/apache/nutch/actions/runs/42068070475] (push 
> of {{{}88b67bc{}}}, {{{}[NUTCH-3232]{}}}) votes {{-1}} only for markdownlint: 
> "The source tree has 23 issues." The same report is on run 
> [41374308732|https://github.com/apache/nutch/actions/runs/41374308732]. Pull 
> requests pass because patch mode does not lint unchanged {{{}CHANGES.md{}}}.
> The 23 lines in {{results-markdownlint.txt}} are markdownlint-cli 0.44.0's 
> usage text, not markdown findings. {{.markdownlintignore}} lists 
> {{{}CHANGES.md{}}}. Yetus 0.15.1 runs {{markdownlint}} once per markdown 
> file. That CLI calls {{program.help()}} when ignore filtering leaves no 
> paths. Yetus records the banner as findings. Other markdown files are clean 
> under {{{}.markdownlint.yaml{}}}. Every other plugin on that run is 
> {{{}+1{}}}.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to