Pushing new commits to a branch, does not stop a prebuild from a previous commit of the same branch.

[shaal]

Bug description

I think a previously running prebuild should be cancelled if new commits are pushed to the same branch.

I noticed it after I pushed changes to a branch, and realized I forgot to make a small change.

Steps to reproduce

Create long init task in .gitpod.yml.
After pushing a commit that will trigger the prebuild, push another commit to the same branch, and go to Prebuilds page on your gitpod.io account.

Workspace affected

No response

Expected behavior

Seems like waste of resources to keep the previous prebuild running.
Not sure if this might cause other issues (like an old prebuild finish running after the latest prebuild, and perhaps override things?)

Example repository

No response

Anything else?

No response

[loujaybee]

Thanks for adding @shaal !

Just came here to note that this behavior is how most CI tools also work, and the workflow would be to cancel any unwanted jobs. And that it might be quite difficult to work out whether or not a commit should or shouldn't be built 🤔

[svenefftinge]

And that it might be quite difficult to work out whether or not a commit should or shouldn't be built 🤔

Can you elaborate on what challenges you expect here? I'm currently believing that just building the latest change per branch would do 😇 .

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.