Migrator doesn't gracefully handle project triggers with an environment filter

[michaelnoonan]

Imagine you have an project trigger which is filtered so it only applies for events from certain environments, like Dev and Test. If you export a project which can only be deployed to Test but not Dev, the Dev environment won't be exported since it's not necessary for that project. Now when you import the project, it will fail when importing the project trigger because there is no such environment as Dev in the target.

What I expected to happen

When importing a project trigger which is restricted to certain environments, if any of those environments do not exist in the target, remove the restriction instead of failing the import.

Most other places follow this logic. Following suit will make this scenario behave similarly.

Affected versions

Octopus Server: 3.5 until fixed.

Workarounds

Nothing good:

1. Only perform full exports and imports.
2. Avoid using events from unrelated environments to trigger deployments to different environments.

[michaelnoonan]

ProjectTriggerImporter doesn't handle missing environments very well

[octoreleasebot]

Release Note: migrator.exe now correctly handles importing project triggers which filter events for certain environments where some of those environments do not exist in the target

[lock]

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.