You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@flink.apache.org by "Chesnay Schepler (JIRA)" <ji...@apache.org> on 2018/05/10 11:56:00 UTC

[jira] [Closed] (FLINK-9318) Mark ConfigOptionsDocsCompletenessTest as IT case

     [ https://issues.apache.org/jira/browse/FLINK-9318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chesnay Schepler closed FLINK-9318.
-----------------------------------
    Resolution: Fixed

master: 0ff88b0e8da5cae764510edfb226947e4ba52b83
1.5: d637a3a43d7e5d48ef31eb794eec946d088e0658

> Mark ConfigOptionsDocsCompletenessTest as IT case
> -------------------------------------------------
>
>                 Key: FLINK-9318
>                 URL: https://issues.apache.org/jira/browse/FLINK-9318
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 1.5.0
>            Reporter: Chesnay Schepler
>            Assignee: Chesnay Schepler
>            Priority: Trivial
>             Fix For: 1.5.0
>
>
> The documentation generators are currently run after the execution of tests. An attempt to regenerate the docs, without disabling the tests, will thus fail since the completeness test is run before the regeneration.
> We should mark (i.e. rename) the {{ConfigOptionsDocsCompletenessTest}} as an IT case, so that the build life-cycle looks like this:
> * run tests verifying generator functionality
> * generate docs
> * verify doc completeness



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)