I agree we should be triggering on SCM poll. Whomever updates that please monitor the results to make sure we weren't avoiding that before due to a bug in jenkins polling.
If we switch the various builds to rely on flaky lists from their minor release that could be fine, but we'll have to be more proactive in backporting things that stabilize tests and EOM branches where we don't do those backports. That sounds great to me personally. I don't have time at the moment to go back and check the discussion threads on branch EOM. if they ended in it being fine to EOM branch-2.1 and branch-1.3 that would cut down on things enough to offset the addition of branch-2.3. Can we switch our jobs to do sequential steps instead of parallel? that will make them take a lot longer but it will mean we don't overwhelm the executors all at once. On Wed, Mar 18, 2020 at 12:45 AM Stack <st...@duboce.net> wrote: > On Tue, Mar 17, 2020 at 3:36 PM Nick Dimiduk <ndimi...@apache.org> wrote: > > > "Poll SCM: daily" sounds like a good default for everything. > > > > > This sounds good to me. Let me try it for: 1.3, 1.4, 2.1 (unless > objection). > > There are two other branches that run nightly: > > > https://builds.apache.org/view/H-L/view/HBase/job/HBase%20Nightly/job/HBASE-22114-branch-1/configure > > https://builds.apache.org/view/H-L/view/HBase/job/HBase%20Nightly/job/HBASE-23162-branch-1/ > > The top-most I changed today seemingly successfully from @daily to @weekly > (at Sean's request). I should change it and HBASE-23162-branch-1 to 'Poll > SCM: daily' too (If I can figure out how to do it). > > On flakeys, if they are not being looked at/addressed, they just burning > CPU. Up on slack, he asked that we not turn off flakeys. I could turn down > frequency on the old builds (I think I know how to do this...). > > Will mess w/ this starting tomorrow (out loud on slack) time permitting. > S > > > > > > > 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 > > > > > > > > > > > > > > >
