You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An enhancement to #2034: if something like #2066 passes, you ought to be able to trigger a release without redundantly running tests again on trunk. Perhaps Jenkinsfile on master, when run manually (#1993), could first check if the full-tests branch has passing checks, and if so, and it was really solely an empty commit relative to the commit under test (head of main), immediately succeed.
The text was updated successfully, but these errors were encountered:
An enhancement to #2034: if something like #2066 passes, you ought to be able to trigger a release without redundantly running tests again on trunk. Perhaps
Jenkinsfile
on master, when run manually (#1993), could first check if thefull-tests
branch has passing checks, and if so, and it was really solely an empty commit relative to the commit under test (head ofmain
), immediately succeed.The text was updated successfully, but these errors were encountered: