Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Concurrent run once tasks #1069

Merged
merged 3 commits into from Jul 20, 2016
Merged

Concurrent run once tasks #1069

merged 3 commits into from Jul 20, 2016

Conversation

@ssalinas
Copy link
Member

@ssalinas ssalinas commented Jun 7, 2016

Right now, if a run once task is already running, we cannot enqueue another until it is finished. These changes allow multiple run once tasks (from different deploys) to run at the same time. There will still be a conflict if the previous deploy is still in progress (i.e. poller hasn't finished it yet), but that's a separate problem to tackle if it happens to slow us down too much

@gchomatas

edit: previously if deploys came too close together, we would actually miss one of them and never run a task for it, that is fixed in this as well

@ssalinas ssalinas added the hs_staging label Jun 7, 2016
@ssalinas ssalinas added hs_qa labels Jun 7, 2016
@ssalinas ssalinas merged commit fb19e94 into master Jul 20, 2016
1 of 2 checks passed
1 of 2 checks passed
continuous-integration/travis-ci/pr The Travis CI build failed
Details
continuous-integration/travis-ci/push The Travis CI build passed
Details
@ssalinas ssalinas deleted the multi_run_once branch Jul 20, 2016
@ssalinas ssalinas removed hs_qa labels Jul 20, 2016
@ssalinas ssalinas added this to the 0.9.0 milestone Jul 29, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

1 participant
You can’t perform that action at this time.