"Poll SCM: daily" sounds like a good default for everything. On Tue, Mar 17, 2020 at 11:44 AM Bharath Vissapragada <bhara...@apache.org> wrote:
> Switch the build trigger for branches from "Build periodically: daily" to > "Poll SCM: daily" ? This may not help master much because commits land > almost every day but for branches like branch-2.2 where the commits are not > that often the nightlies are triggered only when there are new commits > < > https://stackoverflow.com/questions/41114251/what-is-the-difference-between-poll-scm-build-periodically-in-jenkins/41114307 > > > . > > Also +1 to reducing the frequency of 1.3/1.4/2.1 and feature branches. > > On Tue, Mar 17, 2020 at 10:58 AM Stack <st...@duboce.net> wrote: > > > On Tue, Mar 17, 2020 at 10:35 AM Nick Dimiduk <ndimi...@apache.org> > wrote: > > > > > Heya, > > > > > > We've been dinged on HBASE-24001 for our unneighborly Jenkins usage. I > > > haven't dug into the report to verify or diagnose, I hear it as a > > > reasonable accusation. I recently made things worse during the JDK11 > work > > > by using parallel stages. I'm about to make it worse by adding > branch-2.3 > > > to the nightly matrix. > > > > > > How should we approach this? > > > > > > I would suggest we reduce our flakey build runner to only look at > master, > > > branch-2, and branch-1. We'd need to update the nightly and PR jobs to > > use > > > their respective branch's flakey list as well. > > > > > > > > Could turn down or off the frequency at which some of the nightlies run. > Do > > we need 1.3 and 1.4 run every night? 2.1? > > On flakies, could at least turn off 2.1, 1.3, and 1.4 runs unless they > are > > being studied? > > > > S > > > > > > > > > Other idea? > > > > > > Thanks, > > > Nick > > > > > >
