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 Tom Lane
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 2952719.1696601228@sss.pgh.pa.us
Whole thread Raw
In response to Re: Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs  (Peter Eisentraut <peter@eisentraut.org>)
Responses Re: Build the docs if there are changes in docs and don't run other tasks if the changes are only in docs
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
Peter Eisentraut <peter@eisentraut.org> writes:
> I don't have a good sense of what you are trying to optimize for.  If 
> it's the mainline build-on-every-commit type, then I wonder how many 
> commits would really be affected by this.  Like, how many commits touch 
> only a README file.  If it's for things like the cfbot, then I think the 
> time-triggered builds would be more frequent than new patch versions, so 
> I don't know if these kinds of optimizations would affect anything.

As a quick cross-check, I searched our commit log to see how many
README-only commits there were so far this year.  I found 11 since
January.  (Several were triggered by the latest round of pgindent
code and process changes, so maybe this is more than typical.)

Not sure what that tells us about the value of changing the CI
logic, but it does seem like it could be worth the one-liner
change needed to teach buildfarm animals to ignore READMEs.

-    trigger_exclude => qr[^doc/|\.po$],
+    trigger_exclude => qr[^doc/|/README$|\.po$],

            regards, tom lane



pgsql-hackers by date:

Previous
From: "Rares Pop (Treelet)"
Date:
Subject: Custom tstzrange with importance factored in
Next
From: Sergei Glukhov
Date:
Subject: Problem, partition pruning for prepared statement with IS NULL clause.