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
When using components and trying to promote multiple commits at the same time, we have to iterate though all of them and call the /api/promote endpoint multiple times.
When this is done, we are creating a small window where a job could try to get the newly aggregated repo, and that would be quickly replaced by a new repo... So it will be hard to synchronize jobs and they may try to use different aggregates.
Ideally the DLRN api and dlrnapi client will support a batch operation where a user can send multiple commit and distro hash ids for a promotion and the updated repo and aggregated hash is ONLY written once. This would eliminate the issue.
The text was updated successfully, but these errors were encountered:
When using components and trying to promote multiple commits at the same time, we have to iterate though all of them and call the /api/promote endpoint multiple times.
When this is done, we are creating a small window where a job could try to get the newly aggregated repo, and that would be quickly replaced by a new repo... So it will be hard to synchronize jobs and they may try to use different aggregates.
Ideally the DLRN api and dlrnapi client will support a batch operation where a user can send multiple commit and distro hash ids for a promotion and the updated repo and aggregated hash is ONLY written once. This would eliminate the issue.
The text was updated successfully, but these errors were encountered: