+1 to Sanjeev's suggestion On Mon, Jan 28, 2019 at 12:15 PM Sanjeev Kulkarni <sanjee...@gmail.com> wrote:
> If developers are in charge of checking the checkbox, it might lead to > errors. Any way to make it automatic? Since docs are restricted to certain > areas of repo, maybe we can have some rules around that? > > On Mon, Jan 28, 2019 at 12:12 PM Sijie Guo <si...@apache.org> wrote: > > > Hi all, > > > > Currently for every documentation change, we have run 3 precommit jobs, > > java, c++ and integrationt tests. None of them is actually testing the > > documentation change and it is wasting jenkins resources and make the > merge > > process for documentation changes take much longer time. > > > > So I am proposing : > > > > - add a separate precommit job for documentation-only changes. e.g. > > `Jenkins: Documentation Tests` > > > > - provide a checkbox in description > > * [ ] documentation-only change > > * [ ] code-only change > > > > - if `[x] documentation-only` is checked, then java, c++ and integration > > tests will be skipped. > > - if `[x] code-only` is checked, then documentation tests will be > skipped. > > > > > > I would like to see what other people think about this. > > > > - Sijie > > >
