Re: Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs
Date
Msg-id CDAF1500-72E3-4089-A94B-456392208328@yesql.se
Whole thread Raw
In response to Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs  (Nazir Bilal Yavuz <byavuz81@gmail.com>)
Responses Re: Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs
List pgsql-hackers
> On 7 Sep 2023, at 18:06, Nazir Bilal Yavuz <byavuz81@gmail.com> wrote:

> if the changes are only in the docs, don't run
> all tasks except building the docs task; this could help to save more
> CI times.

A related idea for docs in order to save CI time: if the changes are only in
internal docs, ie README files, then don't run any tasks at all.  Looking at
src/backend/parser/README the last two commits only touched that file, and
while such patches might not be all that common, spending precious CI resources
on them seems silly if we can avoid it.

It doesn't have to be included in this, just wanted to bring it up as it's
related.

> I attached two patches.
>
> I assumed that the docs related changes are limited with the changes
> in the docs folder but I am not really sure about that.

Almost, but not entirely.  There are a set of scripts which generate content
for the docs based on files in src/, like src/backend/catalog/sql_features.txt
and src/include/parser/kwlist.h.  If those source files change, or their
scripts, it would be helpful to build docs.

--
Daniel Gustafsson




pgsql-hackers by date:

Previous
From: "Hayato Kuroda (Fujitsu)"
Date:
Subject: RE: pg_ctl start may return 0 even if the postmaster has been already started on Windows
Next
From: shveta malik
Date:
Subject: Re: Synchronizing slots from primary to standby