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 does not gracefully handle importing project connections where the source project or environment does not exist in the destination #5072

michaelnoonan opened this issue Nov 8, 2018 · 3 comments


Copy link

commented Nov 8, 2018

Imagine a scenario where you have a mixture of projects using certain lifecycles deploying to a wide variety of environments. Now imagine you have a handful of tenants connected to a variety of those projects and environments. Finally, imagine you export one of those projects, and import it into a different Octopus Server. The tenant being migrated across is connected to a whole bunch of projects and environments which may have been exported via the partial export of a single project.

Based on how the migrator works in similar scenarios, customers expect the migrator to do its best job at merging the results together.

Today, the import process fails hard when it cannot find a mapping for an environment which a tenant is connected to.

What I expected to happen

The import process should do its best to map any projects and environments it knows about, and merge the results.

Affected versions

Octopus Server: 3.4 until fixed




This comment has been minimized.

@octoreleasebot octoreleasebot added this to the 2018.9.10 milestone Nov 13, 2018

This comment has been minimized.

Copy link

commented Nov 13, 2018

Release Note: migrator.exe now gracefully handles the importing tenant + project + environment connections when the project or environment does not exist in the target

@slewis74 slewis74 modified the milestones: 2018.9.10, 2018.9.8 Nov 13, 2018

This comment has been minimized.

Copy link

commented Feb 11, 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 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
None yet
3 participants
You can’t perform that action at this time.