Downloads:

552,772

Downloads of v 4.30.5:

767

Last Update:

30 Jan 2018

Package Maintainer(s):

Software Author(s):

  • Octopus Deploy

Tags:

automation deployment

Octo.exe

This is not the latest version of Octo.exe available.

4.30.5 | Updated: 30 Jan 2018

Downloads:

552,772

Downloads of v 4.30.5:

767

Maintainer(s):

Software Author(s):

  • Octopus Deploy

Tags:

automation deployment

Octo.exe 4.30.5

This is not the latest version of Octo.exe available.

All Checks are Passing

2 Passing Test

Validation Testing Passed

Verification Testing Passed

Details

To install Octo.exe, run the following command from the command line or from PowerShell:

>

To upgrade Octo.exe, run the following command from the command line or from PowerShell:

>

To uninstall Octo.exe, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade octopustools -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade octopustools -y --source="'STEP 3 URL'"
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Ensure octopustools installed
  win_chocolatey:
    name: octopustools
    state: present
    version: 4.30.5
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'octopustools' do
  action    :install
  version  '4.30.5'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: octopustools,
    Version: 4.30.5,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller octopustools
{
   Name     = 'octopustools'
   Ensure   = 'Present'
   Version  = '4.30.5'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'octopustools':
  provider => 'chocolatey',
  ensure   => '4.30.5',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install octopustools version="4.30.5" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 31 Jan 2018.

Description

Octopus Deploy is an automated deployment tool powered by NuGet. This package contains Octo.exe, a command line tool for creating and deploying releases with Octopus Deploy.

tools\init.ps1 
param($installPath, $toolsPath, $package, $project)

$path = $env:PATH
if (!$path.Contains($toolsPath)) {
    $env:PATH += ";$toolsPath"
}
tools\LICENSE.txt 
From: https://github.com/OctopusDeploy/OctopusClients/blob/master/LICENSE.txt

LICENSE

Copyright (c) Octopus Deploy and contributors. All rights reserved.

Licensed under the Apache License, Version 2.0 (the "License"); you may not use
these files except in compliance with the License. You may obtain a copy of the
License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software distributed
under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR
CONDITIONS OF ANY KIND, either express or implied. See the License for the
specific language governing permissions and limitations under the License.
tools\Octo.exe 
md5: D8CBCA0792E30608A0C58683161B076A | sha1: F1626833FAEFF61DDFF9B93D537C2ED315616D73 | sha256: A89209ABB87FE79B5C187B83F774E8136E3426901177EEFBD09C3DF54E0478EF | sha512: 3409407DEFB3018BD113D1C318D38E6DC278F9B0595BE3D268D61E007E3603B667355394BB728F817EA35641F4F606A998024B382B94963E71E2B4563E279882
tools\Octo.exe.config 
<?xml version="1.0" standalone="yes"?>
<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="System.Runtime" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-2.6.9.0" newVersion="2.6.9.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
  <startup>
    <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5" />
  </startup>
</configuration>
tools\VERIFICATION.txt 
VERIFICATION
Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

This package is published by the Octopus Deploy team itself.

Log in or click on link to see number of positives.

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
Octopus CLI 7.4.1 4802 Thursday, July 2, 2020 Approved
Octopus CLI 7.4.0 1246 Thursday, June 25, 2020 Approved
Octopus CLI 7.3.7 5378 Tuesday, May 19, 2020 Approved
Octopus CLI 7.3.4 6477 Friday, April 17, 2020 Approved
Octopus CLI 7.3.3 132 Friday, April 17, 2020 Approved
Octopus CLI 7.3.2 4050 Friday, March 27, 2020 Approved
Octopus CLI 7.3.1 1110 Sunday, March 22, 2020 Approved
Octopus CLI 7.3.0 662 Tuesday, March 17, 2020 Approved
Octopus CLI 7.2.0 1506 Thursday, March 12, 2020 Approved

This package has no dependencies.

Discussion for the Octo.exe Package

Ground Rules:

  • This discussion is only about Octo.exe and the Octo.exe package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or Octo.exe, or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus