An important part of parallel-processing are locks for access on the same ressource.
There are 2 basic approaches to this:
Cancel the current processing and start the new one
This could be favoured, because the new job is more up-to-date and could/should include some of the current processing steps too
Let the current one finish and put the new one in a queue.
This is potentially alot cleaner, but will increase timing significantly.
An important part of parallel-processing are locks for access on the same ressource.
There are 2 basic approaches to this:
1. Cancel the current processing and start the new one
This could be favoured, because the new job is more up-to-date and could/should include some of the current processing steps too
2. Let the current one finish and put the new one in a queue.
This is potentially alot cleaner, but will increase timing significantly.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
An important part of parallel-processing are locks for access on the same ressource.
There are 2 basic approaches to this:
Cancel the current processing and start the new one
This could be favoured, because the new job is more up-to-date and could/should include some of the current processing steps too
Let the current one finish and put the new one in a queue.
This is potentially alot cleaner, but will increase timing significantly.