Restrict the nightly tests run

[pallavisontakke]

upto the latest release branch.
e.g. when this script is back-ported, avoid running it on the last release branch e.g. 2.17.x

Disable-check: force-changelog-file

[github-actions]

@akuzm, @gayyappan: please review this pull request.

Powered by pull-review

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.93%. Comparing base (59f50f2) to head (45aaf5d).
Report is 785 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #7757      +/-   ##
==========================================
+ Coverage   80.06%   81.93%   +1.86%     
==========================================
  Files         190      247      +57     
  Lines       37181    45424    +8243     
  Branches     9450    11353    +1903     
==========================================
+ Hits        29770    37216    +7446     
- Misses       2997     3737     +740     
- Partials     4414     4471      +57     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mkindahl]

This workflow only runs on schedule and on workflow dispatch.

When running on a schedule, the default branch (main in our case) should be checked out and the workflow should run there, so I am not sure what problem you are solving with this change.

Could you elaborate?

[pallavisontakke]

This workflow only runs on schedule and on workflow dispatch.

When running on a schedule, the default branch (main in our case) should be checked out and the workflow should run there, so I am not sure what problem you are solving with this change.

Could you elaborate?

Hi @mkindahl ,
Right now , this yaml file is on main. When we cut 2.19.x , it'll appear there too. During a minor version release, e.g. 2.19.0 , we'll have 2.18.2 written in downgrade_to_version in version.config . Like during 2.18.0 release, we had 2.17.2 there .

In current scenario, we want to run tests on release-branch 2.18.x and not on 2.17.x too. So the check.

[pallavisontakke]

Maybe I'm wrong here , so will check the behaviour on 2.18.x of the existing yaml file first & then get here, if this PR is really needed.