Thanks for the effort, @Chesnay. This is super helpful. @Jing, Every push to the PR branch should automatically trigger an entire new build. `@flinkbot run azure` should only be used when you want to re-run the failed stages without changing the PR. E.g., when running into known unstable cases that are unrelated to the PR.
Thank you~ Xintong Song On Mon, Oct 11, 2021 at 11:45 AM JING ZHANG <beyond1...@gmail.com> wrote: > Hi Chesnay, > Thanks for the effort. It is a very useful improvement. > I have a minor question. Please forgive me if the question is too naive. > Since '@flinkbot run azure' now behaves like "Rerun failed jobs", is there > any way to trigger an entirely new build? Because some times I'm not sure > the passed cases in the last build could still success in the new build > because of introduced updates in new commit. > > Best, > JING ZHANG > > > Yangze Guo <karma...@gmail.com> 于2021年10月11日周一 上午10:31写道： > > > Thanks for that great job, Chesnay! "Rerun failed jobs" will help a lot. > > > > Best, > > Yangze Guo > > > > On Sun, Oct 10, 2021 at 4:56 PM Chesnay Schepler <ches...@apache.org> > > wrote: > > > > > > I made a number of changes to the CiBot over the weekend. > > > > > > - '@flinkbot run azure' previously triggered an entirely new build > based > > > on the last completed one. It now instead retries the last completed > > > build, only running the jobs that actually failed. It basically behaves > > > like the "Rerun failed jobs" button in the Azure UI. > > > - various optimizations to increase responsiveness (primarily by doing > > > significantly less unnecessary work / requests to GH) > > > - removed TravisCI support (since we no longer support a release that > > > used Travis) > > > > > > Please ping me if you spot anything weird. > > >
