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

Migrator doesn't handle DefaultWorkerPoolId #5065

michaelnoonan opened this issue Nov 7, 2018 · 3 comments


Copy link

commented Nov 7, 2018

We added the concept of certain deployment targets having a DefaultWorkerPoolId, but we neglected to handle it in the data migrator.

What I expected to happen

  1. If the source has a default worker pool, try to use the same default worker pool when importing.
  2. When merging the source with an existing destination, treat the source as truth, setting or clearing the default worker pool as appropriate.

Affected versions

Octopus Server: 2018.7.0 until fixed.


Unfortunately nothing good. After importing make sure your default worker pool for any supported deployment targets are set as you'd expect.

@octoreleasebot octoreleasebot added this to the 2018.9.7 milestone Nov 12, 2018

This comment has been minimized.

Copy link

commented Nov 12, 2018

Release Note: migrator.exe now correctly handles the default worker pool selected by certain deployment targets, where the selection would have been dropped during the import process


This comment has been minimized.

Copy link

commented Feb 10, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. If you think you've found a related issue, please contact our support team so we can triage your issue, and make sure it's handled appropriately.

@lock lock bot locked as resolved and limited conversation to collaborators Feb 10, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
2 participants
You can’t perform that action at this time.