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

Install to non-version-specific path; 64-bit MSI #358

Closed
PaulStovell opened this issue Dec 16, 2013 · 5 comments
Closed

Install to non-version-specific path; 64-bit MSI #358

PaulStovell opened this issue Dec 16, 2013 · 5 comments
Labels
kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time
Milestone

Comments

@PaulStovell
Copy link
Member

Our MSI installer currently installs Octopus to:

C:\Program Files (x86)\Octopus 2.0

(With a Server and Tools subdirectory)

And Tentacle to:

C:\Program Files (x86)\Octopus Tentacle 2.0

(With Agent and Tools subdirectories)

Using "2.0" was a bad idea of mine as it is likely to be confusing when we have a 2.1 release and so on. And I don't even want to have to change it for Octopus 3.0 (which should be an in-place upgrade ideally).

Thoughts:

  • Octopus is AnyCPU so it shouldn't really go under the x86 folder. Perhaps we can do something to fix this in WiX now?
  • Can we just install them to a simple directory structure like below?

Example:

 C:\Program Files\OctopusDeploy\Octopus
 C:\Program Files\OctopusDeploy\Tentacle

We can combine the tools and agent/server binaries all into the same folders so we don't need separate subdirectories for them.

(Putting this in the 2.0 milestone since it's better to change sooner rather than midway through 2.0)

@nblumhardt
Copy link
Contributor

+1 for the removal of the version number.

I'd be wary of trying to colocate/share any installation components though (tools/binaries) as that will take us down some MSI paths I'd probably rather not travel... There's not a big gain in disk space or simplification for the majority of uses as far as I can tell..?

Getting it to Program Files should be as simple as specifying the platform, e.g.:

    <Package ...
             Platform="x64"/>

@PaulStovell
Copy link
Member Author

Decision:

  • Make them install to:
 C:\Program Files\Octopus Deploy\Octopus
 C:\Program Files\Octopus Deploy\Tentacle
  • Build platform-specific MSI's - one for x64 and one for x86. But the binaries themselves will still be Any CPU.
  • Flatten Sever/Agent and Tools into a single folder

@nblumhardt
Copy link
Contributor

Add:

  • Publish x64 installers to S3 (already happens :))
  • Add an x64-only installer link to Octofront

@nblumhardt
Copy link
Contributor

One caveat - our installers don't remove/reinstall services, so after upgrading from an x86 to x64 installation (even with a full uninstall) it is necessary to delete/re-add the Octopus or Tentacle instance before the service will re-start.

Probably just needs a documentation entry, not much else we can do here.

@lock
Copy link

lock bot commented Nov 28, 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 28, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/enhancement This issue represents an enhancement we are committed to adding to Octopus as some time
Projects
None yet
Development

No branches or pull requests

2 participants