Run e2e tests once other minimal checks ends successfully

[jsolana]

Summary

e2e tests are expensive, lasting 30 - 35 min to be executed.

Does it make sense to run resource-intensive e2e tests before completing basic checks like ensuring there are no schema changes? Example

Motivation

Just wondering if make sense to "spend resources" running e2e tests with a pipeline that fails

Proposal

Instead to run e2e in parallel from the beginning, lets waitfor the minimal unit test and checks as linter, changes with codegen etc,. before start to avoid run those pipelines if one of this steps fail:

• Lint Go Code
• Check changes to generated code
• Build, test & lint UI code

[sivchari]

May I work on it ?

[andrii-korotkov-verkada]

@sivchari, sure, you don't have to ask permissions :)

[jsolana]

May I work on it ?

Hi during next days Im gonna have time to dedicate to this issue. Do you have any progress?

[andrii-korotkov-verkada]

It's been only 3 days ago, I suggest to pick some other issue for now and come back to this a couple of weeks later if there's no progress.

[jsolana]

It's been only 3 days ago, I suggest to pick some other issue for now and come back to this a couple of weeks later if there's no progress.

Sure, I was just asking because both tasks were assigned to the same person shortly after I created them, and I was wondering if it might be too much for one person at once.

I understand if work has already started on one, but if not, I was just asking in case I could lend a hand.

Thanks!

[crenshaw-dev]

Instead of blocking e2e tests on faster checks, I'd cancel e2e tests if another check fails. That way we free up runners, but we don't delay e2e another ~5min.