I was following the instructions (https://octopusdeploy.com/blog/octo-exe-import-export) to export/import a project from our production Octopus Deploy environment running 2.5.8 to an internal environment running Octopus Deploy 2.6 to test the new lifecycles feature, and ran into the following issue when attempting to import:
===========================================
Octopus Deploy Command Line Tool, version 2.5.10.39
Handshaking with Octopus server: https://octopusdev
Handshake successful. Octopus version: 2.6.0.751; API version: 3.0.0
Finding importer 'project’
Beginning the import
Export file successfully loaded
Checking that all environments exist
Checking that all machines exist
Checking that all NuGet Feeds exist
Checking that all Library Variable Sets exist
Checking that the Project Group exist
Beginning import of project 'Demo2’
Importing Project
Project does not exist, a new project will be created
Error from Octopus server (HTTP 400): There was a problem with your request.
- The project must be assigned to a lifecycle.
Exit code: -7
While not a showstopper for this test setup, I’m not sure how I would work around this error since Lifecycles was introduced in 2.6, but my exported projects came from an earlier release. Is there something I might be missing here?
Any information would be appreciated! Thanks for your great help and support!
-Sam