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

Saving IIS related steps created by previous version of Octopus fails #3753

Closed
NickJosevski opened this issue Aug 25, 2017 · 6 comments
Closed
Assignees
Milestone

Comments

@NickJosevski
Copy link

NickJosevski commented Aug 25, 2017

Issue

If the bindings are stored as a pipe delimited set when you add to the set or remove from it, save fails with a console error on bindingsToString.

Old style binding: http:#{httpPort}://#{UseStandardHttpBinding}/false when parsed host is undefined.

image

Solution

A new migration Script0092MigrateIisBindingsToJson that reads entire DeploymentProcess table, looking in Steps -> Actions -> Properties -> Octopus.Action.IISWebSite.Bindings, it ignores any that are new style, already have the indicator of starting as a JSON array is empty [] or start of populated set [{.

A new BindingEntry is built up from the split up of the pipe delimited string, following how Calamari does it in this conditional branch of code.

Test cases

In test function: CleanupBindingsCheck_Script0092MigrateIisBindingsToJson

  • Unit tests with crafted steps containing old style

    • 2 taken from customers reporting issue
    • 1 hand crafted
  • Compared Database pre migration with post migration (Script0092MigrateIisBindingsToJson)

During testing, reviewed changes to the entire document, only changes were by design.

image

@NickJosevski
Copy link
Author

This related to #3752

The plan is to write a data migration script so the v1 parser and anything else can go away, and stop biting us.

@NickJosevski
Copy link
Author

@NickJosevski NickJosevski self-assigned this Aug 29, 2017
@pawelpabich pawelpabich added this to the 4.0 milestone Sep 28, 2017
@pawelpabich
Copy link

@NickJosevski, I think we can close this one off ?

@NickJosevski
Copy link
Author

@pawelpabich yes it will be fixed for customers when they install v4 and Script0093MigrateIisBindingsToJson runs, same goes if they run the migrator and go to v4.

@NickJosevski
Copy link
Author

Release Note: Fixed error that occurs when saving IIS related project steps that were created by earlier versions of Octopus

@lock
Copy link

lock bot commented Nov 24, 2018

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 Nov 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants